By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Cookie Policy for more information.
If you’re designing or evolving an enterprise intranet for 20,000+ employees, SharePoint hub sites are one of your most strategic building blocks. They’re the backbone for consistent navigation, scoped search, and news rollups, but they also arrive with very real constraints.
At this scale, the gaps show up fast: navigation buckles, news floods the wrong audiences, permissions get brittle, and multi-geo/multilingual realities add more moving parts.
TL;DR (What leaders should know)
A site can join only one hub at a time. Cross-functional experiences require patterns beyond simple association.
Hub-to-hub extends search across hubs, but web part rollups (like “All sites in the hub”) stay within the original hub. Don’t architect on an assumption that content rollups cross hubs.
Navigation has hard ceilings: up to 500 child links per level (with ~100 recommended in practice) and the Sites web part caps at 99 when set to “all sites in the hub.”
Hub permissions sync is visitors-only, capped at 10 principals (users or groups), and can take up to 4 hours to propagate. There’s no approval flow to leave a hub.
You can create up to 2,000 hub sites per tenant; a site already associated with a hub can’t be converted into a hub.
News flows up to the hub. The News web part can source from “All sites in the hub,” but not across hub-to-hub associations.
Multi-Geo and multilingual add nuance: cross-geo association/search works, but navigation/title translations are manual (and may take time to propagate).
1) One-Hub Association Meets Cross-Functional Reality
The challenge: In a large enterprise, content often belongs to more than one story (e.g., HR + Region; Product + Market). But each site can be associated to only one hub at a time, which forces hard trade-offs for IA and ownership.
Why it matters: If you try to make one “mega hub” carry every scenario, users drown in navigation and irrelevant rollups. If you keep hubs laser-focused, you still need a pattern for cross-cutting journeys (e.g., “New Manager” onboarding across HR, Finance, IT).
What good looks like:
Treat hubs as families with a clear scope (function, region, business line), and use links and curated pages to bridge out to other hubs.
Use managed metadata + Highlighted Content with targeted filters for cross-cutting collections (not raw hub rollups).
Leverage hub-to-hub association for search, not content rollups; design pages that reference content via metadata or specific “select sites” rather than “all sites in the hub.”
2) Hub-to-Hub: Great for Search, Not a Free Pass for Rollups
The challenge: Hub-to-hub association extends search across related hubs (up to three levels), but web parts configured to show “all sites in the hub” remain scoped to the original parent hub. Your content aggregation strategy cannot rely on hub-to-hub to automatically broaden rollups.
What good looks like:
Use hub-to-hub to expand discovery (search results/breadcrumbs), while designing purpose-built landing pages that aggregate content by metadata or explicit “select sites” sources.
3) Navigation at Scale: Hard Limits and Human Limits
The challenge: You’ll hit structural limits and attention limits.
500 child links per level is the technical ceiling; Microsoft recommends ≤100 for usability.
The Sites web part, handy for auto-listing hub sites, caps at 99 when set to “all sites in the hub.
What good looks like:
Keep hub nav to 3 levels max (that’s the product limit) and prefer category landings over endless link lists.
Use audience-targeted nav and card-style landing pages to funnel users quickly.
Promote consistent naming conventions (e.g., “HR Central,” “Sales Hub”) so people learn the system.
4) Permissions: “Visitors-Only” Sync and the 10-Principal Ceiling
The challenge:Hub permissions sync sounds like a shortcut…and sometimes is. But it only pushes a Visitors group to associated sites, it’s limited to 10 users or groups, and updates can take up to 4 hours. Also, there’s no approval flow to leave a hub, sites can disassociate freely.
Scale implications:
For company-wide read, you’ll likely add broad groups (e.g., “Everyone except external users”) at the hub, then let the visitors sync do its thing and govern exceptions at the site level.
Remember SharePoint group limits when planning membership scale (e.g., group and user limits per site). Group-based strategies are mandatory at 20k+.
What good looks like:
Define a permissions blueprint per hub family (who gets visitor/member/owner, how exceptions are handled).
Limit hub sync for broad read; use local groups for creation rights and sensitive areas.
Monitor changes: leaving a hub removes the synced visitors from that site. Plan for the ripple effect.
5) News & Content Rollups: Powerful, but Opinionated
The challenge: Hub news flows up from associated sites and can be sourced as “All sites in the hub.” That’s excellent for visibility, but it’s easy to over-aggregate and swamp the front page. Rollups don’t cross hub-to-hub associations.
Use Organization News for official comms and Boosted News for time-critical messages (e.g., mergers, safety).
Build dual rail patterns on your hub home: left rail for curated corporate news; right rail for “all sites in the hub” (or specific sites) to capture distributed stories without burying the signal.
6) Scale & Limits You’ll Actually Hit
Hub limits: Up to 2,000 hubs per tenant; no limit on associated sites per hub. (And yes: a site already associated can’t be converted into a hub.)
Performance guidance: Microsoft advises practical caps. Don’t assume “unlimited” associations yield a good experience; design for manageable rollups and findability.
Multi-Geo: Sites can associate to a hub regardless of the hub’s geography, and users get unified search across the hub. Plan navigation and compliance with data residency in mind.
Multilingual:Navigation titles, site names, and footers are translated manually; changes can take time to propagate across hub navigation. Bake translation workflows and SLAs into your publishing process.
8) Governance Guardrails (What we implement with clients)
Association policy: Who can associate; approval to join (Flow), no approval to leave—so design detection and remediation.
Navigation standards: Labeling, depth, audience targeting, max link counts.
News playbook: Organization News, metadata, boosting rules, and site-owner guidance.
Permissions model: Visitors strategy (sync vs local), exception handling, and sensitive sites.
Multi-Geo & multilingual: Translation ownership, cadence, and cross-geo experience testing.
Lifecycle: Site creation criteria, periodic reviews, quality checks, and de-association rules
9) Reference IA Patterns We Recommend
Corporate Communications Hub (Org News + policy libraries) with curated rollups from HR, IT, Legal.
Function Hubs (HR, Sales, Finance) with tight editorial control; distributed team sites roll up selectively by metadata.
Regional Hubs (EMEA, APAC, Americas) leveraging audience-targeted nav; cross-link into function hubs for shared topics.
Program/Initiative Hubs for cross-functional missions; use hub-to-hub association to expand search between program and host function.
Closing Thought
At enterprise scale, hub sites aren’t just a feature, they’re an architectural decision. The difference between a thriving intranet and a tangled mess often comes down to clear scope, metadata-driven design, and governance discipline.
Treat hubs as strategic families, not catch-alls, and build patterns for cross-cutting journeys. Do that, and your intranet becomes more than a collection of sites. It becomes a connected experience that scales with your organization.
