1. Home
  2. Account and Permissions Mapping
  3. Scenario: Preserve File Structure, Restrict Permissions

Scenario: Preserve File Structure, Restrict Permissions

What It Is

With this option, the priority is to restrict permissions to retain waterfall permissions on the target without providing unintended access to files or folders where inheritance has been broken, and permissions to child folders have been revoked relative to their parents.  For each item, if it is more restrictive than the parent, the parent’s permissions will be adjusted so that the revoked permissions for the child are also revoked from parent folders further up the tree.

When To Choose It

Choose this option when you are primarily concerned about security and limiting access to confidential information, such as personnel and financial files.

Example

Source Permissions

On the source, we have a directory structure that is shared as follows:

Engineering: shared with “Engineering”, “Product Management”

  • Project Alpha: shared with “Engineering”, “Product Management”
  • Project Beta: shared with “Engineering”, “Bob Johnson”

Marketing: shared with “Marketing”

  • User Studies: shared with “Marketing”, “Designers”
  • Personas: shared with “Designers”, half of the marketing users

Target Permissions

On the target, you want the following directory structure shared as follows:

Engineering: shared with “Engineering.”  “Product Management” will be deleted because it is not a sharee of the child folder Project Beta.

  • Project Alpha: remains shared with “Engineering”, “Product Management”
  • Project Beta: remains shared with “Engineering”, “Bob Johnson”

Marketing: not shared.  “Marketing” will be deleted because  it is not a sharee of the child folder Personas.

  • User Studies: shared with “Marketing”, “Designers”
  • Personas: shared with “Designers”, half the marketing users
Updated on May 6, 2019

Related Articles