Coauthor Office Files

Office coauthoring in SynckHub depends on deployment policy and Microsoft integration setup.

What is supported

  • Coauthoring targets FILE items (Word, Excel, PowerPoint workflows).
  • Availability is deployment-specific:
    • enabled and configured
    • disabled (feature unavailable)
  • Federated items are not supported for coauthoring in v1.

If coauthoring is unavailable, use standard file editing with version history.

Safe working flow

  1. Open the Office file from SynckHub.
  2. Start coauthoring through the provided Office action.
  3. Collaborate in real time with other participants.
  4. Finish session and confirm content is persisted back to SynckHub.
  5. Re-open file in SynckHub to validate final state.

What happens under the hood

  • SynckHub creates a coauthoring session and applies lock policy to prevent conflicting edits.
  • During session lifecycle, working content is synchronized back to SynckHub according to integration policy.
  • Session cleanup releases locks and removes temporary working artifacts best-effort.

Operational cautions

  • Treat generated edit URLs as sensitive capability URLs.
  • If a session appears stuck, ask an admin to resolve lock/session state.
  • Do not run parallel non-coauthor edit workflows on the same file.

Failure modes and user actions

  • Feature not configured: use normal edit/version workflow.
  • Access denied: request the correct write-level permission.
  • Conflict/lock issue: wait for session release or have an admin intervene.
  • Upstream Office integration issue: retry later and avoid partial manual workarounds.
  • restore-previous-version.md for recovery.
  • share-folder-or-file.md for access setup before collaboration.