Real-Time Co-Authoring & Conflict Handling

Agility's Live Collaboration provides genuine real-time, multi-user co-authoring: multiple editors can work on the same content item at the same time. Changes appear live as colleagues type, and conflicts are prevented at the field level: while one editor is focused in a field, that field is locked for everyone else, so two people can never overwrite the same field simultaneously. Editors see who else is in the item, which fields they occupy, and when they are actively typing. Because edits propagate in real time, there is no "discover the clash later" problem — and in the rare case where an item was saved by someone else since you made local changes, Agility notifies you to reload (changes you would already have seen reflected live).

Working on the same item simultaneously

Agility provides real-time co-editing. When more than one editor is active on the same item, the experience is collaborative and live:

• Real-time edits. Changes made by one editor appear to the others as they happen — no manual refresh, no waiting for a save.
• Presence at the top of the screen — see who is currently online in the instance.
• Same-item awareness — if someone is working on the same item as you, their presence is shown with a highlighted (yellow) frame and a message identifying who is there.
• Field-level presence and typing indicators — each active editor's avatar appears on the field they're in, with a typing indicator when they're actively editing, so you can see exactly which field a colleague occupies and when they're typing.
• Live cursors in Web Studio — you can see collaborators' mouse movements in the Web Studio preview, making concurrent work feel real-time.

Live change reflection and collaboration

• Comments and threads update live — editors can comment, reply in threads, react with emoji, edit their own comments, and mark items resolved without leaving the item.
• @-mentions notify a teammate and deep-link them to the exact item and comment.
• Commenting Mode in Web Studio lets editors drop comment bubbles directly on elements in the live preview.

(See Live Commenting & Collaboration in Web Studio for the full commenting workflow.)

Conflict, overwrite, and collision handling

Agility prevents conflicts rather than resolving them after the fact, using two complementary mechanisms:

1. Field-level locking. While an editor is focused in a field, that field is locked for all other editors. A second editor cannot type into a field someone else is actively editing, so simultaneous overwrites of the same field are impossible by design. Editors continue to work in parallel on different fields of the same item.
2. Real-time propagation. Because edits are streamed live, every collaborator sees changes as they are made. There is no window in which an editor is unknowingly working against a stale copy of a field.

Reload notification for stale local state. If another editor saves the item while you have it open, Agility shows a notification — "[User] has made changes to this item" — with Reload (load the latest saved version) and Ignore options. In practice you would already have seen those edits reflected in real time, so the prompt is a safeguard, not a surprise.

Recovery safety net. Beyond prevention, every change is captured in version history (who changed what, and when), so any item can be reviewed and reverted to a prior version if needed.

Shared responsibilities

Area	Agility	Implementation partner / customer
Presence, live cursors, field awareness	✅ Built into Content Manager / Web Studio	—
Live comments, mentions, reactions, resolve	✅ Built in	—
Version history & revert (overwrite recovery)	✅ Built in	—
Editorial process to avoid clashes	—	✅ Defines team conventions (who owns which sections/items), workflow states, and approval gates
Web Studio preview enablement	✅ Provides Web Studio	✅ Configures the site/security settings so Web Studio preview works