Could several users edit the same document?¶
Yes. Several users and applications may contribute to one live cloud document, sometimes concurrently. To attribute a disputed change, reconstruct the participants, permissions and revision record for that content and time.
Build a contribution map¶
Identify direct users, group members, guests, link-based editors and connected applications. Historical access matters: somebody removed today may have held edit permission when the relevant version was created.
Then distinguish contributions such as direct edits, comments, suggestions, accepted changes and automated imports. A final paragraph may have been suggested by one account and accepted by another; both events are relevant.
Match the passage to the revision¶
Some providers retain detailed change attribution. Others combine autosaves or concurrent work into one version. Preserve object and version IDs, revision times, recorded editors, comments and audit/correlation IDs.
Where a particular passage matters, compare the version before and after it appeared. Session, device and communications evidence can then connect the recorded account to a person and explain the surrounding work.
Collaborative authorship explains why the owner or latest editor is not the author of the whole document. This card's narrower question is who contributed the relevant change.
State contribution precisely¶
“Account C-77503 proposed paragraph 12 and account C-54119 accepted it” preserves more information than “C-54119 wrote the document”. Where the provider groups revisions, state that limitation rather than assigning every change to the displayed editor.
In Word for the web, Priya's account C-66308 creates suggestion SUG-22 for paragraph 12 of object OBJ-4407. Dave's account C-77503, in session SES-41C2, accepts it in event ACC-24; autosave then records version V-19 under editor account C-54119. The suggestion and acceptance records can establish distinct contributions even though the version checkpoint alone groups them.
The next useful comparison is the precise changed range and suggestion/acceptance history against V-19, participant permissions, account sessions, device activity and communications about paragraph 12.
Current Microsoft collaboration example - checked 3 September 2026
Microsoft Graph represents file versions as driveItemVersion resources and may identify the user who last modified a version. That version-level actor should be read alongside any more detailed application revision or audit records rather than treated as authorship of every change grouped into the checkpoint.
The point to remember
In a collaborative document, attribute the relevant passage or revision - not the whole file - using historical permissions, revision detail, sessions and corroborating records.