← Back to blog

SharePoint Permissions Best Practices for Small Businesses

November 21, 2026
SharePoint Permissions Best Practices for Small Businesses

The best SharePoint permissions setup is a boring one. Give access to groups, not individuals. Split content by site instead of by folder. Keep unique permissions rare. Set safe sharing defaults, and review who can see what on a schedule. Every rule below follows from how SharePoint calculates access, and each one saves you from the same problem: a tangle of exceptions that nobody can explain a year later.

This guide is written for owners and office managers at law firms, dental and medical practices, manufacturers, accounting firms and nonprofits. You do not need to be an administrator to follow it. Where a term is technical, it is explained the first time it appears.

Greatplainsnetworking
Keep Business Data Access Under Control
Great Plains Networking helps small businesses manage cybersecurity and IT with tailored support explained in plain language.
Visit

Key Takeaways

  • Assign access through groups (Owners, Members, Visitors, or a Microsoft 365 group) and never person by person.
  • Create a separate site for each set of people who need different access, rather than locking down individual folders inside one big site.
  • Treat every broken inheritance as a cost: Microsoft recommends keeping a library under 5,000 unique permission scopes, and sharing folders rather than single files.
  • Set sharing defaults to "Specific people" with View-only permission, and expire any "Anyone" links within 30 days.
  • Put a recurring review on the calendar, because effective access is the highest permission from any source, so old grants quietly stay in force.

Table of Contents

How SharePoint Permissions Actually Work

Four ideas explain almost every permissions problem you will meet.

Permission levels are bundles of rights. Common ones are Full Control, Edit, and View Only (Read). A level says what someone can do.

Groups are collections of people. SharePoint's default groups are owners (administrators), members (contributors) and visitors (readers), per Microsoft's developer documentation. You attach a level to a group once, and everyone in the group gets it.

Inheritance means a folder or file takes its parent's permissions by default. Change the site's permissions and everything underneath follows.

Unique permissions are what happen when inheritance is broken. Microsoft explains that a file or folder then stops inheriting and gets its own permission scope. That happens when someone shares the item, creates a guest link, or manually stops inheritance. Most oversharing and most "why can she see that?" mysteries start here.

One more rule matters. A person's effective access is the highest permission granted by any source, whether direct access, a group, a parent folder or site, or a sharing link, according to Microsoft's guidance on shareable links. To reduce someone's access, you must change every source that gives them more. Removing one grant while another remains does nothing.

Four sources combine to determine effective access

Practice 1: Assign Access to Groups, Never to Individuals

Microsoft's site governance guidance tells site owners to follow least privilege, add people to the standard Members, Visitors and Owners groups instead of granting individual permissions, keep most people in Members or Visitors, and limit the Owners group.

Least privilege simply means each person gets the minimum access their job needs. We cover the idea in more depth in our guide to least privilege access. The same group-based thinking shows up in other industries too, for example in multi-property permissions for marina groups, where access follows role rather than person.

Why it matters for a small office:

  • Onboarding is one step. A new paralegal joins the Members group and has what the team has.
  • Offboarding is one step. Remove the person from the group instead of hunting through hundreds of folders.
  • Audits are readable. "Who can edit Client Files?" has a short answer when the answer is a group.

For team sites connected to a Microsoft 365 group (the default when you create a team site or a Microsoft Teams team), Microsoft's admin center reference recommends managing access through the Microsoft 365 group or Teams membership rather than direct site permissions, for easier administration and consistent access. On those sites you also cannot modify the default Owners, Members and Visitors groups, as Microsoft's customization page notes. That is a feature: it keeps the model simple.

Practice 2: Make a New Site Instead of a New Permission Set

The most common small business mistake is one giant site with a folder tree, where each folder has its own access list. It starts tidy and ends in chaos.

A cleaner pattern: when two groups of people need different access, create two sites. HR gets an HR site. Finance gets a Finance site. A dental practice might keep front desk scheduling documents in one site and billing records in another. A law firm might give each practice area its own site. A nonprofit might separate board materials from program files.

The benefits are practical:

  • Each site has its own Owners, Members and Visitors, so access is visible at the top level.
  • Nobody has to remember which folder was locked down in 2023.
  • Search, sharing settings and reviews can be applied per site.

A simple test: if you find yourself breaking inheritance on a folder because "only these three people should see it," that folder probably wants to be its own site.

