The SharePoint Permission Model: Site, Library and Item-Level Access

Designing a SharePoint permission structure: inheritance and broken permissions, M365 and SharePoint groups, the effect of sharing links, permission templates and reporting.
Technical summary
Technology
SharePoint Online, Microsoft 365 Groups, Entra ID, PnP PowerShell
Topic
Designing a sustainable SharePoint permission structure
Level
Intermediate–advanced
Prerequisites
  • Site owner or SharePoint administrator rights
  • Knowledge of Microsoft 365 group management
  • PnP PowerShell (for reporting)
In this article7 sections

Permission chaos in SharePoint isn’t born from a single big mistake. It’s born from small exceptions accumulated over the years: “temporary” access given to a folder, a file’s sharing link, a departed employee’s forgotten direct permission. One day the auditor asks “who can see this folder?” and nobody can answer. Below, we describe a sustainable permission structure for intranet and document areas from an implementation designer’s perspective: inheritance, group types, the effect of sharing links, permission templates and the reporting method.

Permission inheritance and broken permissions

In SharePoint, permissions are inherited from top to bottom: site → list or library → folder → item. By default, all files in a library carry the site’s permissions. When “stop inheriting permissions” is chosen at any level, a unique permission scope is created for that object; the permissions at that moment are copied and become independent. From then on, changes at the upper level don’t reach this object.

Broken inheritance has two costs. The first is visibility: the site permissions page doesn’t show exceptions on child objects; the question “who can see this file?” can’t be answered without examining object by object. The second is scale: Microsoft specifies a supported limit of 50,000 for the number of items with unique permissions in a list or library, and gives 5,000 as the recommended limit for general use. In a library approaching these limits, permission operations slow down and management practically stops.

The design principle is simple: grant permissions at the highest possible level with the fewest possible exceptions. For content requiring different access, the order of preference is a separate site, then a separate library, and a folder last. Item-level permissions remain the exception.

Microsoft 365 groups, SharePoint groups and direct permissions

Access to a site can be granted in different ways, and each is managed in a different place. Membership managed from the wrong place means two separate lists and constant inconsistency:

Method Where it’s managed Suitable use
Microsoft 365 group Teams, Outlook, Entra ID Team sites connected to Teams; membership is the same as the team’s
SharePoint group The site’s permission settings Communication sites, site-specific roles such as approvers
Security group (Entra ID) Entra ID or on-premises AD Organizational audiences such as departments or locations
Direct user permission On the object Should be avoided; as an exception and documented

On a team site connected to a Microsoft 365 group, group owners are mapped to the site’s Owners group and group members to the Members group. That’s why membership changes on a site connected to Teams are made from Teams or the group. The mistake we see most often in the field is adding the user directly to the SharePoint Members group: the user sees the files but can’t get into the team channel and comes back to the help desk saying “I can’t see the team in Teams”. Communication sites have no Microsoft 365 group; Owners, Members and Visitors are SharePoint groups, and read access for a broad audience is usually given by adding a security group to the Visitors group.

Don’t skip the difference between Edit and Contribute at the permission level: Edit allows adding and deleting lists and libraries; Contribute only gives the right to add, edit and delete items in existing lists and libraries. A user who accidentally deletes a library usually comes with Edit rights. In document management areas, Contribute is often the safer choice for a broad member audience.

Site, library, folder and item level

Each level has a different management cost and the right scenario for it:

  • Site level: A department or project boundary. Drawing the permission boundary here is the most visible and most easily audited model. Hub association doesn’t change permissions; for the site topology, see the hub site architecture guide.
  • Library level: A different audience within the same site; for example, “Policies” that everyone reads on the HR site and “Personnel Files” that only the HR team accesses.
  • Folder level: Small exceptions where a library split isn’t practical. Having “CONFIDENTIAL” in the folder name isn’t a control. Check that permissions are really broken.
  • Item level: Mandatory cases such as person-specific records. If row-level access is needed in a list-based application, consider Dataverse’s security model instead of item permissions; the details are in the Dataverse vs SharePoint list comparison.

Breaking item-level permissions automatically with Power Automate (such as opening each request record only to the requester) is technically possible. But every record means a new unique permission scope. In a process that produces thousands of records a year, this approach hits the recommended limit within a few years. And reversing it is laborious.

When a user shares a file with “Share”, an additional access scope is created for that item in the background. Depending on the link type, SharePoint creates hidden “SharingLinks” groups and grants Limited Access to the parent objects along the path to the file. Inheritance is also broken on the shared item; in other words, every share adds to the number of unique permission scopes described above. While the site permissions page shows “only three groups”, hundreds of shared files can sit in the library. The visible picture is incomplete.

