SharePoint information architecture
SharePoint information architecture
Information architecture is the way your documents are organized, labeled, secured and found. We design it for SharePoint and Microsoft 365: hubs, sites, libraries, metadata, permissions and navigation, so that staff find the right file quickly and sensitive content stays protected.
- Design before implementation
- Maintainable permissions
- Prepared for Copilot
Key facts
- Suited for
- Companies moving files or reorganizing SharePoint
- Typical duration
- 3 to 8 weeks
- Result
- Architecture, sites, permissions, intranet
- Pricing
- Fixed, quoted within one week
Common situations
Signs that your information architecture needs attention
Without a defined architecture, SharePoint tends to reproduce the problems of the old shared drive. These are the issues we see most often.
The old drive copied as it was
Folder trees ten levels deep, moved from the file server with the same confusion as before.
Permissions that nobody can explain
Access granted file by file over the years, until no one can say who sees what.
Several versions of the same file
Copies in email, in chats and on computers, with no certainty about which one is current.
Search that does not help
Staff give up on search and ask a colleague instead.
No intranet
Company news, policies and forms are scattered across emails and shared folders.
Not ready for Copilot
Copilot can surface any content a user has access to. With overly broad permissions, that can include salaries or contracts.
Scope
Scope of an information architecture project
We define the architecture with you in workshops, implement it, move content into it and train the people who will maintain it.
Site architecture
A map of where each type of content belongs.
- Hub sites by department or activity
- Team sites and communication sites
- Libraries and folder conventions
Metadata and classification
Documents described consistently so they can be filtered and found.
- Columns and content types where useful
- Views by client, project or status
- Sensitivity labels where your plan allows
Permissions model
Access managed by groups rather than individual files.
- Standard roles for each site
- Restricted areas for sensitive content
- External sharing rules
Intranet and navigation
A home page and navigation that connect everything.
- Company news and announcements
- Policies, forms and key links
- Consistent navigation across hubs
Content migration
Your files moved into the new architecture.
- From file servers, NAS or cloud storage
- Old content reviewed and archived
- Permissions mapped to the new model
Copilot and AI readiness
Content exposure reviewed before AI tools are enabled.
- Oversharing review
- Sensitive content identified
- Retention and lifecycle rules
Method
How an information architecture project runs
We design first, then implement, then move content. Working in this order avoids most of the problems seen in SharePoint environments.
-
Phase 01
Content and access review
We look at what you have and who needs access to what.
- Current file shares and sites
- Volumes, owners and sensitive areas
- How departments share documents
-
Phase 02
Architecture workshops
Together we design the target architecture.
- Hub and site map
- Metadata and permissions model
- Navigation and intranet content
-
Phase 03
Implementation
Sites, libraries and permissions are created according to the design.
- Hubs, sites and libraries
- Groups and access rights
- Intranet home page and navigation
-
Phase 04
Content migration
Files are moved into the new architecture in waves.
- Duplicates and outdated content cleaned up
- Migration with permissions applied
- Validation with each department
-
Phase 05
Training and handover
Staff learn the new organization and site owners learn to maintain it.
- Training for users and site owners
- Architecture documentation
- Rules for creating new sites and libraries
Why we avoid copying the old drive
Moving the same folder tree into SharePoint changes where files live but not how hard they are to find. A migration is the right moment to correct the structure and the permissions.
Example
Example architecture for a company of about 100 people
Each company is different. This example shows the type of architecture we design, with one hub per area and clear owners for every site.
| Level | Site | Access | Content |
|---|---|---|---|
| Home | Intranet | All staff | News, policies, forms, links to each hub |
| Hub | Operations | Operations staff | Procedures, planning, supplier documents |
| Hub | Sales and clients | Sales team and management | Proposals, client folders, price lists |
| Hub | Administration | Restricted per site | Finance, HR and legal sites, each with its own access |
| Team site | Project sites | Project members and guests | Project files, connected to the matching team in Teams |
| Archive | Archive | Read only | Closed projects and older content kept for reference |
Deliverables
An architecture your staff can find their way in for years
You receive an implemented architecture, a permissions model your IT contact can maintain, and documentation explaining each decision.
What you receive
- Information architecture map
- Hub sites, team sites and libraries
- Metadata and classification scheme
- Group-based permissions model
- Intranet home page and navigation
- Content migrated into the new architecture
- Oversharing review for Copilot readiness
- Documentation and training for site owners
Our approach
How we approach information architecture
Design comes first
Workshops and a written architecture precede any configuration.
Permissions you can maintain
Access is managed by role and group, so your team can maintain it without us.
Content reorganized
Files are cleaned up and reorganized during the move, not transferred as they are.
Prepared for AI
A clean permissions model is the first step before Copilot. We address it during the project.
Questions
Frequently asked questions about information architecture
What exactly is information architecture?
It is the way information is organized, labeled, secured and found. In Microsoft 365 it covers sites, libraries, metadata, permissions, navigation and search. It determines whether staff can find a document in seconds or not at all.
Can you reorganize an existing SharePoint?
Yes. We review your current sites and permissions, design the target architecture, and reorganize content and access step by step without blocking your teams.
How does this relate to the Teams service?
Every team in Teams has a SharePoint site behind it. The Teams service covers how people collaborate. Information architecture covers where all documents live, including departments, the intranet and archives. Many companies combine both.
Do we need an intranet?
Not always. Above about 50 employees, a simple intranet home with news, policies and links usually reduces internal email significantly. We assess this during the workshops.
Why does information architecture matter for Copilot?
Copilot can only show users content they already have access to. If permissions are too broad, it can surface documents that should remain private. A clean architecture is the first step before any AI rollout.
How are sensitive areas such as HR and finance handled?
They get their own sites with restricted access, managed by a small group of owners. Sensitive content is never stored in sites open to all staff.
Request a quote
Describe your setup on the quote form. After a short discovery call, we send a written, fixed quote within one week.
- Quote form
- About five minutes
- Discovery call
- 45 minutes, by video
- Written quote
- Fixed price, within one week
Related services
Services often combined with this one
When several services are part of the same project, we plan them together and send a single quote.
Related service
Microsoft Teams
Team and channel structure, governance rules and training for everyday collaboration.
Teams serviceRelated service
Copilot and AI adoption
Microsoft 365 Copilot prepared, piloted and rolled out with governance and training.
Copilot and AI serviceRelated service
Power Platform automation
Business apps and automated workflows built with Power Apps and Power Automate.
Power Platform serviceOrganize your documents properly
Tell us where your documents are stored today and you will receive a written, fixed quote within one week.