A Folder Admin can maintain access and supported settings for selected folders without administering the Site's users or integrations as a whole. The grant includes all folder permissions, so it also gives full access to the files within its scope. Choose it for someone trusted both with those files and with decisions about who else receives them.

Administrative Scope

Folder Admin permission is recursive: it applies to the selected folder and its subfolders. It includes permission to change folder grants, supported Folder Settings, notifications, and v1 Automations. A smaller file-access grant does not narrow that authority, and a Permission Fence does not remove inherited Folder Admin authority.

Folder Admin access alone does not provide user management, Group membership management, site-wide policy changes, or general administration of Remote Servers and Syncs. Those capabilities require their own grants. Workspace Administrator access is appropriate when the responsibility includes the team's users, connections, and workflows together.

Directory Visibility

Folder Admins control permissions, supported folder settings, notifications, and v1 Automations for the folders they administer. They can see all users and groups on the site, including people and groups that have no access to those folders. This directory visibility is intentional: an administrator must be able to find the people and groups to whom they want to grant access or assign notifications.

A folder's permission list is not a filter on the user and group directory. Grant Folder Admin access only to someone who may see that directory. Seeing an account or group does not itself grant permission to edit it, change its membership, or read its files elsewhere. Those actions require their own permissions.

Inherited Permissions and Settings

Ancestor visibility depends on recursion. For permission records, Folder Settings, and notifications, a record on an ancestor folder, including the site root, is visible through a descendant only when it is recursive and its scope reaches a folder the Folder Admin administers. Non-recursive records and records whose scope does not reach those folders are not included through ancestor visibility. This lets Folder Admins understand inherited access and rules affecting their folders.

Folder Admins can see permission records on their administered folders and all subfolders, plus ancestor grants that meet this recursion requirement. The records include permissions assigned to other users, groups, or Partners. Seeing an ancestor's grants does not grant access to that ancestor's files or permission to change its grants. Permission records on sibling folders and unrelated branches remain outside the Folder Admin permission's scope unless the user also administers those folders.

The web app's Permissions tab focuses on the selected folder and lists applicable ancestor grants under Inherited. The REST API permission list follows the same administrative scope and recursion requirement. Site Administrators can see every permission on the Site.

Workflow Authority

A Folder Admin can configure and start v1 Automations on administered folders. The workflow's owner determines the permissions used for its file operations, and an edit by a Folder Admin changes that ownership. Automations v1 explains those execution and lifecycle rules.

A v1 Run Sync Automation can start configured Syncs within its Workspace without giving the Folder Admin permission to view or change those Syncs. Starting a configured transfer uses the Sync's execution authority. Syncs explains the selection boundary and why that ability matters when granting Folder Admin access.

Folder Admin access does not grant administration of v2 Automations; those use Site and Workspace administration. Notification recipients and Share Links can also have lifetimes independent of the Folder Admin's own access. Access Revocation explains what must end separately when a person's responsibility changes.