Skip to content
Skip to main content
Cloud Services Technical Explainer

What is a shared folder?

A shared folder is a cloud folder to which more than one account, group or guest has permission. Sharing creates capability; it does not make every permitted user the owner, uploader or author of every file.

Permissions define what each participant could do

Typical roles include viewer, commenter, editor and manager or owner, although providers use different names. Permission may be granted directly, inherited from a parent folder, supplied through group membership or reached through a shared link.

A current membership list is only a snapshot. To understand an event at 15:20 on Tuesday, the relevant question is who held what permission at 15:20, including invitations, removals and role changes.

Account Permission at event time Recorded activity
C-54119 Owner Created folder and invited group G-17
C-77503 Editor through G-17 Uploaded object OBJ-4407
C-66308 Viewer No access event retained

The table supports different conclusions for each account. Ownership, permission and action should not be merged.

Dave is account C-77503 in group G-17. At 15:20, OneDrive accepts upload event UP-204 for object OBJ-4407 through Dave's signed-in session. The folder owner created the place and the group supplied capability; the upload record is the event that connects Dave's account to this object change.

Permission explains capability; the object event shows what happened
EstablishedThe permission history and upload event distinguish who could act from the account recorded acting on this object.
Still openWho controlled the session and whether unretained activity occurred.

Folder activity can spread to devices

An editor may upload a file that synchronises automatically to other members' devices. A local copy on a viewer's laptop can therefore reflect folder membership and background sync rather than a manual download. Conversely, provider access or edit events may demonstrate later interaction.

Deletion may remove the managed object while independent downloads, caches, versions or backups remain elsewhere.

Read the record at the correct level

Provider evidence may identify the folder owner, membership source, permission history, object uploader and account associated with an event. It may not identify the human controlling that account.

Useful wording distinguishes:

  • permission to access;
  • recorded access;
  • upload or edit of a particular object; and
  • personal attribution for that event.

The next useful records are the historical group membership, permission grant, object event and the account session or device that submitted it.

Current Microsoft shared-folder record example - checked 3 September 2026

Microsoft Graph currently represents access to a drive item through permission resources. A permission may describe a user, group, application, sharing link or invitation, and inherited permissions may be associated with an ancestor rather than created directly on the item. Preserve the returned permission IDs, roles and inheritance context because product labels and interfaces can change.

The point to remember

A shared folder separates capability from action. Reconstruct permissions at the relevant time, then use object, event, session and device records to establish who actually handled the material.

Reference: CLD-061Cloud Services