A Sync is a configured transfer between a source and a destination. Permission to configure that transfer, permission to start it, and permission to browse its files directly are different. An access review needs to establish what the Sync can read or change and who can cause that work to run.

Configuration and Execution Authority

Syncs belong to the Site or Workspace, rather than to the user who created them. Site Administrators can view, configure, start, dry run, and delete every Sync on the Site. Workspace Administrators can perform those actions for Syncs within their Workspace. Folder Admin permission alone does not grant those Sync administration operations.

The administrator who configures the Sync chooses its source, destination, filters, and transfer behavior. Starting it uses that configured transfer's permissions and connections, rather than the personal folder permissions of the person who starts it. Removing the creator's administrative grant does not remove the Site-owned or Workspace-owned Sync.

Control over a destination is control over where the files are delivered. Control over source cleanup can also permit file deletion. Choose Sync administrators for the data and connections they are trusted to manage, even when their daily work does not involve opening the files themselves.

Connected Storage and Other Sites

A Remote Server connection supplies the remote account's permissions. The source needs list and read access; the destination needs list and write access, including replacement where required. Source deletion requires separate permission when the Sync's After Copying setting removes source files. Sync Configuration explains the remote permissions and the cases requiring destination deletion.

A Sync using files on another Files.com Site still follows that relationship's access checks. Connected Sites require the Host Partner's permissions; a Files.com Remote Server uses the paired credential. Folder Settings and content restrictions also depend on the route. Access Across Sites and Storage explains those combinations. Starting a Sync does not supply a missing permission on the other Site or storage system.

Starting a Sync Through an Automation

A v1 Run Sync Automation lets a Folder Admin select any configured Sync in the Automation's Workspace, including Syncs they cannot view or manage directly. It cannot select a Sync in another Workspace. This permits starting a transfer without giving its operator control over the transfer's configuration.

For example, a Folder Admin maintaining an intake workflow can configure it to start a Sync in the same Workspace that delivers files to a destination outside that administrator's own folder access. The Sync uses its configured authority. The Folder Admin does not gain permission to browse that destination or edit the Sync. Include the ability to initiate these configured transfers when deciding who may administer folders in the Workspace.

The Automation's success records that the Sync was initiated; it does not establish that the transfer completed. Sync runs have their own run and file records. Use those results when a later process depends on delivery.

Ending Transfers

Removing a user's folder permissions or administrative access does not disable a configured Sync. When the intended outcome is to stop transfers, disable the Sync and review any Automations or schedules that initiate it. When retiring a remote connection, also review its credentials and other workflows using it. Access Revocation explains why ending a person's access and ending configured work require separate decisions.

The Syncs guide explains source and destination selection, configuration, triggers, and transfer behavior.