NetFusion Designs logo
Heart icon
Support
Email
info@nfd.ca
Phone
647-476-5259(Canada)
IT Services
Icon dropdown arrow

Infrastructure Implementation

Project PlanningHardware Voice over IP (VoIP)Application DevelopmentCloud DesktopSecurity Cameras

Managed IT Services

IT Support24/7 HelpDeskCyber Security & AntivirusData Backups & Disaster
Recovery
Co-Managed ITComplianceEmergency Ransomware
Recovery
Penetration & Vulnerability
Assessment

Optimization of Processes

Microsoft 365 OptimizationVirtual CIO ServicesPenetration TestingInventory Lifecycle
Management
Transforming SMEs with AI
Industries
Icon dropdown arrow
Dental Managed IT Services
Construction
Hotels & Hospitality
Franchises
Financial & Insurance Services
Government
Health Care & PharmaceuticalLegal & Professional Services
Local Small & Medium Businesses
Manufacturing
Non-profit
Real Estate
Retail
Transportation & Logistics
Enterprise & Consulting
Publicly Traded Companies
Our Story
Icon dropdown arrow
About UsTestimonials
Partners
Sponsorship
BlogContact Us
Open menuClose menu
Icon chevron up
Browse Blog:
Business
Insight
Advice
Insight

SharePoint Information Architecture: A Practical Guide

SharePoint Information Architecture: A Practical Guide

SharePoint information architecture is the plan for where your content lives, how it is labelled, how people move through it and who can see it. Get it right and staff find the current version of a document in seconds. Get it wrong and SharePoint turns into a second shared drive that nobody trusts. For a small or mid-sized business, the sound approach is a flat set of purpose-built sites, a few hubs, consistent metadata and permissions decided before content is moved in. It is also work that goes faster with a Microsoft 365 team beside you: our Microsoft 365 Optimization service covers this ground.

This guide explains the building blocks in plain language, then gives you an order of work you can follow.

NetFusion Designs Inc
nfd.ca
Make SharePoint Easier to Navigate
NetFusion’s Microsoft 365 Optimization service helps businesses organize SharePoint content, permissions, and navigation around how teams work.
Visit

TL;DR

  • Information architecture covers navigation, search, site hierarchy, metadata and security, not just folders. Microsoft describes it as how you organize and label content and how people use it to get work done.
  • Modern SharePoint is flat: every site is its own site collection, and hubs connect related sites instead of subsites nesting inside each other.
  • Use columns and content types (metadata) instead of deep folder trees. More than one or two levels of folders makes content hard to find.
  • Decide permissions, retention and ownership up front. Hub association does not change who can open what.
  • Treat the design as ongoing. People, projects and organizations change, and the structure has to follow.

Table of Contents

  • What information architecture means in SharePoint
  • The building blocks
  • Three kinds of sites, and what each is for
  • Flat structure, not subsites
  • Navigation that answers three questions
  • Metadata beats folders
  • Permissions, search and governance
  • How SharePoint fits with Teams and OneDrive
  • An order of work for a small or mid-sized business
  • Where we can help
  • Our perspective
  • FAQ
  • Sources

What information architecture means in SharePoint

Think of a filing room. The cabinets, the labels on the drawers, the sign on the door and the keys each person holds are all part of how well the room works. In SharePoint Online, those are sites, libraries, metadata, navigation, search and permissions.

Microsoft’s guidance defines information architecture as how you organize and label content and how visitors interact with it, including navigation, search, site hierarchy, taxonomy (a shared set of labels and categories) and security. In modern SharePoint it also means making sure the right content reaches the right people while following content compliance regulations. Microsoft’s overview adds that a well-planned structure improves adoption and productivity and reduces information overload, IT cost and compliance and security risk.

For an Ontario law firm, accounting practice, clinic or manufacturer, that last point is the one that matters most. Client files, patient records and engineering drawings need a clear owner, a clear home and a clear audience. A structure that grew by accident cannot give you that.

The building blocks

You only need to know a handful of terms to plan well.

  • Site: a workspace for a team, a project or a topic. Each has its own libraries, pages and permissions.
  • Library: a place for files inside a site. A list is the same idea for rows of data, such as a register or a tracker.
  • Page: a web page inside a site, used for news, policies or a home page.
  • Hub site: a site that connects related sites, so they share navigation, search scope and look and feel.
  • Metadata: information about a file, such as client name, matter number, document type or year.
  • Content type: a reusable template that pairs a kind of document (an engagement letter, a work order) with the metadata and rules that go with it.

Microsoft’s content planning guidance says to decide which lists, libraries and pages you need and whether to create content types, which let site owners pre-configure details so content stays consistent across sites. ShareGate’s overview of the building blocks adds that a content type can define how an item is treated, including its required metadata and retention schedule.

