Every time a user creates a folder, it will initially be set to inherit permissions from the folder above it. This includes the role-based permissions from the folder and any group or class based permissions that exist.
If the folder above is also inheriting permissions, then it creates a linked chain in the folder structure. The inheriting effect is ongoing, so if you make a change to the permissions or group membership of one folder in the chain, it will apply to all folders below it.
Folders that are inheriting permissions cannot hold their own group or class code because these are different ways of allowing permissions that might contradict the inherited permission.
If you need to customise the role-based permissions for your new folder:
1. Deselect the 'inherit permissions' check box.
2. Set the role-based permissions that you would like for your new folder.
NOTE: You will also need to deselect 'inherit permissions' in order to create a new group or add a new class code.
When a Superuser creates folders in bulk, they will choose whether to set role-based permissions for the folders or to inherit permissions from the folder above.
Modifying Permissions on an existing folder
1. Navigate to the Resource Browser.
2. Check the permissions by selecting 'Modify'.
3. From this screen, you can modify the folder name, details and existing permissions.
4. If you want to apply the selected role permissions to folders beneath that aren’t currently inheriting permissions, you can select the 'Apply to subfolders' checkbox. This will act as a one-off change to the role-based permissions, but will not modify any groups or class codes on the subsequent folders. Any user with write access will subsequently be able to change the role based permissions for any single folder in the structure without affecting any other folders. This might be used to ensure all the folders in a particular branch have been given the same folder based permissions even though they may have groups or classes attached.
Ticking both the “Inherit permissions” and “Apply permissions” checkboxes links the folder and its sub-folders in the ongoing “Inherit permissions” chain. All subfolders will continue to inherit folder permissions, group access, and class codes, including any changes to those items, from the top folder in the chain. This will remove any groups or class codes attached to the subfolders in the chain. But, is useful in creating a single branch of the folder structure with access for a particular set of users.