What is a synced folder?¶

A synced folder is a device folder that a cloud client maps to an account and provider location. Changes inside it can be uploaded, while cloud changes can create, alter or remove local items automatically.

One folder belongs to two evidence systems¶

On the device, the folder has a local path, filesystem records and application activity. In the cloud, it relates to a tenant or account, folder and object identifiers, permissions and provider events. The sync client keeps the mapping between them.

That mapping matters more than the visible folder name. Two devices may both show Cloud Drive\Projects, but each can use a different account, selected-folder setting or local path.

Dave's Surface Laptop maps its local Projects path to OneDrive folder F-2804 under account C-54119. The client record links local path LP-17, device DEV-A and provider folder F-2804. A second laptop has a folder called Projects, but its mapping points to account C-77503; the matching name does not make it the same sync relationship.

The folder can contain different local states¶

At the same moment it may contain:

• full files downloaded to the device;
• offline cloud files retained for disconnected use;
• placeholders that retrieve content when opened;
• temporary previews or cache entries; and
• local changes waiting to upload.

The icon shown by the client may indicate state, but preserve the underlying application database or logs where possible. An icon can change after synchronisation resumes.

Local presence may be a propagated event¶

If another device uploads object OBJ-7712, the client can create a local copy without the local user selecting or opening it. Its filesystem creation time may describe arrival on this device. The synchronisation chain is needed to identify the originating change.

The same applies to deletion. Removing an item in the mapped folder may request cloud deletion and propagate to other devices, while moving it outside the folder may create a detached local copy.

Establish the mapping and relevant state¶

Useful records include the signed-in account, provider folder ID, local path, client/device ID, selected folders, offline settings, last successful sync and queued or failed transfers.

The next useful comparison is the mapping record against the first local write, provider acceptance event and later transfer entries. That sequence distinguishes a local origin from automatic arrival.