Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
shared/team/folders/access/controls [2018_07_27 08:42] – created danshared/team/folders/access/controls [2020_05_11 17:44] – [Inherited Permissions and Managed Folders] steven
Line 1: Line 1:
 #Shared Team Folder Access Controls #Shared Team Folder Access Controls
 +
 +{{ youtube>9J6Zr-6OjaY?medium }}
 +
 +####Last updated: Nov. 28, 2019
 The org. admin can manage access to any Shared Team Folder.  This means that he can control who has access to a Shared Team Folder, and he can grant access to himself. The org. admin can manage access to any Shared Team Folder.  This means that he can control who has access to a Shared Team Folder, and he can grant access to himself.
  
Line 15: Line 19:
  
 ##Inherited Permissions and Managed Folders ##Inherited Permissions and Managed Folders
-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.  If permissions are changed on the Shared Tea Folder then the folders beneath it inherit the changes.+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.
  
 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 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. 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 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.
  
-Permission modifiers such as "Create subfolder", "Upload files", "Rename", etcare not inherited.+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 
 + 
 +Permission modifiers provide more granular control over permitted operationsThis table summarizes the permissions modifiers: 
 + 
 +{{ ::stf_permissions_modifiers.png?direct&400 |}}
  
-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 +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 Only//