Core Workflow

Collaboration and saving

Work alongside teammates and AI agents, understand live presence, and handle interrupted saves.

Team members with edit access can work on the same project. Documentation supports shared text editing; Structure and Pages show where others are viewing, selecting, editing, or moving content.

Read live presence

In Documentation, connected editors' names and editing positions appear in the document. In the canvases, live cursors and activity indicators help you see which nodes, pages, or sections are receiving attention.

Presence is a coordination aid. A Selected, Editing, or Moving indicator is not a guarantee that a field is exclusively reserved. Different records can save concurrently, but two people changing the same content may still encounter a conflict.

Agree who is working on a shared definition or a major revision. In Pages, editing a reusable section's definition can affect every page using it, even if those page cards are elsewhere on the canvas.

Finish saving

Wait for Saved in the project header before leaving, closing the browser, or handing work over. Saving... means the current save is still in progress. Draft, Save failed, or Session expired requires attention.

The Pages section editor applies valid edits after a short pause and when closing or switching sections. There is no separate Save step. Correct validation errors before continuing and check the project header for Saved. Discard pending edits, when offered after an error, removes only pending changes; it does not undo changes already saved.

Saving is separate from publishing AI Context. The team can work on the live project while trusted AI tools continue reading the last deliberately published snapshot.

Handle a conflict or connection problem

  1. Keep the project open and read the message shown.
  2. Preserve unsaved text or use the recovery download when offered.
  3. Restore the connection or follow the sign-in instructions.
  4. If a reload is required, preserve pending work first, then inspect the latest project.
  5. Reapply only the changes still needed and check for Saved.

Do not clear browser storage as a first response: it may contain pending work. If the problem repeats, contact support with the project name, the error message, and what you were editing. See Troubleshooting.

Work with a computer-use agent

An agent uses the access and identity of the signed-in account. Give it a clear, focused task and ask it to read the current target before editing. Avoid having a person and agent type into the same section or edit the same node at once.

Ask the agent to check the result and wait for Saved after meaningful changes. If its task is interrupted, inspect what already saved before retrying, so it does not duplicate nodes, sections, or connections.

The normal workspace History records the changes. It does not automatically identify an edit as AI-generated or collect an entire agent task into one entry. Save a named milestone before a significant revision when you want a clear recovery point.

Read Update an existing project with AI for examples and tool requirements.

Coordinate restores

A restore replaces a workspace version and can undo other editors' subsequent changes there. Let collaborators finish saving and review the comparison before confirming. Other open editors may need to preserve unsaved work and reload afterwards.

Use History, milestones, and restore to understand the scope. For a small mistake, a focused correction is often easier to review than a workspace restore.

Client review

The Share link provides a separate view-only project. Clients cannot edit or comment through it, and can use Refresh to load newer saved content. See Share a project for client review.