SharePoint Information Architecture: Design Guide for Enterprise Success

What Is SharePoint Information Architecture?

SharePoint information architecture (IA) is the structural design of your SharePoint environment — how content is organized, labeled, and navigated. A well-designed IA makes information findable, governance sustainable, and search accurate. Poor IA leads to site sprawl, duplicate content, and user abandonment.

For enterprise organizations, IA decisions made at deployment define how well SharePoint scales for 5, 10, or 20 years.

The Foundation: Hub Site Topology

The modern SharePoint IA is built on hub sites — a flat, association-based model that replaced the legacy subsite hierarchy after 2018.

Why Flat Beats Hierarchical

Legacy SharePoint subsites created permission inheritance nightmares and deep navigation trees. Hub sites solve this:

| Model | Subsites | Hub Sites |

|-------|----------|-----------|

| Structure | Parent/child hierarchy | Flat + association |

| Navigation | Inherited, rigid | Shared, flexible |

| Permissions | Inherited by default | Independent per site |

| Search | Site collection scoped | Hub-scoped rollup |

| Governance | Hard to manage | Manageable at hub level |

Hub Site Topology Patterns

Divisional Hub Model (best for large enterprises 5,000+ users):

• Corporate Hub → links to Division Hubs (HR, Finance, Legal, IT, Operations)
• Each Division Hub → links to Department/Team Sites
• Maximum 2 hub levels recommended

Functional Hub Model (best for mid-market 500-5,000 users):

• Intranet Hub (communications focus)
• Project Hub (project sites)
• Department Hub (team collaboration)

Geographic Hub Model (best for global enterprises):

• Americas Hub → US, Canada, LATAM sites
• EMEA Hub → UK, EU, APAC sites
• Common Services Hub → HR, IT, Legal (global)

Site Types and When to Use Each

Communication Sites

• Purpose: Broadcast information to large audiences
• Use for: Intranet homepages, departmental news, policy portals, executive comms
• Governance: Tightly controlled publishing, limited editors
• Search: Designed to be found company-wide

Team Sites (M365 Group-connected)

• Purpose: Collaborative work among defined team members
• Use for: Project sites, department working sites, cross-functional teams
• Governance: Team members control their own space
• Search: Scope by default to team, searchable company-wide with proper labels

Team Sites (non-group)

• Purpose: Structured content repositories without a linked Team
• Use for: Records repositories, regulated content stores, policy libraries
• Governance: Strict permission management without group overhead
• Search: Configured per sensitivity level

Document Centers

• Purpose: Manage large volumes of documents with content type governance
• Use for: Enterprise document libraries with 10,000+ items
• Governance: Content Type Hub publishing, mandatory metadata

Metadata Taxonomy Design

Metadata is the backbone of SharePoint IA. Without it, search, filtering, and content organization fail at scale.

Managed Metadata vs. Site Columns

Managed Metadata (Term Store):

• Centrally managed in SharePoint Admin Center → Content Services → Term Store
• Terms are consistent across all site collections
• Enables enterprise search refiners, cross-site filtering
• Required for: Department, Geography, Document Type, Project, Client

Site Columns:

• Defined at site or content type level
• Good for: Team-specific tags, project-specific metadata not needed enterprise-wide
• Risk: Proliferate without governance

Essential Managed Metadata Term Sets

```

Term Store Structure:

├── Document Management

│ ├── Document Type

│ │ ├── Policy

│ │ ├── Procedure

│ │ ├── Contract

│ │ ├── Report

│ │ └── Form

│ ├── Confidentiality

│ │ ├── Public

│ │ ├── Internal

│ │ ├── Confidential

│ │ └── Restricted

│ └── Retention Schedule

│ ├── 1 Year

│ ├── 3 Years

│ ├── 7 Years

│ └── Permanent

├── Organization

│ ├── Department

│ │ ├── HR

│ │ ├── Finance

│ │ ├── Legal

│ │ └── IT

│ └── Geography

│ ├── North America

│ ├── EMEA

│ └── APAC

└── Projects

├── Project Status

│ ├── Active

│ ├── On Hold

│ └── Closed

└── Project Type

```

Metadata Governance Rules

• Mandatory fields at upload: Document Type + Department minimum
• Default values: Pre-populate Department based on site
• Validation: Required fields enforced at library level, not power automate
• Term set ownership: Each term set has a designated owner who approves new terms
• No free-text tags: Controlled vocabulary only for enterprise-wide metadata

Navigation Design

Global Navigation (Tenant-wide)

Configured in SharePoint Admin Center → Settings → Global Navigation. Appears across all SharePoint sites when the app bar is enabled.

Structure your global nav to 5-7 items maximum:

• Home (Intranet Hub)
• News & Updates
• My Sites
• Tools & Resources
• Departments
• Help & Support

Hub Navigation

Hub navigation appears on all sites associated with the hub. Limit to 6-8 items. Use audience targeting (Microsoft 365 groups) to show/hide items by department or role.

Local Navigation

Each site has its own left navigation (Teams-connected sites) or top navigation. Follow the rule: 3 clicks to any content from the site homepage.