Three kinds of sites, and what each is for

Most confusion starts when every site is created the same way. Microsoft’s hub planning guide separates three purposes:

Site type Purpose Typical use
Team site Collaboration for a defined group. Connected by default to a Microsoft 365 group, with Teams and Planner available. A project, a department, a client matter
Communication site Broadcasting content to many readers HR policies, company news, onboarding, product documentation
Hub site Connecting related sites with shared navigation and content roll-up A department family, a region, a service line

A practical rule: if people work together on files, use a team site. If a few people publish and most people read, use a communication site. If you have several sites that belong together, put them under a hub.

Flat structure, not subsites

If you remember SharePoint from a decade ago, you may expect a tree: a top site with subsites several levels down. Modern SharePoint does not work that way. According to Microsoft’s guide to the modern experience, every site is a site collection associated to hubs in a flat structure, which replaces the classic subsite hierarchy.

This changes how you plan. You no longer draw one big tree and slot everything into it. Instead you create sites for real business units or purposes, and then group them with hubs. A site can be moved between hubs later without rebuilding it, so the structure can change as the business does.

Classic subsites compared with modern SharePoint hubs

Microsoft’s portal guidance also warns about common failures: too many top-level site collections, content buried too deep, and poor master data management leading to poor taxonomy. Its portal information architecture guidance says planning should start from business objectives, organizational structure, content type (collaborative or published), classification and confidentiality, content life cycle and retention, and how people actually behave and what tasks they perform.

An example for a 60-person professional services firm

A reasonable starting point might look like this:

  • A communication site called Firm Hub Home for news, policies and the staff directory.
  • A hub site for Client Services, with associated team sites for each practice group.
  • A hub site for Operations, associated with HR, Finance and IT team sites.
  • A team site per major internal project, created from a template, with an owner named at creation.
  • One library per document family inside each team site, such as Engagement Letters or Invoices, each with the same columns.

That is around a dozen sites for 60 people, not hundreds. The aim is that someone new can guess where something lives.

Navigation that answers three questions

Microsoft’s navigation planning guide frames navigation around organizing (grouping similar intents), labelling (clear names), usability and findability. It also recommends progressive disclosure, so a visitor can always answer three questions: where am I, what can I do here, and where can I go next?

In practice:

  1. Use the words staff use. Label a link “Submit expenses”, not “Finance Portal Services”.
  2. Keep the top level short. A handful of links on the hub navigation is easier to scan than twenty.
  3. Put the same links in the same place. Hub navigation appears across all associated sites, so consistency is built in if you use it.
  4. Test with real tasks. Ask three colleagues to find a specific document and watch where they click.

If you are planning navigation across a global, hub and local level, general site architecture best practices cover the same logic of keeping hierarchy shallow and paths short.

Metadata beats folders

Folders feel natural because they mirror a file share. They fail because a document can only sit in one folder, and every extra level makes the path harder to remember. Microsoft warns that folder structures with more than one or two levels of nesting create a significant discoverability burden, and recommends topic-specific libraries with site columns instead.

The same page names columns and content types as the two most important metadata elements. Metadata lets users filter and sort inside a library and improves search. Using columns in the Site Pages library also lets highlighted content web parts connect related pages based on shared metadata.

A worked example

An accounting practice stores year-end files by client. The old share has paths like Clients / Smith Corp / 2025 / Tax / Working Papers / Drafts. In SharePoint, you would build one library with these columns:

  • Client (choice or managed metadata)
  • Fiscal year
  • Document type (working paper, return, correspondence)
  • Status (draft, final, filed)

Now a partner can filter to all final returns for 2025 across clients, or open a saved view for one client. A single flat library with four columns does more than six folder levels, and it does not break when a client is renamed.

Before you build, agree on the column list and who maintains it. Site columns defined once and reused across libraries keep labels identical everywhere. Two libraries that call the same thing “Client” and “Customer” will undo the benefit.

Permissions, search and governance

Structure and security are linked, so plan them together.

Permissions. Microsoft states that associating a site with a hub does not change its permissions. Content rolled up on a hub is security-trimmed, meaning people only see items they already have access to. Associating a site with a hub is therefore safe from a visibility point of view, but it does not grant access either. Give each site an owner who decides who gets in, and keep the number of unique permission exceptions low, because every exception is something someone must remember later. For client records, health information or anything under confidentiality obligations, set access by group, not by individual.

Search. In modern SharePoint, search is personal and contextual. Per Microsoft’s modern experience guide, searching from the tenant root covers all of SharePoint, searching from a hub covers its associated sites, and searching from a site or library is scoped to that site or library. This is a strong reason for hubs: a hub gives a department its own search scope without extra work.

