Permission Inheritance

For easier administration, it is recommend that you avoid breaking inheritance too frequently. That is, you should keep the permissions inheritance intact for all sites, lists, libraries, and items. To avoid breaking inheritance at the list, library, list item, or file level, you should organize sites so that you can assign permissions to the site that contains the protected content. For example, you might create a sub site for documents that contain sensitive data, or a sub site that contains lists with restricted access. In this way, you can manage permissions for all content in a site with one action, instead of tracking many individual documents or list items. (See the white paper, Best practices for using fine-grained permissions.)

If you believe permission inheritance has been broken at the list, library, list item or file levels, then you can use the Unique Permissions DeliverPoint commands to find where permission inheritance was stopped and different permissions assigned.

*A site collection is a security boundary, that is, the top-level site of the site collection, and it does not inherit its permission settings from any other site. The site collection administrator configures the initial permissions settings for a site collection, which are then inherited by the content in the site collection (sites, lists, libraries, list items and files).

You can use the DeliverPoint CSWP to manage site, list, folder, or item-level permission inheritance. You can use the Permission Inheritance DeliverPoint commands, Inherit Permissions and Break Permissions, from the DeliverPoint Dashboard Actions Menu.

To Inherit Permissions or Break Inheritances, follow the steps below:

1. Navigate to the “DeliverPoint dashboard”
   
   
2. In the tree view, select the SharePoint objects to be included in the scope. For example, select one or more sites or an account, depending on which view you are currently using (Farm or Account Centric View)..
   
   
3. On the ribbon, select Actions, Permissions Management, and either Break Permissions or Inherit Permissions, depending on which action is required. Note: You will only see Permissions Management in the menu if you have selected an object in the tree that is capable of inheriting permissions (e.g. not a top level site collection)
   
   
   
   
4. Under Inherit Permissions Operation, confirm your scope and click Run.
   
   
   
   An Actions section appears with a message that the jobs have completed successfully.
   
   

!When you select Inherit Permissions, you will lose any unique permission settings that you have configured on that site.