Link type Who gets access Design note
Anyone (anonymous) Anyone with the link Recommended to be turned off in corporate document areas
People in the organization All internal users with the link A forwarded link widens the scope
Specific people Selected people Controlled; preferred as the default
People with existing access Those already authorized Grants no new permission; only generates a link

Two settings are decisive in implementation design: the default link type (can be set to “Specific people” at tenant and site level) and leaving sharing only to site owners on sensitive sites. Whether members can share files and folders is set in the “Sharing settings” section of the site settings. For the security side of external sharing and guest access, the SharePoint and OneDrive external sharing security guide contains the detailed settings.

In a corporate Microsoft 365 environment, designing each site’s permission structure from scratch produces inconsistency. Use templates by site type. The following are starting suggestions; they should be adapted to the organization’s information classification:

Site type Owners Editing Read
Corporate communication site 2–3 intranet editors Content authors group All employees security group
Department site Department manager + deputy Department security group Other relevant departments or all employees
Teams team site M365 group owners M365 group members Visitor group if needed
Controlled document site Document control owner Authors; a separate approver group All employees, approved version only
Confidential project site Project manager + IT deputy Project team None; sharing by owners only

Common rules for the templates: at least two owners on every site; a site with a single owner is left ownerless when that person goes on leave. Named role holders in the Owners group where possible; read access given to groups, not individual users; direct user permissions only as a documented exception. The approver group and draft visibility setup on the controlled document site are explained in the document revision management guide.

Reporting permissions and periodic review

A permission structure is right on the day it’s set up. The problem starts six months later. The tools we use in periodic reviews:

  • Check permissions: “Check Permissions” on the site permissions page shows what rights a user or group has on that object and where the right comes from. When a user says “why can/can’t I see this”, that’s the first place to look.
  • Manage access panel: Lists the links and direct access granted at file or folder level.
  • PowerShell inventory: PnP PowerShell is used to list items with unique permissions in a library.
Connect-PnPOnline -Url https://contoso.sharepoint.com/sites/hr -Interactive `
  -ClientId <app-registration-client-id>

$items = Get-PnPListItem -List "Documents" -PageSize 2000
$result = foreach ($item in $items) {
    $unique = Get-PnPProperty -ClientObject $item -Property HasUniqueRoleAssignments
    if ($unique) {
        [pscustomobject]@{ Id = $item.Id; Path = $item.FieldValues["FileRef"] }
    }
}
$result | Export-Csv .\unique-permissions.csv -NoTypeInformation -Encoding UTF8

Since the script sends a separate query for each item, it takes a long time on a large library; run it outside business hours and per library. -ClientId is the Entra ID app registration you created for PnP PowerShell in your tenant. In tenants with a SharePoint Advanced Management license, data access governance reports and site access reviews do the same job tenant-wide; verify their scope in Microsoft’s current documentation. For each row in the output, a single question is asked: “is this exception still needed?” If not, restore inheritance (Delete unique permissions). This operation also removes sharing links given on that object. Inform users beforehand.

Content sensitivity determines the review frequency; for example, owner confirmation can be obtained every three months for confidential project and HR sites, and every six months for general department sites. If this process is assigned to site owners as a “verify your site’s owner and member list” task, the IT team’s workload drops. Microsoft’s sharing and permissions in the modern experience documentation contains the official explanation of group mappings. Applying permission templates across the intranet is one of the first steps of our SharePoint intranet and employee portal work.

Frequently asked questions

On a site connected to Teams, is adding a user to a SharePoint group enough?

No. The user gets access only to the site content; they can’t access the team’s channels and chats. On sites connected to Teams, manage membership through the Microsoft 365 group or Teams.

Is it better to give a folder unique permissions or to create a separate library?

If content requiring different access is permanent and large, a separate library is more visible and auditable. Broken permissions at folder level are suitable for small, temporary exceptions.

Not directly. Links are created as hidden SharingLinks groups at file level and as Limited Access on parent objects. They’re examined through the file’s manage access panel or a PowerShell inventory.

Is there a practical limit for item-level permissions?

Microsoft specifies a supported limit of 50,000 and a recommended general limit of 5,000 for items with unique permissions in a list or library. For applications requiring row-level access, consider the Dataverse security model.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Web

We build and maintain corporate websites, WordPress and CMS platforms, intranet and SharePoint portals, document management, and form and approval workflows, and keep them secure and up to date.

Knowledge Center

Other articles