Live edit apply is behind a beta flag
By default you get presence and the room. Merging concurrent edits into the document requires the beta flag to be on.
Up to twenty people in one room. You can see who is in, and someone who joins late receives the whole document instead of catching up by hand.
Applying live edits is gated behind a beta flag; presence is on by default.
You start alone. Then someone reviews the design, someone rewrites the copy, someone checks the prices. That only works if two people can hold the same project open at once — seeing each other, and having their changes converge rather than overwrite.
Permissions come from the workspace, so the same roles apply everywhere.
Add people and give each one a role: owner, admin, editor, or viewer.
Everyone in the room shows up in the presence indicator with a live count.
A late arrival receives the current document in full and is immediately in step.
These are enforced by the collaboration gateway, not by convention.
The twenty-first connection is refused with a message that says why.
Owner covers billing and deletion, admin manages people, editor builds, viewer reads.
The full current state is sent on join, so nobody replays history to catch up.
Edits made while briefly offline merge back in when the connection returns.
Concurrent edits converge to the same result regardless of arrival order.
Each window with two or more people is stored with its start, peak size, and duration.
Presence ships today; shared editing is deliberately still gated.
By default you get presence and the room. Merging concurrent edits into the document requires the beta flag to be on.
Talk on whatever you already use. This synchronises the project, not the conversation.
Leaving a note pinned to a spot in the project is not built yet.
A workspace with no owner has nobody who can pay or delete, so that removal is refused.
Seats and credits are shared at the workspace level, which is where the pricing page starts.