Your team. Your AI.
On the same page.

Yes. Connected MCP clients can read the section outline and edit a section by heading, heading path, or block ID. Each client should send the hash returned when it read that section: changes elsewhere stay in place, while a changed target returns a conflict with the current text to review. Every successful section edit saves a version under the identity of the person who authorized the connection. Document permissions and locking still apply.

Yes. People with edit access can type in the same document at the same time. Each teammate has a named, colored cursor and selection, and their edits appear in the shared editor. Changes are acknowledged after saving; if the connection drops, pending edits reconnect and merge with the latest document. Undo applies to your own edits. View permissions and document locks still apply, and public published pages remain read-only.

Yes. Select text and choose Task from the formatting toolbar. Leera uses the text as the task title and replaces the selection with a linked issue. If no project is active, the task creation dialog lets you choose one.

With a configured AI provider, select text to improve writing, fix grammar, change tone or length, translate, summarize, explain, or simplify. Review the suggestion before accepting or inserting it, adding it below where available, or discarding it.

Autosave keeps the current document up to date. Save version adds a checkpoint to history. You can preview a saved version and restore its title, icon, and content; restoration saves the current version first so you can return to it.

The Share tab shows page access. Workspace visibility gives members view access; private pages use individual and inherited collection permissions. Owners can grant workspace members viewer or editor roles. Collection permissions still apply, and owners can lock a page to pause editing until it is unlocked.

A document’s owner can publish it as a public read-only page, and a collection’s owner can publish the whole collection. A published collection shows every page in it that is not private or archived, including pages added or moved into it later. Publishing shares the displayed content and attachments, not the rest of the workspace. Later edits appear on the published page. Unpublishing a page’s own link does not remove public access through a published collection; manage collection sharing too. Publishing again restores the same link.

On a self-hosted instance, an administrator can choose a published collection as the site’s public blog at /blog. Its pages keep the collection’s search engine indexing choice and use their blog addresses as their canonical URLs.

Yes. On individual document links, Appearance lets readers change text size, typeface, page width, and light, dark, or automatic theme. These controls do not edit the published document. Readers can also copy its text or use the layout preview to choose paper size, orientation, and scale, then download a PDF directly.

Published pages and collections have a Show in search engines setting, which is off by default. With it off, they ask search engines not to index them. With it on, canonical pages can be indexed and appear in the published-page sitemap. Pages in an indexable collection follow that collection’s choice. Anyone with a public link can read the content regardless of its search setting; the rest of the workspace keeps its access rules.

The document outline turns headings into a compact rail of ticks. Open the outline to see the section titles and choose a heading to jump to it. The active section follows your position while editing or reading an individual published document.