Collaboration

What you'll learn

• How presence indicators show who else is in the project and on which tab
• How simultaneous draft co-editing works (and what its limits are)
• How to leave, resolve, and reply to comments on a diagram
• How to mark items as checked or flagged during review
• How to share specific diagrams, versions, harnesses, and whole projects via links

Prerequisites

• Complete Tutorial 2: App Overview so you know the layout and where Properties and the left pane live.
• Complete Tutorial 12: System Configuration & Versioning so you understand variants, checkpoints, and releases.
• You need at least one teammate in the same organization to try the multi-user flows for real.

Steps

1See who else is in the project

Two presence indicators run side by side.

• Top-right project avatars — colored circles with 2-letter initials next to your profile avatar. Up to 5 are shown; additional users appear as +N. Click any avatar to open a popover that lists each user's email and their currently active tab (diagram, harness, library item, or version history). Click a row to open that same tab in your own workspace.
• Tab-level "same view" indicator — every editor tab shows a small user icon with a count (e.g. 👤 2) when other teammates are looking at exactly the same view. Hover to see their emails. Diagram tabs and harness tabs count separately even when they share an underlying version.

There are no live cursors and no remote selection highlights — presence tells you who is around, not what they are touching.

2Co-edit a draft in real time

Two Editors (or an Editor and an Administrator) can edit the same draft version of a diagram at the same time. Changes are debounced and synced about once a second through the cloud.

• Your edits show Syncing Changes... then All Changes Synced in the sidebar footer.
• Conflicting edits are merged where possible; rejected edits snap back automatically.
• A small white dot appears on tabs with unsynced local changes.

Important constraints:

• Checkpoints and releases are read-only for everyone. Viewer-role users are read-only on drafts too. Read-only views show a banner naming the checkpoint or release, with a link back to the editable draft.
• Read-only users can still leave comments. Non-comment edits on read-only views are reverted.
• This is polling-based sync, not push — there is no live keystroke-by-keystroke broadcast.

3Leave a comment on the canvas

Comments are version-scoped notes anchored to a point on the diagram.

1. Right-click empty canvas (or right-click an item) where you want the comment → Add Comment.
2. Type into the placeholder Enter your comment....
3. Click Comment to post, or Cancel to discard.

The comment appears on the canvas with optional arrow pointers to related items. Comments are stored on the current diagram version (and, in the harness editor, on the current harness too). Checkpoints and new variants copy existing comments forward.

4Browse comments in the left pane

For a project-wide view of comments on the active version, use the comments pane.

1. Open the editor's left pane and click the Comments tab, or press Ctrl/Cmd+Shift+C.
2. The header reads Comments (N Unresolved) when there's open work.
3. Click any comment row to highlight it on the canvas.
4. Use the eye icon to toggle Show on canvas / Hide on canvas (this preference is per-user and remembered between sessions).
5. The empty state reads No comments yet / Right-click the canvas to add a comment.

5Resolve and reply to comments

Each comment supports a thread, resolve/unresolve, and editing your own text.

• Resolve — click the purple checkbox circle on the comment or in the Comments pane. Tooltip: Unresolved — click to resolve / Resolved — click to unresolve. Resolved comments auto-collapse and show a Resolved label.
• Reply — select a saved comment so the right pane title changes to Comments. Use the Reply... textarea and click Reply to post (or Cancel to discard).
• Edit your own text — click the pencil icon next to your message; Save or Cancel the change.
• Viewers can resolve their own comments but cannot resolve other people's threads — they'll see a Blocked Action toast if they try.

There are currently no @mentions and no in-app notification bell — teammates discover new comments by opening the version and checking the Comments pane.

6Mark items as checked or flagged

For quick review marks, use checks (reviewed, OK) and flags (needs attention) instead of full comments. Right-click the canvas or an item → Add Check or Add Flag, or drag one from the Checks / Flags tiles in the Comments pane. Flags can be resolved; both can carry a note.

7Copy shareable links

Anyone in your organization with access to the project can open the same view. There is no per-project invite; to share a project, send its link.

Recipients who open the link while logged in are routed to the right project, variant, checkpoint, or harness.

8Work in parallel and review

For larger parallel changes, give each engineer their own variant. For reviews, open a read-only checkpoint or release and leave comments there, or add Required Reviewers when releasing. See Tutorial 12: System Configuration & Versioning.

9Use the Artifact Agent (if enabled)

If your organization has the Artifact Agent (Copilot) enabled, an Open Artifact Agent button appears in the top-right next to your profile avatar.

• The Agent is a single-user AI assistant, not a multi-user chat. Each user has their own threads stored locally.
• The Agent can perform tools on your behalf (search the library, propose library item changes, etc.) but its work doesn't show up in teammates' presence.
• Use the New chat menu item to start a fresh thread.

Treat the Agent as your personal pair-programmer, not a shared channel. For a full walkthrough of capabilities, chat management, and library/diagram edits, see Tutorial 18: Using the Copilot.

Summary

You can see who is in your project and on which tabs, co-edit drafts with teammates in near-real-time, leave comments with threads and resolution, share specific views through links, and use variants and checkpoints for parallel work and review. Presence is passive (no live cursors), comments are version-scoped, and there is no per-project sharing.

What's next

• → Tutorial 17: Admin Options — add teammates and assign roles.
• → Tutorial 12: System Configuration & Versioning — variants, checkpoints, and releases.