What is a file owner in a cloud service?¶

A file owner is the account, tenant or organisation to which the cloud service assigns primary control of an object. Ownership usually governs administration - such as sharing, transfer or deletion - not authorship of the content.

Ownership arises in different ways¶

The recorded owner may have created or uploaded the file. Ownership may instead be inherited from an organisational workspace, transferred by another user, reassigned when staff leave or allocated automatically to the owner of a destination folder.

Provider models differ. A consumer service may assign ownership to one personal account. A managed tenant may treat the organisation as owner while an individual account is recorded as creator or uploader.

Current control is not historical activity¶

An ownership record can show who could manage the object at a particular time. Permission and ownership history may show transfers, administrator action and changes in control. It does not establish who opened, edited or even knew about the file.

Useful records separate:

• current and previous owner;
• tenant or workspace;
• creator or uploader, where recorded;
• ownership-transfer event and actor;
• permissions held by other accounts; and
• version and access activity.

An offboarding transfer may be routine. Its timing and business record can explain why an account became owner without suggesting that its user created the material.

Dave uploads handover.docx to OneDrive object OBJ-5510 while account C-77503 owns the personal drive. When Dave leaves, administrator ADM-17 transfers control to Priya's account C-66308 in event OWN-204; version V-7 and its content do not change. The transfer establishes a new administrative relationship, not new authorship or use.

Use ownership for the proposition it supports¶

Ownership identifies provider-recorded control. Whether it proves authorship is a separate question answered through version, upload, session and device evidence.

The next useful comparison is the ownership-transfer event against the unchanged version or hash, earlier creator/upload record, later access history and the organisation's offboarding record.