Smart Solutions
Need help?
  • 100% Free & MIT Licensed
  • No third-party data hosting
SharePoint PermissionsHow-toGovernance

How to remove unique permissions in SharePoint Online (audit + reset workflow)

8 min readBy Offered as a service by our team

SharePoint Online inherits permissions by default — a library gets its permissions from the site, a folder from the library, an item from the folder. The moment someone clicks Share or Stop Inheriting Permissions, that chain breaks and you now have a new permission scope to track. Multiply that by a few hundred Share clicks and you have a Copilot-readiness problem.

This post walks through the cleanup workflow we use on client tenants: inventory the broken-inheritance scopes with a free reporter, review them against the parent, then reset the safe ones from the SharePoint UI (for a handful) or PnP PowerShell (for bulk). The tool finds the problem; SharePoint and PowerShell apply the fix.

Why unique permissions accumulate

  • Share button — every "Share with…" on a file or folder breaks inheritance for that object.
  • Stop Inheriting — owners click this to tweak one folder and forget about it.
  • Migration tools — some content moves carry the source ACL across, even when the target site has cleaner groups.
  • OneDrive co-authoring — files moved out of OneDrive into SharePoint can land with per-user grants.

None of these are bugs. They are SharePoint working as designed. The problem is nobody is tracking the accumulation — until Copilot starts surfacing documents a user technically had access to but everyone assumed was "private to the team."

Step 1 — Inventory every broken-inheritance object

Two ways to do this. The PowerShell way:

Get-PnPListItem -List "Documents" | Where-Object {$_.HasUniqueRoleAssignments -eq $true}

That works at small scale but goes slow on libraries over a few thousand items and gives you no UI to act on the results. The no-code way is the free SharePoint Smart Permissions SPFx web part: point it at a site, clickShow only unique permissions, and you get a sortable, filterable, exportable list of every scope that has broken inheritance — site, list, folder, item.

Step 2 — Classify each Unique row

The Smart Permissions report tags every scope with just two categories: Inherited or Unique. Inherited rows will clean themselves up the moment you fix the parent, so filter the export to the Unique rows — that's the entire scope of the cleanup.

For each Unique row, compare the principals and roles against what the parent grants and add your own Decision column with one of three tags:

  • Matches parent — same principals, same role assignments as the parent. Pure noise from an accidental Share click. Safe to reset.
  • Stricter than parent — removes some inherited access (e.g. a locked-down folder). Owner-driven; keep.
  • Adds access — extra principals on top of what the parent grants. Most common, most risky. Needs owner sign-off before reset.

This Decision column is what you'll act on in Step 4.

Step 3 — Get owner sign-off on the "adds access" rows

Filter the Excel to Adds access rows and walk them through the site owner. Most additions are stale — someone left the team, a project ended, a vendor was offboarded. Capture every decision in the spreadsheet; this is your audit trail.

See also: How to audit SharePoint permissions (without losing a week).

Step 4 — Reset the safe rows

Smart Permissions is a read-only reporter — it finds and exports what to fix, it does not rewrite ACLs. The reset happens in one of two places:

For a handful of items — SharePoint UI

Open the item or folder, click the … menu → Manage access → Advanced, then click Delete unique permissions. The object re-inherits from its parent immediately. This is the right choice when your Excel shows a dozen rows.

For bulk — PnP PowerShell

When Excel shows hundreds or thousands of rows, loop them through PnP PowerShell:

Import-Csv .\reset.csv | ForEach-Object { Set-PnPListItemPermission -List $_.List -Identity $_.ItemId -InheritPermissions }

Set-PnPListItemPermission -InheritPermissions performs the exact same operation as the UI's Delete unique permissions button — it is the scriptable equivalent. Run it in batches of a few hundred with a small delay to stay clear of throttling.

Step 5 — Re-run the report

Re-export the permissions report straight after the reset. Only the rows you intentionally kept unique should remain. Save both exports as the before/after evidence — Copilot governance reviews love this, and you'll thank yourself when you re-run the cleanup in a quarter.

Why this is a Copilot-readiness problem

Copilot for Microsoft 365 surfaces every document the user technically has access to. If a folder was shared to a now-former employee five years ago and inheritance was broken, that grant lives on. Copilot doesn't ask whether the access "should" exist — it just respects the ACL. Resetting inherited permissions is the cheapest, fastest way to collapse the surface area before Copilot rollout.

Related: SharePoint external sharing report — for Copilot readiness.

FAQ

Will resetting inheritance delete files?

No. It only rewrites the ACL on the object to match the parent. The files themselves are untouched.

Can I undo it?

Not from a single button. That's why the before-export matters — it lets you re-grant any specific access that turns out to be needed.

How often should I run this?

Quarterly for active sites, twice a year for archive sites. Drift is constant; the only question is whether you catch it in 30 minutes or a week.

Related

Free · MIT license · no sign-up

Get your first result in about 10 minutes

Visual permissions audit + Excel export. No PowerShell. Free, MIT licensed, no sign-up.

  1. Download the .sppkg package from the latest release.
  2. Upload it to your tenant App Catalog.
  3. Add the web part to a SharePoint page.
Install guide
Download the latest releaseView on GitHub
Email me when a new release ships
Get notified when SharePoint Smart Permissions updates

No marketing spam. One short email when a new release ships. You can unsubscribe anytime.

The SharePoint permissions guides

Understand how access is granted, report on who actually has it, then compare the tools that get you there.

Was this page helpful?

One click. No form, no email address.

Missing something in SharePoint Smart Permissions? Feature requests and bug reports go straight to the developer on GitHub — no account needed to read, free account to post.

Request a feature

Related tool

SharePoint Smart Permissions

Visual permissions audit + Excel export. No PowerShell. Free, MIT licensed, no sign-up.

Want a second set of eyes?

Get a SharePoint permissions audit from our team

We review who can see what across your sites, flag oversharing before you roll out Copilot, and help you put a cleanup plan and governance in place.

About the author

Sean Regan

SharePoint & Microsoft 365 consultant with 20+ years of hands-on experience building SPFx web parts, migration tooling and tenant-grade automation. Maintainer of the open-source SharePoint Smart Solutions suite.