SharePoint information architecture
Copying the old file server into SharePoint copies its problems too.
A good SharePoint structure means people find the right version first time, and you can explain who has access to what. It comes from planning sites around audience, ownership and lifespan, not from recreating a folder tree. Here is how to structure it, what changed in 2026, and a tool that tells you where a body of content belongs.
Based on Microsoft Learn guidance, checked 31 October 2026.
- Sites, hubs and libraries
- Permissions you can explain
- Where-does-it-go tool
Reviewed by Blake Bath, General Manager, on 31 October 2026.
SharePoint information architecture
- Sites
- Hubs
- Libraries
- Permissions
Read this page as
You want the business to keep running when something breaks, and to stop being the person who has to sort it out.
People come to you when the email, the printer or a laptop stops. You want one number to call and someone who owns it until it is fixed.
Start withHow it worksThe building blocksQuestions
You want to know what is included, what it costs over a year and what you will have in writing for the insurer and the auditor.
Start withWhere does it go?When to splitQuestions
Time and money are tight, most of your people are not IT people, and your board asks about risk.
How it fits together
Four building blocks.
Each one has a job. Mixing them up is where things go wrong.
Sites
The access boundary. One per audience, owner or lifespan.
- Flat
- One owner
- Own sharing
Hubs
Join related sites for navigation and search. Not for access.
- Navigation
- Search
- Branding
Libraries
Where files live. Split when retention or audience differs.
- Metadata
- Views
- Versions
Permissions
Set at site level where you can. Exceptions recorded.
- Groups
- Few exceptions
- Reviewed
Want the whole picture?See how it worksTalk to us
Where does it go?
Site, library or folder?
The same five questions we ask in every SharePoint design workshop.
Think of one body of content, like payroll, a client project or the policy library. Answer five questions and you get where it belongs and what to check first.
Where it goes
A library or folder in the existing site
- Same people, same owner and the same risk means no new boundary is needed.
Before you set it up
- Use a few metadata columns and views for finding things, not deeper folders.
Want a person to look at your answer?Talk to usBook a free 30 minute chat (opens in a new tab)
Boundaries
When content needs its own site.
| If the content has | Use | Why |
|---|---|---|
| A different audience | A new site | Sites are the access boundary |
| A different owner | A new site | Someone has to approve access and content |
| People outside the business | A separate site | Sharing is set per site |
| Confidential material for a few | A separate site or private channel | Not a folder with broken inheritance |
| Different retention rules | A separate library | Retention and default labels apply cleanly |
| Same people, same owner, same risk | A library or folder | No new boundary needed |
Microsoft recommends flat sites joined by hubs rather than subsites. Subsites make restructuring harder later.
"Can not recommend them enough."
Access you can explain
Permissions that stay explainable.
- Manage team sites through the groupFor Teams and group-connected sites, add and remove people in the group, not inside SharePoint.
- Remember channel sitesStandard channels use the team's site. Private and shared channels each get their own site and membership.
- Tighten sharing defaultsMicrosoft ships sharing at the most permissive setting. The more restrictive of tenant and site settings applies.
- Record every exceptionEach shared link or broken inheritance is another access path. Note who, why and when it's reviewed.
- Give every guest a sponsorA named person inside the business who says when their access should end.
- Test as an ordinary userAdmins see everything. Check what a member and a guest can actually open.
Not sure where you stand?Get a free checkTalk to us
Search and AI
Copilot finds everything people can already open.
Copilot and search respect permissions. They don't create new access. What they do is make old oversharing easy to find: the payroll folder shared with everyone in 2021, or a link set to anyone in the organisation.
Microsoft's preparation guide starts with the same work as good information architecture: owners on every site, inactive sites archived, sharing tightened and overshared sites found and fixed.
- Find oversharingData access governance reports show broad links and sites open to everyone except external users.
- Hide while you fixRestricted Content Discovery keeps a site out of Copilot and organisation-wide search without changing its permissions.
- Archive what's deadOld sites add noise to answers and risk to every search.
- Label what's sensitiveSensitivity labels on sites and files add a second layer of control.
Restricted Content Discovery is part of SharePoint Advanced Management, which comes with Microsoft 365 Copilot or as an add-on. Restricted SharePoint Search is retiring and can't be newly turned on from 31 July 2026.
What changed
What changed in SharePoint in 2026.
| Change | When | What to do |
|---|---|---|
| SharePoint 2013 workflows retired | 2 April 2026 | Rebuild in Power Automate |
| SharePoint Alerts removed | From July 2026 | Use Rules or Power Automate |
| Restricted SharePoint Search, no new enablement | From 31 July 2026 | Use Restricted Content Discovery |
Rules need Contribute permission on the list or library. Staff with read-only access who relied on Alerts need a Power Automate flow instead.
Numbers that matter
The limits worth knowing.
| Limit | Number | What it means |
|---|---|---|
| Unique permissions per library | 50,000 supported, 5,000 recommended | Keep exceptions few |
| Changing inheritance | Blocked above 100,000 items | Plan access before a library grows |
| Items synced per person | 300,000 recommended | Across all synced libraries, shortcuts included |
| File path length | 400 characters | Deep folders and long names break first |
| Lists and libraries per site | 2,000 | Rarely a problem for small business |
Our view
Start with five real tasks, not the folder tree.
Ask five people to find something they use every week: the current leave policy, the latest drawing for a job, a signed contract. Where they look first tells you how they think. Build around that, then decide where the access boundaries need to be.
Then keep it simple: a site register with an owner and backup owner for each site, sharing tightened, exceptions written down, and a review twice a year. That is most of the value.
Questions about your own setup?Book a free 30 minute chat (opens in a new tab)Talk to us
How we work
Our SharePoint review in five steps.
- Step 1Inventory
Every site, team, channel, owner and sharing setting.
- Step 2Tasks
How staff actually look for things.
- Step 3Design
Sites, hubs, libraries and metadata.
- Step 4Move
Content migrated, exceptions cleaned up.
- Step 5Govern
Register, reviews and owners kept current.
Ready when you are.Book a free 30 minute chat (opens in a new tab)Talk to us
Related guides
Structure first. Then everything else gets easier.
Guides that build on a sound SharePoint.
Questions
What people ask about SharePoint structure.
How many SharePoint sites should a small business have?
There's no right number. Create a site when content has a different audience, owner, sensitivity or lifespan, and join related sites with a hub. Most small businesses end up with an intranet site, a site per team or function, and project or client sites where those come and go.
Should we use folders or metadata?
Both. A shallow folder structure is fine where it helps people work. Metadata columns and views make finding and filtering easier. Neither one controls access.
Does joining a hub give everyone access to the sites in it?
No. A hub links navigation, branding and search. Each site keeps its own permissions, so test access on each one.
What replaced SharePoint Alerts?
Microsoft removed Alerts from July 2026. Use Rules in the list or library for simple notifications, or Power Automate. Rules need Contribute permission, so read-only staff need a flow instead.
Will Copilot show staff files they shouldn't see?
Copilot only shows what the person can already open. The risk is that many people can open far more than anyone intended. Check sharing and permissions before rolling it out.
Is there a file limit before sync breaks?
Microsoft recommends syncing no more than 300,000 items across all the libraries a person syncs, shortcuts included. It's a performance guide, not a hard stop. Sync what people need, not everything.
Next step
Want a SharePoint people can find things in?
We inventory what you have, design sites and permissions around how your team works, move the content and set up the register and reviews that keep it tidy.
What happens next
- You pick a time that suits you.
- One of our engineers calls you. It takes 30 minutes and it's free. There's no slide deck.
- If we can help, we send a written plan. If we can't, we'll tell you who can.
- Nothing happens until you say yes.
You talk to the people who do the work, not a sales team. Rather talk now? Call 07 3114 2808.
Already a client? Log a job in the client portal (opens in a new tab)
Keep reading
- SharePoint support Our service.
- Copilot Deployment.
- M365 governance Guide.
- Pricing Plans.
- IT support in Brisbane The MSP Brisbane businesses call for help desk, cyber security and AI.
- Managed IT services across Australia Everything we look after, on one page.
Reviewed by Blake Bath, General Manager, on 31 October 2026. Microsoft Learn and Microsoft Support pages, checked 31 October 2026. Microsoft Learn, Information architecture in modern SharePoint; Microsoft Learn, Planning hub sites; Microsoft Learn, Teams and SharePoint connected sites; Microsoft Learn, External sharing overview; Microsoft Learn, SharePoint limits; Microsoft Learn, Manage permission scopes; Microsoft Support, SharePoint Alerts retirement; Microsoft Learn, Get ready for Copilot with SharePoint Advanced Management; Microsoft Learn, Restricted SharePoint Search

Remote