Live collaboration
Enable real-time editing
Section titled “Enable real-time editing”- Invite collaborators with the appropriate permissions.
- Open the project’s Share dialog.
- If available, turn on Real-time collaboration.
- Follow the Reload document prompt when the editing mode changes.
The reload switches the document into the correct editing session. Ask other people who already have it open to follow their reload prompt too.
This example shows Alice and Sam working on methods.typ in separate browser sessions. The paper remains the same project; they do not exchange new copies of the source after each edit.
See who is editing
Section titled “See who is editing”Colored labels above live cursors show each collaborator’s name without needing to hover. Names come from their account display name, with an email name or Anonymous as a fallback. Long names may be shortened to fit the label.
This close-up uses demonstration names and a sample document. Cursor labels identify where people are working; they do not mark authorship of every passage.
Join and leave notices
Section titled “Join and leave notices”A brief notice appears when someone joins or leaves the document. It disappears after six seconds, or you can dismiss it with the close button.
Multiple tabs from the same account count as one person for these notices. Your own other tabs do not generate alerts. Opening the document or reconnecting establishes who is present without announcing everyone again. If someone loses their connection abruptly, their leave notice may be delayed.
Presence notices are temporary indicators, not an activity history or proof that changes have synced. They do not require browser notification permission.
Discuss changes while editing
Section titled “Discuss changes while editing”Use inline comments and replies for questions about a passage. On desktop, select text to open Enter comment… beside the selection. Suggested changes are useful when an edit needs review rather than immediate acceptance.
Without real-time collaboration, the app may reserve ordinary editing for one active editor. Respect the presence or reload notices rather than assuming another editor’s changes will merge.
Connection and external changes
Section titled “Connection and external changes”If a connection drops, preserve the current browser’s work and reconnect before moving to another device. An update from Git, history restoration, or an external tool may require the open session to refresh or reconcile.
Read the app’s recovery message before reloading, especially if it reports pending local changes. See saving and offline use for the difference between local changes and synced work.
After a server security update
Section titled “After a server security update”Reload open tabs after the live-channel authentication update. Document events and collaboration no longer accept sign-in tokens in URLs. Removed sharing permissions, suspended accounts, expired credentials and revoked API keys stop live access; offline edits remain on your device for recovery. Automation that opens event streams must send Authorization: Bearer …; custom WebSocket clients can send the same header.