Mega Menu Design

Communication sites support mega menus — use them for sites with 20+ content areas. Structure:

• Top-level: 5-6 parent items
• Second level: 4-8 items per parent
• Never go to a third level in mega menus

Content Types and the Content Type Hub

Content types define the schema for documents across your environment. The Content Type Hub publishes types to all site collections.

Enterprise Content Types to Define

| Content Type | Inherits From | Metadata Fields |

|-------------|---------------|-----------------|

| EPC Policy | Document | Department, Effective Date, Review Date, Owner, Confidentiality |

| EPC Contract | Document | Client, Value, Expiry Date, Contract Type, Confidentiality |

| EPC Project Document | Document | Project, Phase, Version, Document Type |

| EPC Meeting Notes | Document | Meeting Date, Attendees, Action Items |

| EPC Report | Document | Report Period, Author, Department |

Content Type Hub Configuration

• Designate one site collection as the Content Type Hub (Admin Center → Settings)
• Create content types in the hub
• Publish to all site collections (Manage Publishing → Publish)
• Subscribe site collections to receive published types
• Apply content types to libraries via List Settings → Content Types

SharePoint Search Configuration

Search quality directly depends on IA quality. Key configurations:

Crawled vs. Managed Properties

Crawled properties are auto-detected from site columns. Map them to managed properties to enable search refiners and KQL queries:

• `RefinableString00` → Document Type managed metadata
• `RefinableString01` → Department managed metadata
• `RefinableDate00` → Document Effective Date
• `RefinableString10` → Project Name

Result Sources

Configure result sources for hub-scoped and department-scoped searches:

```

Result Source: HR Documents

Query: path:"https://contoso.sharepoint.com/sites/HR*"

ContentType:"EPC Policy" OR ContentType:"EPC Procedure"

```

Search Schema Best Practices

• Alias managed properties to friendly names (e.g., `DocumentType` not `RefinableString00`)
• Enable the top 10 most-used managed properties as refiners
• Configure promoted results (best bets) for top 20 frequently searched terms
• Set up result blocks for people, sites, documents separately

Governance Framework for IA

Site Provisioning Process

Never allow self-service site creation in enterprise environments. Use:

• Request form (SharePoint or Power Apps) — captures purpose, owner, hub association, retention
• Automated provisioning (Power Automate + PnP PowerShell) — creates site with standard template
• Owner training (mandatory before handover)
• Lifecycle policy — sites reviewed at 90 days if no activity

Site Lifecycle Management

Sites without activity become stale, consuming storage and polluting search. Implement:

• Activity monitoring: PowerShell script weekly to identify sites with 0 unique views in 90 days
• Owner notification: Automated email via Power Automate asking owner to confirm site is active
• Archive workflow: Sites confirmed inactive → read-only for 30 days → archived to cold storage
• Deletion: Archived sites deleted after 180 days per retention policy

```powershell

# Identify stale sites (0 activity in 90 days)

Connect-PnPOnline -Url "https://contoso-admin.sharepoint.com" -Interactive

$sites = Get-PnPTenantSite -IncludeOneDriveSites $false

foreach ($site in $sites) {

$lastActivity = $site.LastContentModifiedDate

$daysSinceActivity = (Get-Date) - $lastActivity

if ($daysSinceActivity.Days -gt 90) {

Write-Output "$($site.Url) - Last modified: $lastActivity"

}

}

```

Common IA Anti-Patterns to Avoid

| Anti-Pattern | Problem | Solution |

|-------------|---------|----------|

| Deep subsite hierarchy | Permissions nightmare, navigation complexity | Migrate to flat hub model |

| No content types | Inconsistent metadata, poor search | Define and enforce via Content Type Hub |

| All files in one library | Governance impossible at scale | Structure by type: Contracts, Policies, Projects |

| Free-text tags only | Inconsistent taxonomy, search refiners fail | Managed metadata term sets |

| No naming convention | Users can't find sites/files | Enforce naming via provisioning template |

| Permissions at document level | Unmanageable overhead | Permissions at library/site level only |

| Guest access unchecked | Security risk | Conditional Access + access reviews |

Migration IA Redesign

When migrating from legacy SharePoint (2013/2016/2019) or file shares, IA redesign is mandatory.

Migration IA Assessment Checklist

• [ ] Inventory all source sites, libraries, folders, document counts
• [ ] Identify content owners for each area
• [ ] Map source structure to target hub/site/library topology
• [ ] Define content type mapping (source document types → target content types)
• [ ] Design metadata migration plan (folder structure → managed metadata columns)
• [ ] Create naming convention standards for target sites and libraries
• [ ] Plan permission migration (groups, not individuals)
• [ ] Define retention schedule mapping

Conclusion

SharePoint information architecture is the most consequential decision in any deployment. Get it right at the start — the cost of retrofitting IA after thousands of sites and millions of documents are created is enormous.

EPC Group designs enterprise SharePoint information architectures for organizations migrating from legacy systems and building new environments from scratch. Contact us for an IA assessment and design engagement.