Non-Inherited Permissions

Overview


Egnyte folders under the Shared folders automatically inherit permissions from their parent folder. When you add a permission for a user to a Shared folder (e.g. /Shared/Project) that permission will also apply to any of its sub-folders (e.g. /Shared/Project/budget) unless there is a more specific permission for that user on the sub-folder. While this is helpful most of the time, there are cases where you may want folders to be locked down so that permission changes to a parent folder won’t affect the child folder.

Egnyte now supports non-inherited permissions. Administrators or Power User folder owners can now mark a folder so that it does not inherit permissions from its parent.

Viewing the Permissions Inheritance Status

When you open the folder permissions dialog you can see the inheritance status for the current folder:

folder_perm.png

Note: This section does not show for private folders or for the folders directly beneath /Shared, since neither of these folders can inherit permissions.

 

Turning Off Permissions Inheritance

Administrators and folder owners can change the inheritance status for a folder. After clicking Turn off inheritance at the top of the folder permissions dialog, you can choose how you would like to treat the existing inherited permissions.



When choosing Remove inherited permissions, all existing inherited permissions will be removed and only permissions that were already set on the current folder will be maintained.

When choosing Keep existing permissions, any existing inherited permissions will be copied to the current folder after disabling inheritance. This can be helpful when you want most of the users from a parent folder. This allows you to start off with the current list and then remove the users who shouldn’t have access.

 

Turning Permissions Inheritance Back On

If you've turned off permissions inheritance for a folder, you can re-enable permissions inheritance by clicking the Turn on inheritance link in the permissions dialog.

 

Non-Inherited Permissions FAQ

Why can't I see permissions inheritance status for folders directly beneath/Shared?
Folders directly under Shared (e.g. /Shared/Projects) never inherit permissions since permissions cannot be set directly on /Shared. This means that the option is not relevant for these folders.

Who can change the permission inheritance status for a folder?
Admins and folder owners can turn on and off permissions inheritance for any eligible folder.

Does the non-inherited state get inherited to sub-folders?
No, folder inheritance has to be set on each individual folder. Usually, when you turn off inheritance for a folder and give that folder permissions you want the users with access to also have access to the sub-folders. When you turn off inheritance to a folder /Shared/Finance/budget its sub-folder /Shared/Finance/budget/Q2 will inherit permissions from the budget folder. If you want to, you could disable inheritance for the Q2 folder as well. 

Why do some users still have access to a folder after I disable permissions inheritance?
Any permission that was already set directly on the folder (not on the parent folders) will remain. Also, if you choose to keep existing permissions then a copy of the parents permissions will be copied to the folder.

What happens when I copy or move a folder that doesn't inherit permissions?
When you choose to keep source permissions the folder will retain its non-inherited permissions state. When you choose to use destination permissions then the folder will inherit permissions from the new destination folder.

Do I need a specific version of Storage Sync or other Egnyte applications to use non-inherited permissions?
No, Non-Inherited Permissions work with all the existing versions of Egnyte applications, including Storage Sync.

 

Egnyte Community

Egnyte Community

Want to connect with other Egnyte users and our Egnyte team? Share ideas and ask questions in our Community .