Real-time co-authoring

Multiple editors in Word Online at the same time — with every edit, comment, and @mention captured for audit.

Collaborative authoring used to mean emailing Word files around with color-coded tracked changes and hoping nobody worked on the wrong version. Microsoft 365 fixed the technology years ago — Word Online lets multiple people edit the same document simultaneously, see each other's cursors, leave comments, and @mention each other. docs365.ai takes that native capability and wraps it in the compliance fabric: every co-authoring action flows to the audit log, every version transition is captured, and the document never leaves the governed library.

Stage 1 · Create Business: Included Enterprise: Included Premium: Included Diamond: Included

✓

Illustration placeholder

At a glance

What you get

Four properties of Word Online's co-authoring become valuable in a compliance context when the product wraps them in versioning and audit. Without the wrapper, they're productivity features; with it, they're evidence-generating workflows.

Multiple editors simultaneously

Two, five, ten people in the same Word document at once — native Microsoft 365 capability, no conflict resolution needed.

Live presence and cursors

See who's in the document, where their cursor is, what they're typing — in real time.

Comments and @mentions

Review comments and @mentions flow through Outlook notifications; resolutions are captured as metadata.

Every edit to the audit log

Co-authoring activity, version transitions, and comment resolutions are all logged against named identities.

How it works

From draft to approval-ready

Co-authoring is the native Word Online behavior — no additional plugin, no separate collaboration tool. The DMS simply hosts the document in SharePoint and lets multiple authors open it at once; everything they do is captured in the version history and the audit log.

Document opened in Word Online

The library's context menu opens the document in Word Online directly — desktop Word works too, with the same co-authoring behavior.

Multiple authors edit in real time

Each author sees the others' cursors and edits live; conflicts are resolved automatically by Microsoft 365's sync engine.

Comments and @mentions route through Outlook

Review questions and assignments are surfaced in the authors' inboxes; resolutions are captured on the document.

Minor versions preserve every state

Each save creates a minor version; the draft is fully traceable from first keystroke to final approval submission.

Before / after

What changes when this is on

The authoring failure modes most compliance programs fear — lost edits, overwritten versions, unauditable changes, review comments that vanish — are all solved by the combination of real-time co-authoring and the DMS governance layer.

Without it

With intranet.ai

✗ Emailing Word files with tracked changes; hoping nobody works on the wrong version

✓ Everyone edits the same canonical document in real time; there is no "wrong version"

✗ Two authors working on parallel copies; merging changes manually at the end

✓ Microsoft 365 sync handles merging automatically; conflicts are resolved live

✗ Review comments scattered across email threads, Teams chats, and sticky notes

✓ Comments live on the document; @mentions route through Outlook; resolutions are captured on the page

✗ No audit trail of who contributed which section of a draft

✓ Every edit is logged to a named identity; the minor-version history reconstructs the whole drafting arc

Availability

Plan availability

Co-authoring is a feature of Microsoft 365 itself, not an add-on. Every DMS plan inherits it natively — the product's value is the audit-log wrapper and the versioning discipline, not the co-authoring mechanics.

business

enterprise

premium

diamond

✓ Included

Real-time co-authoring is a native Microsoft 365 feature — every DMS plan inherits it. Our value is the audit-log capture and versioning discipline applied on top.

Keep exploring

Related features

Co-authoring is the creation-stage complement to templates, versioning, and the audit log. These three features define how collaborative drafts move toward approval.

Stage 1 · Create

Document templates

Every document starts from a controlled, approved template — consistency baked in from the first keystroke.

Stage 4 · Govern

Versioning

Minor versions while drafting, major versions at publication — every state preserved, every version recoverable.

Stage 2 · Approve

Sequential approval

Named approvers, in defined order, with role-based routing — every step logged, every version tied to the approvals that produced it.

Deep dive

Read the full narrative

For the buyer who wants the full detail — compliance context, edge cases, adjacent workflows.

Multiple colleagues on the same document — with @mentions, comments, and full version history.

Drafting a procedure or policy is rarely a solo activity. The person closest to the work writes the first draft, the quality team reviews, legal comments on specific clauses, the manager adds operational context. Traditionally that dance happens across email attachments — version conflicts, missed comments, lost context. Since the product’s documents live in Word Online on SharePoint, it happens in one place, in real time.

Simultaneous editing, one source of truth

Multiple colleagues can edit the same document at the same moment. Each active editor’s avatar appears in the document header. A small cursor indicator shows exactly where each person is typing. Changes appear in the shared document as they’re made; nobody is working on a private copy they’ll merge later.

In-document comments with @mentions

Reviewers highlight specific passages and leave comments attached to that passage. @mentioning a colleague by name notifies them and pulls them into the review. Comment threads support back-and-forth discussion, replies, and resolution. When an issue is fixed, the thread is marked resolved — not deleted — so the resolution history is preserved for later reference.

Every change preserved in version history

Because the document is a SharePoint file, every save is a version in the history. If a colleague accidentally deletes a section, the previous version is recoverable in a couple of clicks. If a regulatory change requires rolling a document back to a prior state, the prior state is retrievable. The version history also serves as the audit artifact for ISO 9001 surveillance and similar review contexts.

No email attachments, no version conflicts

The operational benefit is immediate: nobody emails a file to anybody. Nobody ends up with four copies of the same document on their laptop, each with different edits. Nobody has to reconcile three colleagues’ edits by hand. The draft is the draft, everybody is looking at the same version of it, and the activity is captured in the version history.

Works in Word Online and Word desktop

Co-authoring works whether collaborators are editing in Word Online (the browser-based version) or in the Word desktop app. Changes sync automatically across both; a colleague editing in the desktop app sees changes a colleague is making in the browser, in real time.

Who can edit — permissioned per library

Co-authoring is governed by SharePoint permissions at the library level. The editing area of a Document Management zone is visible only to people with edit permission — typically the document owner, co-authors they invite, and reviewers from relevant teams. End-users who consume published documents don’t see the editing area; they see only the approved PDF in the public area.

What this feature prevents

Version conflicts. No more “I made changes to v3, but Sara emailed me v2 with her changes — whose edits win?”
Lost comment threads. Email replies scatter; in-document comments live with the document.
Offline drift. A draft edited offline and not re-synced is a source of silent divergence. Co-authoring keeps everyone on the shared current state.
Accidental content loss. Every save is a version; revert is always available.

Template-driven creation — co-authoring starts from a governed template.
Versioning — every change preserved, every version recoverable.
Sequential approval — once co-authoring is done, the document moves into the structured approval flow.

Lifecycle stage: Create →

Deep dive · Pillar guide

The active document lifecycle on SharePoint Online

Why passive document management fails — and what an explicit four-stage lifecycle looks like in practice inside a Microsoft 365 tenant.

22 min read · 5,200 words

Read the full guide

See this feature running on your documents

Thirty minutes. No cost. No obligation. We'll walk through how real-time co-authoring fits into your current document-governance practice.

Book a free assessment or see all features