Every SharePoint admin eventually opens a library and finds a folder that nobody can explain. It has its own permissions, three named users nobody recognises, and a note from 2022 that says “temporary”. Welcome to broken inheritance.
This is a field guide for that moment. It covers how SharePoint permission inheritance works, when breaking it is the right call, and how to stop unique permissions from quietly taking over your environment.
The model in one paragraph
Inheritance controls how access flows from a parent to the objects below it: site, library or list, folder, file. By default, each new object inherits from its parent. Breaking inheritance gives one object its own permission set while the rest of the site keeps inheriting. That is useful and dangerous for the same reason: the exception is invisible from the level above.
One detail worth remembering: a hub site shares navigation and theme with its associated sites, but not permissions by default. Associating a site with a hub does not grant anyone access.
When breaking inheritance is justified
Sometimes a single folder really does need a different audience, for example HR documents inside a general team library. In that case break inheritance, but treat it like a change request, not a click:
Write it down. Record what was changed, why, and who approved it. The m365.fm guide on permission inheritance recommends keeping a permissions register for exactly this reason.
Use groups, not people. Give the unique permission set to a security group, ideally one in Microsoft Entra ID mapped to a role. Named individuals are what turn a tidy exception into the mystery folder from the start of this article.
Set a review date. A unique permission without an expiry tends to outlive the project it was made for.
Three traps that catch experienced admins
Restoring is a one-way door. Returning to inheritance (the option is labelled “Delete unique permissions” or “Inherit Permissions”, depending on the interface) discards the custom set, and per the guide it cannot be undone through the UI. Run Check Permissions first so you know who will lose access.
Permissions do not travel with content. According to the same guide, moving or copying an item with unique permissions does not carry those permissions over. If a document was shared through a protected folder and then moved, it takes on the permissions of its new location.
Removing the wrong group. When you break inheritance you get a copy of the current permissions to edit. It is easy to remove a site owners group while tidying up. Check that someone accountable still has Full Control before you save.
Finding the exceptions you already have
You cannot manage what you cannot list. The guide names PnP PowerShell cmdlets such as Get-PnPListItem and Get-PnPSiteGroup for enumerating items and groups, plus Reset-PnPListItemPermission and Set-PnPListItemPermission for correcting them. For tenant-wide scale, a scheduled report helps more than an occasional manual look; the m365.fm episode on auditing SharePoint Online permissions at scale describes an approach with PnP PowerShell, Microsoft Graph and Azure Automation that expands group-based and inherited permissions instead of only direct assignments.
A simple rule of thumb
Treat unique permissions as debt. A few are fine, each one should have an owner and a reason, and the total should trend down. A quarterly audit that counts exceptions, per site, is enough to show whether you are paying the debt off or adding to it.
Listen / Read more
Article: SharePoint Permission Inheritance Explained on m365.fm
Episode: Audit SharePoint Online Permissions at Scale (M365.FM)