Governance. Governance is the set of rules that stops the design decaying. Microsoft’s intranet governance guidance says it should cover navigation architecture (how sites and hubs are associated), page architecture guidelines for consistent home pages, metadata architecture (columns and content types) and search experiences, including discovery attributes such as acronyms, bookmarks and Q&A. Put another way, someone should own the answers to four questions: who can create a site, who approves a new hub association, who changes the shared columns, and who reviews what appears in search.

If your team also builds apps on top of SharePoint data, our note on Power Apps governance covers how to keep those under control too.

Permissions, search and governance

How SharePoint fits with Teams and OneDrive

Many businesses design SharePoint and then find that half their files are somewhere else. The reason is that Teams does not store files itself. Files shared in a standard Teams channel sit in the SharePoint site behind that team, while files shared in a one-to-one or group chat sit in the sender’s OneDrive. That means your SharePoint plan has to include Teams: each team you create also creates a SharePoint site, so the rules for who may create teams are really rules for who may create sites.

A workable division:

  • OneDrive for personal drafts and work in progress that no one else needs yet.
  • Teams channels for working conversations and the files attached to them, which are stored in the team’s SharePoint site.
  • SharePoint libraries for anything that must be found, retained and governed: the authoritative copy.

Tell staff the rule in one sentence: when a file is final, it lives in the library, not in a chat. Our guide to file sharing for multi-location teams explains how this plays out when offices in different cities share the same documents. For professional services, SharePoint for law firms goes deeper on matter-based structures.

An order of work for a small or mid-sized business

Canadian guidance aimed at organizations under 500 employees, published by Internee, suggests starting with well-structured communication sites as the authoritative home for HR policies, product documentation, org charts and onboarding, linking Teams channels to the relevant libraries and configuring Microsoft Search from the start, with editorial bookmarks and acronym definitions added in the Microsoft Search admin center. It also observes that small organizations rarely lack information. Their problem is that it is scattered across places with no agreed home.

That points to this sequence:

  1. Inventory what you have. List shared drives, mailboxes, Teams and any existing SharePoint sites. Note owner, size and last use.
  2. Define the content families. For each, record the document type, who edits it, who reads it, how long it must be kept and how confidential it is.
  3. Choose the sites and hubs. One site per real purpose, grouped under hubs by department or service line.
  4. Define columns and content types. Start with the four or five you will use everywhere, such as client, document type, status and year.
  5. Set permissions by group. Owners, members and visitors for each site, nothing granted to individuals unless unavoidable.
  6. Configure navigation and search. Hub navigation first, then bookmarks for the ten things people look for most.
  7. Migrate in waves. Move one department, test with real tasks, adjust, then continue. If you are moving from file servers or another tenant, see our Microsoft 365 migration steps and tenant to tenant migration notes.
  8. Review on a schedule. Check usage, search terms that return nothing and sites with no owner.

Licensing affects some of these choices, for example which compliance and retention features are available to which users, so check your plan early with our Microsoft 365 licensing guide.

Mistakes that cost the most

  • Copying the file share. Recreating the old folder tree inside SharePoint keeps the old problems and adds new ones.
  • Too many top-level sites. Microsoft’s portal guidance lists this as a known failure. Each extra site is another owner, another permission set and another place to look.
  • Skipping retention. If nobody decides how long a document is kept, content piles up and is hard to dispose of later.
  • No named owner. A site without an owner is the first to go stale.
  • Treating it as a one-off. Microsoft’s guidance is clear that information architecture should be measured and evolved over time, since the best structure may not be obvious to end users at the start.

Where we can help

NetFusion Designs is a Managed IT and AI enablement provider for small and mid-sized businesses across Ontario and Canada, with teams in Kitchener-Waterloo, Toronto, Markham, Mississauga, Montréal and Winnipeg. Microsoft 365 is part of our fully managed IT, alongside security, monitoring and helpdesk, so the structure you design in SharePoint sits inside an environment we already look after, with a SOC 2 Type II certified team behind it.

If you want a SharePoint structure planned and then kept in order, see our Microsoft 365 Optimization service. For ongoing management of your whole environment, start with Managed IT Services.

NetFusion Designs Inc

We plan the work in plain language, so owners and partners know what is changing and why. If your internal IT person is stretched, our co-managed IT option lets us take the Microsoft 365 work while your team keeps the rest.

Our perspective

Most SharePoint problems we are asked about are not technical. The platform does what it was designed to do. What goes wrong is that nobody decided what belongs where, who owns it and how long it should live.

We think of information architecture as part of running IT, not a one-time project. It touches security, because permissions and retention are structure decisions. It touches compliance, because regulated firms need to show where records are and who can see them. And it touches adoption, because people stop using a system they cannot navigate.

That is why we prefer to have one provider responsible for Microsoft 365, security and support together. When the same team manages your tenant, your helpdesk and your protection, a new site gets the right owner and the right access from day one, and nobody has to coordinate between vendors. Our approach is plain-language communication, predictable monthly pricing and a clear record of what was set up.

