Multi-User Editing

Multi-user editing combines permissions with page-specific edit control. Collaborator roles decide what a person may do; an edit lock, request, handoff, or takeover decides who currently owns writes to one page. These are related operationally but are not the same concept.

Inspect collaborator scope without confusing it with a lock

The privacy-safe Collaborators panel shows site invitation scope and an empty collaborator list. Use it to understand who can administer content and publishing, but do not read it as evidence that any page is currently locked.

Roles and edit control are different

An Administrator can manage content and publishing within the site’s allowed scope, while owner-only billing and deletion remain unavailable. A page lock does not grant a role, and a broader role does not bypass the current editor’s lock.

Request edit, Hand off page, and Take over

Use the smallest coordination action that protects the current work.

Request edit

When another human editor owns the page, choose Request edit. The current editor can choose Hand off page or Keep editing; if they do not answer, the page transfers automatically after three minutes. Requests from Codex through MCP are approval-only and remain pending until the current editor explicitly responds.

Hand off page

Choosing Hand off page transfers edit control without changing roles or publishing. If the current editor has unsaved changes, Save & hand off passes the saved revision, while Discard & hand off transfers the last saved version. The receiving editor then syncs the latest page state before continuing.

Take over

When MCP owns the page, a human editor can choose Take over. This moves the page lock, invalidates the MCP write token, and syncs the latest changes. Coordinate first whenever possible so both editors understand which revision is authoritative.

Avoid conflicts

Divide work by page, not by simultaneous unsaved changes to the same page. Keep short, meaningful save points; identify dependent global changes; and pause connected release work until the responsible page owner confirms readiness.

Separate save and publish ownership

The person editing a page does not automatically own publication. Name the final reviewer and authorized release owner, especially when several drafts, the Navbar, Footer, theme, or presets must ship together.

Screenshot limitation

No privacy-safe active lock or takeover state was available for this guide. The image documents collaborator scope only; it must not be treated as proof of lock behavior.

Collaboration checklist

Assign the smallest useful role. Divide work by page. Use Request edit instead of overwriting. Save before choosing Hand off page. Describe unfinished work. Transfer control explicitly. Reload after receiving it. Keep release ownership clear. Verify the live result only after an authorized future publication.

Next steps

Use Add Collaborators from the Dashboard for site invitations and Content Workflow for review and release scope. When another editor owns a page, use Request edit and coordinate the handoff rather than changing permissions.