Shared Team Folder Access Controls

The Access Anywhere admin, or a member who has the admin role, can manage access to any Shared Team Folder. This means that they can control who has access to a Shared Team Folder and can grant access.

Any organization member who has been assigned a role that has the “manage Team Folders” permission can also manage access to any Shared Team Folder and can grant access.

An organization member to whom the “Manage Permissions” privilege has been assigned for a Shared Team Folder, either directly or because the organization member has been assigned a role that has this privilege, can manage access to that folder.

Access to each Shared Team Folder can be granted to individual organization members. Access to each Shared Team Folder can also be granted to roles, in which case the access privilege applies to every organization member to whom the role has been assigned, subject to these two rules:

1. Access privileges granted to the individual organization member supersede privileges granted to a role that has been assigned to the organization member.
   
   
2. When an organization member has been assigned two or more roles and the roles have different access privileges for a folder, the most permissive access level prevails.

Each folder also has a default access level. This is the access level that is applied to organization members to whom no other access level has been assigned either directly or through a role.

When a Shared Team Folder is created, either as a new folder or by converting an existing folder, any folders beneath that folder in the directory tree inherit whatever permissions are applied to that folder (but not necessarily the permission modifiers, which are discussed later in these notes). If permissions are changed on the Shared Team Folder then the folders beneath it inherit the changes.

Unlike other solution permissions can be broken within the sub hierarchy of the tree. Permissions can be changed by a user with the appropriate authority on folders that are beneath a Shared Team Folder in the directory tree. When this happens, the folder on which permissions were changed becomes what we term as a 'Managed Folder'. At the moment that a folder becomes a 'Managed Folder' it stops inheriting access permissions from the folder above it in the directory tree, and changes to the permissions on its parent folder’s permissions no longer apply to the newly created Managed Folder.

A new 'Managed Folder' allows no access to any users or roles except those granted by the user who created the 'Managed Folder' by changing a permission. The new 'Managed Folder’s' default access level is copied from its parent folder at the time the Managed Folder is created and can be changed independently of the parent folder’s default access level.

Permission modifiers provide more granular control over permitted operations. This table summarizes how the permissions modifiers are used:

This table summarizes what they do:

Some modifiers are mutually exclusive:

• Create Shared Links and Web View Only cannot be used together
• Neither Create Shared Links nor Web View Only can be used with List Folders.

Please note that as of v2106.00, the Read/Download modifiers now inherit down to subfolders.

The Modify Structure permission modifier is also new in version v2106.00. It allows users to rename subfolders, and to delete subfolders, their descendant folders and the shared folder itself. It also makes the “Create subfolders” modifier available. If that modifier is set then users can also create subfolders.

As an advanced example, how can we grant a user or group access to specific subfolders within a private subfolder?

First, grant the use “List Folders” permission on any parent folders they don't have access to. This will allow the user to navigate to the subfolders they'll have access to, but not access any content. (If this is not desirable Business Groups or Shared Folders may be a better fit). If there are multiple parent folders recognize you can also use Permission Inheritance as described above.

Then grant access as desired for each of the subfolders. Note that any inherited permissions will be lost when the subfolder permission is added. If still needed they can be explicitly added to the subfolder as well.

You can also disable “List Folders” access for other subfolders within that parent folder (or other parent folders):

Org. members who have been assigned the Admin role or a role that allows both managing Shared Team Folders and managing Team Clouds will see Shared Team Folders that were created by other members and to which the member with the relevant role was granted access either in the root directory of the org. member with the role or inside the provider on which the shared team folder was created depending on how the directory tree is navigated.

A combination of Web View only access permissions combined with document watermarking provides effective Data Loss Prevention for sensitive documents.

Org. admins can create reports showing the permissions that have been granted on Shared Team Folder.