Practice 3: Keep Unique Permissions Rare and Deliberate

Sometimes a folder-level exception is the right call. When you use one, do it on purpose and write it down.

Microsoft puts numbers on the cost. A document library can hold up to 50,000 unique permission scopes, but Microsoft recommends staying under 5,000 for best performance. It also advises sharing folders instead of individual files, and sharing folders before a library grows past 100,000 items. Once a list or library has more than 100,000 items, inheritance cannot be broken on the list itself.

Practical rules for exceptions:

  1. Break inheritance at the folder or library level, not on single files. One folder-level exception is far easier to audit than forty file-level ones.
  2. Give the exception to a group. Even a one-off restriction should use a group so it can be maintained.
  3. Know what sharing does. When someone shares an individual item, inheritance is automatically broken and the inherited permissions are copied to it, so later changes to the parent no longer apply, per Microsoft Support. Ordinary sharing quietly creates unique permissions.
  4. Remember folder access reaches upward. Granting someone access to a folder also gives them the Guest role on the parent list and website, as Microsoft's developer documentation explains. That lets them reach the folder, but it is one more reason to prefer a separate site.

A caution about removing access

On a list or library you must first select Stop Inheriting Permissions before you can grant unique permissions, change levels or remove users. Microsoft Support warns that removing a user's permissions removes them from all children and cannot be restored. Before you remove anyone from a busy library, note what they had so you can re-grant it deliberately.

Practice 4: Know Who Your Owners and Admins Are

Two roles get confused, and the difference matters for risk.

  • Site owners have full control of the site itself.
  • Site admins (formerly called site collection administrators) have the highest permissions. They have the same Full Control as an owner, plus management of search, the recycle bin and site collection features, and they can access items in the site even where inheritance is broken, according to Microsoft's site permissions reference.

Group or team owners are automatically both site admins and site owners. People added directly to the site owners group do not get access to the associated Microsoft 365 group or team.

The practical takeaway: keep the Owners group small, ideally two or three named people, so there is always a backup but never a crowd. Because admins can see items even where you have restricted inheritance, a restricted folder is never hidden from them. Choose them carefully and keep the list current.

Practice 5: Lock Down Sharing Before Someone Shares Too Much

Permissions are only half the picture. Sharing links are how most sensitive files leave the building by accident. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) publishes a SharePoint and OneDrive security configuration baseline from December 2023. It is written for federal agencies, but its settings are a sensible yardstick for any office. It calls for:

  • External sharing limited to "Existing guests" or "Only People in your organization."
  • The default sharing scope for files and folders set to "Specific people."
  • Default sharing permission set to View.
  • If "Anyone" links are used at all, expiring them within 30 days and limiting them to View only.

These defaults matter because a shared link is the easiest way to create unique permissions without anyone noticing. A "Specific people" link names who can open it, so a forwarded email does not forward the access.

For a deeper walkthrough of guest access settings, see our guide to SharePoint external sharing, and for the wider picture, our practical setup guide to secure file sharing. If outside clients or vendors join your Teams, guest access and MFA gaps are worth closing at the same time. Multi-factor authentication (MFA) means a password alone is not enough to sign in, and it is the single best companion to any permissions model; our guide to starting MFA with security defaults shows how.

Practice 6: Use Restricted Site Access for Your Most Sensitive Sites

Some sites hold content that should never be broadly visible: client case files, patient billing, payroll, board minutes. Microsoft offers a structural control for this. With restricted site access control, you designate Microsoft 365 or Microsoft Entra security groups (up to 10 per site) as the site's control group. People outside those groups cannot reach the site or its content, even if they were granted access earlier or hold a shared link. The policy is also honored by organization-wide search and Microsoft 365 Copilot.

Two details to remember. Being in the control group does not by itself grant access to content; the person still needs a site or content permission. And because search and Copilot respect the restriction, sensitive documents are less likely to surface for the wrong person.

If you run a regulated practice, this is a good control to discuss with your IT provider alongside your compliance requirements.

Practice 7: Review Access on a Schedule

Permissions drift. People change roles, projects end, a temp leaves, and a link created for one vendor is still active two years later. Microsoft's permission scope guidance recommends regular audits and reviews of access requests to keep permissions clean. It also assigns site owners responsibility for permissions and scheduled content audits, with a clear completion test: everyone has the content they need, and confidential content stays secured.

