Team Collaboration

Workspace membership controls access to diagrams, documents and other workspace content. A copied content link does not grant access, including on the Free plan.

Roles

An invitation can grant Editor or Viewer access. It cannot grant ownership or administrator privileges. Ownership transfer is not available in this release.

Invite a teammate

1. Open Settings → Team in the workspace.
2. Choose Invite Member and select Editor or Viewer.
3. Create the invitation and copy its link.
4. Send the link to the intended teammate, who signs in before accepting it.

The interface creates an invitation link; it does not send an email automatically. An unused link expires after seven days and can be revoked in the invitations list. A link is redeemed once. Keep it private until the intended teammate accepts it.

API-created invitations can specify an email address. Those invitations require the recipient's verified primary email to match. Invitations created without an email can be accepted by the first signed-in person who has the link.

Edit diagrams together

Presence and cursor indicators show connected collaborators. Committed diagram changes are broadcast to workspace members. If your diagram has no pending local edits, it can receive the new version.

Diagram saves include a revision. When someone else changes the same diagram or shared UML model first, a stale save is rejected. The editor keeps local work and stops saving so you can resolve the conflict; it does not merge every simultaneous edit automatically.

1. Download the local JSON when the editor reports a conflict.
2. Reload the latest saved version only after preserving your local work.
3. Reapply the intended changes and save again.

Documents, presentations, brainstorms and planning items also use revisions. Their stale updates and deletions are rejected. Unsaved editor content remains available when a newer version arrives or access changes. Reconnecting refreshes clean content; pending local changes require review.

Version history and recovery

Open History in the workspace sidebar to see changes across diagrams, documents, presentations, brainstorms, sprints, epics, stories and work items. Content editors also offer history for the open item.

1. Select a saved version to see its author, time and operation.
2. Choose a changed field to compare removed and added content.
3. Save or download pending local edits before restoring.
4. Choose Restore this version and confirm. Restoration creates a new version; earlier versions remain available.

Owners and Editors can restore; Viewers can inspect and download history. Deleted items remain in workspace history. Restore an earlier version to recover the same item, provided required linked items still exist. Deleting the entire workspace also deletes its history.

For UML diagrams, restoration includes the shared workspace model. It can change other diagrams that use the same elements. The confirmation names this effect, and restoration is rejected if it would invalidate another view or if either revision changed.

History records committed changes from this release onward. Older content gets a baseline when first changed; that baseline records when it was captured, not an invented original edit date. Legacy diagram versions without enough metadata remain downloadable but cannot be restored exactly.

Version history is separate from server backups. A database or host failure requires a server backup; the version list is stored with the workspace.

Accounts and access

Sign in with the account that accepted the invitation. Workspace membership is checked by the API; being connected to a collaboration room does not replace that check. MCP also checks the same membership and additionally requires the OAuth scope for each operation.