Shared edit experience. I am thinking of a google docs esqueue edit experience. Chat sidebar allows colab convo in session. Convo and session details can be stored for retrieval later and users can take chat and dump in a jira ticket or email or whatnot. If session is closed, they get a read only view of chat and diff of changes view that they can link/export to jira or other resource as needed.
An editor initiates a live collaboration session on a draft item( checked out and generates a colab/live draft session link).
Session initiator adds expected users to join session. When these users follow link they join shared session. If not allowed they get a you can't join this session contact message to get into session. Potentially they can designate other users as approvers that gives them the ability to close with approve
The initiator shares a session link (e.g. via Teams) — invited editors join and all edits happen in real-time. The live edit link page has user verification with a link between users and sessions table.
Check-in is locked for everyone while the session is active — no version can be created mid-session
Closing the session with Approve or Reject works as follows:
Approve — accepts all changes made during the session; draft is updated and check-in re-enables. Only the session initiator can approve.
Reject — rolls back all changes to the pre-session draft state; no edits are applied. Any participant can reject (e.g. if the initiator is unavailable or removed), and any user with content admin rights can also force-reject an orphaned session. Could still record the chat/changes to allow users to talk about and look at rejected changes.
Auto-timeout reject — if the session has been inactive for a configurable period (e.g. 30 min of no edits and no active participants), it automatically closes with reject. This prevents a draft being locked indefinitely because someone closed their browser without ending the session
- OR a special versioning where it isn't checked in but current state saved so user can open link and continue from saved point and never auto closed.
This design gives the initiator approval authority while ensuring no session can block the workflow permanently — reject is always reachable regardless of who initiated it while taking in the changes would be only approvers.
If page checkout was rejected then, colab session is also closed with reject.