Permissions 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 Add-In 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). The DeliverPoint Add-In can only manage permissions within the scope of a single Office 365 SharePoint Online Site Collection.

You can use the DeliverPoint Add-In to manage site, list, folder, or item-level permission inheritance. You can use the Permission Inheritance DeliverPoint Add-In commands, Inherit Permissions and Break Permissions, from the DeliverPoint Add-In Main Page.