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

SharePoint permissions audit estimator

Last updated · By Sean Regan

Size your audit

Everything is calculated in your browser — nothing is sent anywhere.

Site collections you need to report on, including any Teams-connected sites.

Lists, libraries, folders and items that could carry their own permissions. A typical department site runs 1,000-5,000.

Broken inheritance. Well-governed tenants sit near 1-2%; tenants with heavy per-folder sharing reach 10% or more.

Used only to translate hours into a number a budget owner recognizes.

Uniquely permissioned objects

6,000

of 150,000 total

Manual review

171 hrs (22.8 days)

$12,813 of effort

PowerShell

25.7 hrs

$1,925, scripting included

Reporting web part

7.5 hrs

$563 of effort

On these inputs a reporting tool saves roughly 163 hrs (21.8 days) against clicking through the UI and 18.2 hrs against writing and running your own PowerShell. Scan time itself is machine time, not your time — the figures above count human attention.

What drives the number

A site where every library, folder and item inherits from the site is one thing to check. Every broken inheritance is a separate access decision somebody made, and each one has to be opened, understood and recorded. That is why the unique-permission percentage moves this estimate far more than the site count does.[1]

The second multiplier is group nesting. A SharePoint group containing a Microsoft 365 group containing a security group is three lookups before you know who "Members" actually means, and the answer changes without anyone touching SharePoint. An audit that lists group names rather than expanded people is not an audit — it is a table of pointers.

Third is sharing links. Anyone links, organization links and direct-access grants are real permissions that never appear in the classic group view, and they are the ones that matter most before a Copilot rollout.

What a complete audit covers

  • Site collection administrators for every site in scope.
  • SharePoint group membership, expanded through nested Microsoft 365 and security groups to real people.
  • Every object with unique permissions, and the permission level granted on it.
  • Sharing links, separated into Anyone, organization-wide, and specific-people links.
  • External and guest accounts, and precisely what each one can reach.
  • A dated export, so next quarter's run is a comparison rather than a fresh start.

Running it with Smart Permissions

SharePoint Smart Permissions is a free, MIT-licensed SPFx web part that produces exactly that inventory: every object classified as Inherited or Unique, group membership expanded to people, sharing links surfaced, and a per-user "what can this person reach" lookup — exported to Excel for the owner review. It is strictly read-only, so the audit never becomes an accidental change. The install takes about ten minutes, and the full audit walkthrough covers the order to work in.

FAQ

How long does a SharePoint permissions audit take?
The driver is not the number of sites but the number of uniquely permissioned objects. A 50-site tenant with broken inheritance on a few thousand folders is days of clicking through the UI, minutes with a reporting tool, because the tool enumerates unique permissions instead of you opening each object.
What should a permissions audit actually cover?
Site collection administrators, SharePoint group membership expanded through nested Microsoft 365 groups and security groups, every object with unique permissions, sharing links (including Anyone links), and external or guest accounts.
Is PowerShell faster than a reporting tool?
It is far faster than clicking, and slower than it looks. Scripts need writing, throttling handling, rerunning after failures, and shaping into something a business owner can read. The estimate here charges PowerShell a lower per-object rate than manual review but a real per-site overhead.
How often should permissions be audited?
Quarterly for most organizations, and immediately before enabling Microsoft 365 Copilot, because Copilot surfaces content according to existing permissions and over-sharing becomes visible fast.
Can Smart Permissions fix the problems it finds?
No. Smart Permissions is strictly read-only: it reports which objects inherit and which are unique, and who has access. Remediation stays a deliberate act you perform in SharePoint.

References

  1. [1] Sharing and permissions in the modern SharePoint experience — Microsoft Learn

Related

Looking for the other calculators? They all live on the tools & calculators page.

Free · MIT license · no sign-up

Get your first result in about 10 minutes

Download SharePoint Smart Permissions, follow the step-by-step install guide, and run it against a real site the same afternoon. Nothing to license, nothing to renew.

  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.

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.