# One SharePoint site, 300 staff: a permissions layout that works

> When management allows one SharePoint site for a whole branch, folder permissions are not optional. The fix is a library for each team, one private folder in each, and groups on every lock. The hard part is keeping track of it, so the layout is built to be checked.

[( Insights)](https://tenantcraft.ca/insights)

Stage

Plan

Topic

SharePoint

Published

Oct 22, 2026

Written by

[Geri Crroj](https://tenantcraft.ca/about)

Tested in a live tenant, October 22, 2026

(Short version)

Give each team its own document library. Team group gets Edit, everyone else gets Read, and that covers view-only with no extra folder. Add one private folder per library, and put cross-team work in its own libraries. Use groups on every broken lock and check the exceptions list each month.

An admin runs SharePoint for one branch of a company. The branch has about 300 people. Management has made one rule: one site, no more. That rule is not up for debate.

The branch has 20 to 30 teams. Most of them want the same three things. A private space no one else can see. A space everyone can read but only the team can change. And a shared space for work with other teams.

Then come the special cases. The CEO meets each of the seven department chiefs one on one. Each chief needs a folder shared with the CEO, and no chief may see another chief’s folder. The health and safety officer keeps accident reports that only the officer should see. Sometimes the officer needs a witness to add a statement, and that space must be open to the witness and no one else.

The admin has read the advice. “Never set permissions on folders.” With one site and 25 teams, that advice cannot be followed. This post gives you a layout that bends the rule in a few predictable places, and a way to check it each month.

The 5-minute version

1.  **Create the groups first.** One per team, plus one per private pairing such as the CEO and a chief.
2.  **One library per team.** The team group gets Edit and everyone else gets Read. That is the view-only space, with no extra folder.
3.  **One private folder per library.** Break inheritance on that one folder and give it to the team group only.
4.  **Cross-team work gets its own libraries.** CEO and chiefs in one, health and safety in another. Never inside a team’s library.
5.  **Check monthly, two levels deep.** The site’s exceptions list shows the libraries. Each library’s list shows the folders.

## The whole layout on one page

Here is what the finished site looks like. Every row is a place with its own permissions. Everything else inherits.

| Location | Who can edit | Who can read |
| --- | --- | --- |
| **Finance** library | Finance team | Everyone |
| **Finance** > **Finance - private** | Finance team | No one else |
| (repeat both rows for each team) |  |  |
| **Leadership** library | Site owners only | No one else |
| **Leadership** > **CEO - Finance chief** | CEO and Finance chief | No one else |
| (one folder per chief, seven in all) |  |  |
| **Health and safety** library | Safety officer | No one else |
| **Health and safety** > one folder per case | Officer and that witness | No one else |

Two rules hold across the whole table. Locks only go on a library or a top-level folder, never deeper. And the names follow one pattern, so anyone can spot a lock from the name alone.

## Why folder locks are fine here

“Don’t use folder permissions” is good advice for a company that can make sites. Each site gets its own owners, members and visitors, and access lives in one place per site.

You can’t do that. So aim for locks in the same two places in every library, done the same way every time.

[Microsoft’s limits](https://learn.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits) leave plenty of room. A site can hold 2,000 lists and libraries. The recommended ceiling is 5,000 unique permissions per list or library, and the supported maximum is 50,000. This layout uses one or two per library. You’ll lose track of them long before SharePoint objects, which is why the last step is a monthly check.

## Step 1: Create the groups first

Every lock in the table lists groups, not people. Build the groups before you build the libraries, so you never need to add a person by name “just for now.”

1.  Go to **Settings > Site permissions > Advanced permissions settings**.
2.  Select **Create Group**.
3.  Name it for its job: **Finance team**, **Leadership - Finance chief**.
4.  Add the members.

Make one group per team, and one per private pairing. A SharePoint group can hold up to 5,000 users, so size is never a reason to skip one. If your IT team already keeps Microsoft Entra security groups for each department, add those inside your SharePoint groups instead.

Yes, **Leadership - Finance chief** is a group with two people in it. When the Finance chief changes, you change one group. You don’t hunt for every folder the old chief was on.

## Step 2: One library per team

Each team gets a document library named after the team: **Finance**, **Payroll**, **Operations**. Inside it, the team works in normal folders that inherit from the library. Personal drafts stay in each person’s OneDrive until they’re ready, which is [the usual split between OneDrive and SharePoint](https://tenantcraft.ca/insights/sharepoint-onedrive-teams-where-files-live).

1.  Open the library.
2.  Go to **Settings > Library settings > More library settings > Permissions for this document library**.
3.  Select **Stop Inheriting Permissions**.
4.  Set the groups to match this table:

| Who | Permission level | What it gives them |
| --- | --- | --- |
| **Finance team** | Edit | Add, change and delete files |
| Site members (everyone else) | Read | Open and download, no changes |
| Site owners | Full Control | Admin access |

That is the team’s view-only space. Everyone in the branch can read the library. Only the team can change it. One common suggestion is three folders per team, including a “view only” folder. You don’t need it, because the library already does that job with no extra lock to track.

![The Permissions page for a Finance library. Finance team has Edit, IntraTeam Members and Visitors have Read, Owners have Full Control, and one named user also has Full Control.](https://tenantcraft.ca/images/perm-01-library-permissions.png)

Library permissions

The ringed row is a person added by name. Delete it once setup is done.

Before you move on, check the page for named people. Breaking inheritance can leave whoever did the setup on the list by name. Remove them.

## Step 3: Add the private folder

Each team library gets exactly one private folder, at the top level. Use one naming pattern everywhere, such as **Finance - private**.

1.  Create the folder at the root of the library.
2.  Right-click it and choose **Manage access**.
3.  Select **More options** (the **…**) and then **Advanced settings**.
4.  Select **Stop Inheriting Permissions**.
5.  Remove site members and visitors. Leave the team group with Edit and owners with Full Control.

Set this up on day one, while the folder is empty. Once a folder holds more than 100,000 items, [Microsoft says](https://learn.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits#items-in-lists-and-libraries) you can’t break or restore inheritance on it.

## Step 4: Build the shared libraries

Collaboration is where most layouts fall apart. Teams share folders inside their own library with people from other teams, and six months later no one knows who can see what. So shared work never goes inside a team library. Each kind gets a library of its own.

**For the CEO and the seven chiefs:**

1.  Create a **Leadership** library.
2.  Stop inheriting and leave only site owners on it.
3.  Create seven folders, one per chief, such as **CEO - Finance chief**.
4.  On each folder, stop inheriting and add its group, such as **Leadership - Finance chief**, with Edit.

The chiefs can’t see each other’s folders, because none of them has access to the library itself.

**For health and safety:**

1.  Create a **Health and safety** library.
2.  Stop inheriting and give it to the safety officer only.
3.  Create one folder per case.
4.  When a witness needs to add a statement, add that person to that one case folder by name.

This is the one place a named person makes sense. Put the removal date in the case notes, and take the access away when the statement is in. A two-week grant to one person is fine, as long as someone takes it away again.

## Step 5: Check it monthly, two levels deep

One commenter warned about this part, and they were right. The layout is easy to build. The ongoing work is keeping it accurate.

SharePoint keeps a list of every lock. Go to **Settings > Site permissions > Advanced permissions settings**. If anything on the site has its own permissions, a yellow bar says so, with a **Show these items** link.

![The Exceptions dialog for the IntraTeam site. It lists two libraries with unique permissions, Finance and Leadership, each with a manage permissions link.](https://tenantcraft.ca/images/perm-02-site-exceptions.png)

Site exceptions

The site-level list shows libraries only, not the folders inside them.

That list stops at the library. In my own tenant, the site’s Show these items list named both libraries but not the private folders inside them. I had to open each library to find those. Each library’s permissions page has its own yellow bar and its own **Show these items** link.

![The Exceptions dialog for the Finance library. It lists one folder with unique permissions, Finance - private, with a manage permissions link.](https://tenantcraft.ca/images/perm-03-library-exceptions.png)

Library exceptions

Each library's own list is where the private folders show up.

So the monthly check is two passes:

1.  Open the site’s **Show these items**. Every library listed should be in the layout table above.
2.  Open each library’s **Show these items**. A team library should list one folder, its private one. Leadership should list seven. Anything else is drift.

On each page, scan for named people. Anyone listed by name, outside a safety case folder, gets moved into a group or removed. For a view across every site in the tenant, see [how to find every SharePoint site with broken permission inheritance](https://tenantcraft.ca/insights/find-broken-permission-inheritance).

Budget fifteen to twenty minutes a month for 30 libraries, and put it in the calendar.

## What this does not fix

This layout keeps one site manageable. Whether one site is the right call is a separate argument, and these gaps remain either way.

**Sharing links still get around it.** Anyone with edit rights can share a file with a link, and that link adds access the layout doesn’t plan for. Review your site’s sharing settings. This post doesn’t cover them, and [sharing confidential files with an outside buyer or auditor](https://tenantcraft.ca/insights/sharepoint-virtual-data-room) is a separate setup.

**One site means one audience for mistakes.** Search only shows people what they can open, so the private folders stay private. But a careless Read grant on a library is visible to all 300 people at once.

**The rule may change.** Plenty of admins would say one site for this many teams is a mistake, and they have a point. If management ever allows more sites, the team libraries [move cleanly into team sites](https://tenantcraft.ca/services#projects). The groups come with them.

## The bottom line

Build the groups first. Give every team a library, with Edit for the team and Read for everyone else, and one private folder at the top. Keep cross-team work in its own libraries, and walk the exceptions list two levels deep once a month.

If your one site already has years of folder-by-folder sharing, clean that up before you lay out the new libraries.

Permissions Cleanup & Governance Prep Checklist

PDF · 7 pages · 45 checkpoints

[Email me the PDF](https://tenantcraft.ca/resources/guides/permissions-cleanup-prep)

---

_Canonical HTML: https://tenantcraft.ca/insights/sharepoint-permissions-layout-one-site · Agent guide: https://tenantcraft.ca/llms.txt · Site map: https://tenantcraft.ca/sitemap-index.xml_