A lightweight quarterly routine for a small office:

  1. List your sites and confirm each has a named owner.
  2. Open each site's permissions and check the Owners group first.
  3. Look for individuals granted access directly instead of through a group, and move them into groups.
  4. Review any folders or libraries with unique permissions. Ask whether each one still needs to exist.
  5. Check outstanding sharing links, especially any "Anyone" links, and remove those no longer needed.
  6. Confirm that former employees and finished vendor engagements no longer appear anywhere.

On a file or folder, the Manage Access panel shows who has access through People, Groups and Links, which makes spot checks quick.

How to Adjust Permissions Step by Step

Here is the standard path on a modern SharePoint Online site, following Microsoft's instructions:

  1. Open the site and go to Settings, then Site permissions, then Advanced Permissions Settings.
  2. To create a group, choose Create Group, name it for its job (for example, "Finance Editors"), and add its members.
  3. To give a group or person access, choose Grant Permissions and pick a level such as Edit or View Only.
  4. To change a level, select the user or group, choose Edit User Permissions, and set the new level.
  5. To remove access, select the user or group and choose Remove User Permissions. You will see a confirmation that all of their permissions will be removed.
  6. For a list or library exception, select Stop Inheriting Permissions first, then make your changes.

The steps are simple. The hard part is the design decisions behind them: which groups to have, which sites to split, which exceptions to allow. Get those right once and the steps rarely come up again.

What This Looks Like in Real Offices

A dental practice. Clinical staff, front desk and billing need different access. Separate sites with group-based access keep patient-related documents with the people who need them. If your practice handles protected health information, your compliance obligations under HIPAA also apply to who can see it, so involve your IT provider before you design the structure.

A law firm. Client matters often need ethical walls between teams. A site per practice area or sensitive matter, with restricted site access on the most confidential, is easier to defend than a maze of folder exceptions.

A manufacturer. Engineering drawings, supplier contracts and quality records have different audiences. Give each its own site and keep supplier-facing sharing set to specific people with View access.

A nonprofit. Staff, board members and volunteers should not share one big library. Group-based access lets volunteers come and go without anyone rebuilding folder permissions each season.

Common Mistakes to Avoid

  • Giving everyone Edit "just to make it work." Start with View or Members access and add only what is needed.
  • Letting every employee own a site. A crowded Owners group defeats the point of the model.
  • Using "Anyone" links for convenience. They are the hardest to track and the easiest to forward.
  • Nesting folder exceptions several levels deep. If you cannot explain a folder's access in one sentence, it needs to be redesigned.
  • Adding permissions without removing old ones. Because the highest permission from any source wins, stale grants undo your cleanup.

Getting Help With Your SharePoint Setup

If your permissions have grown organically and nobody is sure who can see what, you are not alone. Our Microsoft 365 support covers Microsoft 365 setup and management for small businesses in Norman, Moore and Oklahoma City, and we explain things in plain language. We offer same-day response and no long-term contracts, and our 24/7 monitoring helps catch issues before they disrupt your work. For regulated offices, we also provide compliance guidance for HIPAA, IRS and CMMC requirements.

A quick way to start is the 10-minute readiness audit, which is free. You can also see how permissions fit into a broader plan in our Microsoft 365 security checklist.

Greatplainsnetworking

FAQ

What are unique permissions in SharePoint?

They are permissions a file, folder or list has on its own after it stops inheriting from its parent. This happens when you share the item, create a guest link, or manually stop inheritance. Each one adds a permission scope, which makes access harder to audit and can affect performance at scale.

What is the difference between a site admin and a site owner?

Both have Full Control of the site. Site admins also manage search, the recycle bin and site collection features, and they can reach items even where inheritance is broken. Owners control the site itself. Keep both groups small.

Should I set permissions on folders or on sites?

Prefer sites. Microsoft recommends using default groups and keeping unique permission scopes to a minimum, and a library performs best under 5,000 of them. When a folder needs a different audience from its neighbors, a separate site is usually cleaner. Use folder-level exceptions sparingly and share folders rather than individual files.

How often should I review SharePoint permissions?

Quarterly works for most small offices, and immediately after staff changes or when a project with outside guests ends. Check the Owners group, direct individual grants, folders with unique permissions and active sharing links.

Sources