What you will do
1
Invite a teammate
Add a person to your organization by email so they can open the same workflows you can.
2
Open the same workflow
You and your teammate both open one workflow in the builder and join the same live canvas.
3
Co-edit live
Move nodes, add steps, and edit configuration while seeing each other’s cursors and node locks in realtime.
4
Resolve a conflict
Watch what happens when two edits collide, and learn how ModuleX reconciles them for you.
Before you start
An organization you administer
You invite teammates into an organization. Only an organization owner or admin can send invitations.
A workflow to share
Have at least one workflow saved in the Workflow Builder. Everyone in the organization can open it.
A teammate's email
You invite by email address. Your teammate signs in (or signs up) with that email to accept.
Two browser sessions to follow along
To see live co-editing yourself, open the workflow in two windows signed in as two different people.
Step 1 — Invite a teammate
People collaborate inside an organization. Adding a teammate to your organization is what gives them access to your shared workflows.1
Open your organization's members
Go to your organization settings and open the members area. You see this only if you are an owner or admin of the organization.
2
Send an invitation by email
Enter your teammate’s email address and send the invitation. New teammates are added with the admin role.
ModuleX organizations have two roles: owner and admin. The older
member role has been retired, so an invited teammate joins as an admin. See Roles & permissions for what each role can do.3
Your teammate accepts the invitation
Your teammate opens the invitation link and accepts it while signed in with the invited email address. If they are not signed in yet, the link prompts them to sign in or sign up first, then completes the acceptance.
If they sign in with the wrong account
If they sign in with the wrong account
Acceptance is tied to the invited email address. If your teammate is signed in with a different account, ModuleX tells them which account the invitation was sent to so they can switch to the right one and try again.
4
They switch to the shared organization
After accepting, your teammate selects the organization from the organization switcher. Everything they do from then on is scoped to that organization, and your shared workflows become visible to them.
A freshly accepted role can take up to a few minutes to take effect on the live collaboration server, which caches membership briefly. If a brand-new teammate cannot edit immediately, have them refresh after a minute.
Step 2 — Open the same workflow
Now both of you open the same workflow so you share one live canvas.1
Both open the workflow in the builder
Each person opens the workflow from the Workflow Builder list. Opening a workflow joins you to its live collaboration room automatically — there is no separate “start collaborating” button.
2
Confirm you are both in the room
When your teammate joins, their presence avatar appears in the canvas, and you appear on theirs. Each person is assigned a color that is used consistently for their avatar, their cursor, and any node they are editing.
You do not save and reload to see each other’s work. Everyone is editing the same live graph, so changes appear as they happen. There are no separate copies to merge later. For the full picture of the two realtime planes (live canvas editing versus run streaming), see Realtime & collaboration model.
Step 3 — Co-edit live
With both of you in the same workflow, you can build together. Here is what you will see, and what each signal means.Presence and cursors
Presence avatars
Everyone currently in the workflow shows up as a colored avatar. When someone leaves or closes the tab, their avatar disappears.
Live cursors
You see your teammate’s cursor move across the canvas in their assigned color, so you always know where their attention is.
Away status
If a teammate stops interacting for a while, they are shown as Away rather than dropping off entirely. They come back to active as soon as they interact again.
Consistent colors
A person’s color is the same for their avatar, cursor, and edit badge, so it is easy to tell at a glance who is doing what.
Editing nodes safely with locks
To stop two people from editing the same node at the same instant, ModuleX uses node locks.1
Open a node to edit it
When you open a node in the Detail Panel to change its configuration, ModuleX claims a lock on that node for you.
2
Teammates see the node is held
While you hold the lock, your teammates see that node marked as being edited by you, in your color. If they try to open it, ModuleX tells them who is currently editing it instead of letting them collide with you.
3
The lock releases when you are done
Your lock releases when you finish editing the node. It also releases automatically if you leave the workflow or disconnect, and it expires on its own after a few minutes of being held, so a node never stays stuck if someone closes their laptop mid-edit.
Locks apply to editing one node’s configuration. Moving nodes around the canvas, adding new nodes, and connecting edges are not locked — those changes simply broadcast to everyone live. The lock exists to protect the inside of a node while one person has it open.
What broadcasts live
Most edits flow to everyone in the room as you make them:Adding and deleting nodes
A node your teammate adds appears on your canvas moments later, already in place.
Moving nodes
Dragging a node to a new position updates it for everyone, so the layout stays in sync.
Connecting steps
New edges between nodes show up for the whole room as they are drawn.
Node configuration
Configuration changes save to the shared workflow and reach your teammates once the editor finishes with the node.
Step 4 — Resolve a conflict
Because everyone edits the same live graph, ModuleX keeps every collaborator on the same version. Most of the time this is invisible — edits stream back and forth and stay in order. Occasionally two people make changes so close together, or one person’s connection lags far enough behind, that their version of the workflow has drifted from the shared one. That is a conflict, and ModuleX resolves it for you.What you will see
1
A short notice appears
The person whose edits fell behind sees a brief notice that their changes conflicted and the workflow is reloading.
2
Their canvas reloads to the latest version
ModuleX pulls the current shared version of the workflow and shows it. The other collaborators are unaffected — they keep working.
3
Everyone is back in sync
After the reload, both people are looking at the same up-to-date graph, and editing continues normally.
You do not resolve a conflict by hand and there is no “accept mine / accept theirs” prompt. ModuleX always reconciles by reloading the behind collaborator to the latest shared version. The reliable way to avoid losing in-progress edits to a single node is to use the node lock: hold the node while you edit it, and your teammates will not edit it underneath you.
Why does a conflict reload instead of merging?
Why does a conflict reload instead of merging?
ModuleX tracks a version number for the live workflow and advances it on every accepted edit. If a collaborator’s edits arrive while their version has drifted too far behind the shared one, ModuleX cannot safely apply them in place, so it reloads that person to the current version rather than risk applying a stale change. Locking a node before you edit its configuration keeps your work safe while you have it open. The exact version and conflict mechanics are documented on Presence, locks & versioning.
Changes from Composer or the API
Not every change to a workflow comes from a person dragging nodes. The AI Composer can rewrite the graph, and so can changes made elsewhere. When that happens while you have the workflow open, those edits sync into your open canvas live so you are always looking at the current version — you do not have to reload to pick them up. See Realtime co-editing & external sync for how that external sync works.A few things to know
Do I need an API key for any of this?
Do I need an API key for any of this?
No. Live co-editing happens entirely inside the ModuleX web app, which signs you in with your account session. There is no REST endpoint or SDK method for presence, cursors, or locks — they exist only on the live collaboration connection the app makes for you. API keys (
mx_live_*) are for running workflows programmatically; see Authentication.How many people can edit at once?
How many people can edit at once?
Everyone in your organization who opens the same workflow joins the same live room and can edit together. There is no separate per-workflow collaborator list — organization membership is what grants access.
What happens to my locks if I close my laptop?
What happens to my locks if I close my laptop?
Any node locks you hold are released automatically when you leave the workflow or disconnect, and they also expire on their own after a few minutes. A node never stays locked because someone walked away.
My teammate accepted but cannot edit yet
My teammate accepted but cannot edit yet
The live collaboration server caches organization membership for a short time. A brand-new teammate may need to wait a minute and refresh before their edit access takes effect. See Account & access — Help.
Where to go next
Canvas collaboration
The product tour of what co-editing looks and feels like.
Presence, locks & versioning
The wire-level reference: every event, payload, timing, and edge case.
Build a workflow with Composer
Go from a plain-English prompt to a running workflow.