Start small, pick a few sites, name owners, and review. A calm, well-labelled SharePoint is within reach of any business with 10 people or 500.

Geeshan

FAQ

What is the difference between SharePoint and Microsoft 365?

Microsoft 365 is the whole subscription: email, Teams, OneDrive, Office apps and security tools. SharePoint is one service inside it, used for sites, document libraries and intranet pages. Teams channel files are stored in SharePoint, so the two are closely linked.

Should I use folders or metadata in SharePoint?

Use metadata as your main method and keep folders to one or two levels at most. Microsoft notes that deeper folder nesting makes content harder to find. Columns let one document be filtered by client, year, type or status without being copied.

Do I need a hub site?

You need one when several sites belong together and should share navigation and search, such as all your practice groups or all your plants. Hubs do not change permissions, so they are a safe way to connect sites. A very small company with a few sites can begin with a single communication site as its home page.

How often should we review our SharePoint structure?

Treat it as ongoing. Microsoft describes information architecture as iterative, because organizations, people and projects change. A review each quarter of sites without owners, unused libraries and failed searches is a sensible routine for most small businesses.

Sources

  • Introduction to SharePoint information architecture, Microsoft Learn
  • Plan the content for your SharePoint site, Microsoft Support
  • Building a SharePoint information architecture, ShareGate
  • Planning your SharePoint hub sites, Microsoft Learn
  • Guide to the modern experience in SharePoint, Microsoft Learn
  • Portal information architecture, SharePoint developer documentation
  • Plan and implement SharePoint site navigation, Microsoft Learn
  • Planning intranet governance, Microsoft Learn
  • Microsoft 365 knowledge hub architecture, Internee
  • Site architecture best practices

Recommended

  • Power Automate Examples: Workflows for IT and Business
  • Microsoft 365 Optimization

Continue Reading

Microsoft Teams as a Call Centre: Queues and Setup
Microsoft Teams as a Call Centre: Queues and Setup
AI Change Management: A Practical Guide for Canadian SMBs
AI Change Management: A Practical Guide for Canadian SMBs
Privileged Access Management: A Practical Guide for Small Business
Privileged Access Management: A Practical Guide for Small Business
New Employee IT Onboarding Checklist for Small Businesses
New Employee IT Onboarding Checklist for Small Businesses
NetFusion Designs logo
NetFusion Designs is a globally recognized IT service provider and services clients across North America.

We hold a SOC 2 Type 2 report, and maintain internal processes and procedures that keep our clients’ data secure and confidential.
NetFusion Designs IT support team

IT Services Near Me

BurlingtonOakvilleHamiltonMississaugaMiltonBramptonEtobicokeBrantfordGuelphKitchenerWaterlooCambridgeSt CatharinesTorontoMarkhamCaledonNewmarketNorth YorkPickering & DurhamLondonMontreal

Services

Project PlanningHardwareTelephony & VoIPApplication DevelopmentCloud DesktopSecurity CamerasHelpdesk & SupportCyber Security & Anti-VirusData Backups & Disaster RecoveryMicrosoft 365 OptimizationVirtual CIO ServicesPenetration TestingPricingSchedule a MeetingRemote Support
Pricing

Pages

Free Security ScanAbout UsOur Migration ApproachWork CultureOur Core ValuesCode of ConductTestimonialsContactBlogSchedule a MeetingRemote Support

TORONTO

Bank capital office building law
401 Bay St, 16th Floor, Toronto Ontario
Email
info@nfd.ca
Phone
647-476-5259 (Canada)

MARKHAM

Bank capital office building law
141 Main Street N, Markham, ON L3P 1Y2
Email
info@nfd.ca
Phone
647-476-5259 (Canada)

TRI-CITY AREA
(Kitchener / Waterloo / Cambridge)

Bank capital office building law
22 Frederick St, Suite 700, Kitchener Ontario
Email
info@nfd.ca
Phone
647-476-5259 (Canada)

PEEL REGION

Bank capital office building law
6700 Century Ave, 3rd floor, Mississauga, ON L5N 1V8
Email
info@nfd.ca
Phone
647-476-5259 (Canada)

DURHAM REGION

Bank capital office building law
1315 Pickering Parkway, Pickering, ON L1V 7G5
Email
info@nfd.ca

MONTREAL

Bank capital office building law
8815 Av du Parc #402, Montréal, QC H2N 1Y7
Email
info@nfd.ca
Phone
647-476-5259 (Canada)

Special Offers

Radio station signal antena tower
Pricing: $100–185 per user
Icon chevron right
Terms and ConditionsPrivacy PolicyCookie Policy
© 2026 NetFusion Designs Inc.
LinkedInFacebookAlignable logo