default inheritance when creating new folders

#Default inheritance when creating new folders full#

File-level permissions are more difficult to manage, as it can be hard to identify when an individual file breaks inheritance. It is recommended that most sites start with folder-level permissions, which strikes a good balance between ease of maintenance and flexibility of configuration. How permissions are actually configured for folders and files, and for particular users and groups, is discussed here. It is important to note that only Site Administrators and Content Administrators can alter the permissions assigned to a site, folder or file and only those users can modify inheritance. For example, GroupA may have view-only rights on Parent Folder but edit rights on the 'M&A Agreement' in that folder. By default, files will inherit the access rights associated with the folder they reside in, but that inheritance can be broken. It is similar to the site & folder permission level, but permissions can be granted all the way down to the individual file level.

Site, Folders and Files (also known as file-level) - This is the most granular permission level, and also the hardest to maintain.

#Default inheritance when creating new folders full#

GroupB may have view rights on Parent Folder but full folder administrative rights on Child Folder. For example, GroupA may have edit rights on Parent Folder but only view rights on Child Folder. Subfolders will inherit the access rights of the parent folder by default, but that inheritance can be broken by restricting or enhancing who can access the subfolder or what types of access rights those users have. Any access rights that are provided to a group for a given folder will apply to all of the files in that folder.

GroupB can be given completely different rights to those same folders: edit rights on Folder1, no rights on Folder2 and view-only rights on Folder3. For example, GroupA may have view-only rights to Folder1, edit rights to Folder2, and no rights to Folder3. Site and folders (also known as folder-level) - With this setting, different groups (or users) can be granted different types of access rights to different folders.On the other hand, GroupB may be given view-only access rights, and those rights will apply to every file and folder on the site. For example, if GroupA is given edit access rights, it will have those same rights to every file and folder on the site. All of these rights will be applied consistently across the entire Files module. (If a group is not granted even file view access, then that group should not be given access to the Files module at all.) However, some groups or users may have additional rights, like the ability to add or delete files and folders. As a result, every user who has access to the Files module can, at a minimum, view every file in the site. In other words, every folder and file inherits the permissions of the ultimate parent folder. Site only (also known as site-level) - With this setting, the same permissions will apply to every file and folder in the site.

This determination should be made based on the requirements of a given site. File and Folder PermissionsĬhoose the level at which permissions will be set in the Files module. Once a change has been made to this page, make sure to hit Save or any changes that were made will not be saved. The Files admin page is used to configure the corresponding Files module, the key content area of most sites.