SharePoint hub sites
A hub site is an ordinary SharePoint site that an administrator has registered as a hub, so other sites can associate with it. Associated sites inherit the hub’s shared navigation and theme, roll their content up into the hub’s web parts, and join the hub’s search scope. Hubs are how modern SharePoint imposes structure on a deliberately flat estate: instead of nesting sites inside each other as subsites, you connect independent sites side by side and each keeps its own permissions, storage and ownership.
Part of the SharePoint reference · Limits verified against Microsoft documentation · Last reviewed 1 September 2026
What association actually inherits
This is the whole subject in one list, and getting it wrong is the source of most disappointment with hubs. Association gives you four things — and four things people commonly expect but do not get.
- Shared navigationThe hub's navigation bar appears on every associated site.
- ThemeThe hub's theme and logo propagate to associated sites.
- Search scopeThe site joins the hub's search scope, so hub search covers it.
- Content roll-upNews, Events, Sites and Highlighted content pull from the site when the source is set to all sites in the hub.
- Permissions — not inheritedAssociation does not change permissions. Associate a restricted site and only people with access see its rolled-up content.
- A place in the navigation — not automaticAssociating does not add the site to the hub menu. Hub owners choose what appears there.
- Governance policies — not inheritedRetention labels, sensitivity classifications and sharing restrictions must still be set per site or per tenant.
- A permissions hierarchy — does not existEvery associated site stays an independent site collection. Hubs are a navigation and search construct, not a parent-child tree.
Limits and thresholds
One of these figures is worth reading carefully, because published guidance disagrees with Microsoft.
| Hard limits — enforced by the service | |
| Hub sites per tenant | 2,000 |
|---|---|
| Associated sites per hub (per Microsoft) | Unlimited |
| Hubs a single site can join | 1 |
| Can an associated site become a hub? | No |
| Supported hub-to-hub nesting levels | 1 |
| Child links per navigation level | 500 |
| Sites web part, source “all sites in the hub” | 99 |
| Registration changes take effect within | 2–4 hours |
| Practical guidance — exceed at a cost | |
| Navigation links per level, recommended | 100 |
| Hubs for a 5,000-person organisation | 8–15 |
| Navigation depth | 3 levels |
Sources: Microsoft Learn, Register-SPOHubSite (2,000 hubs per tenant, unlimited associated sites, 2–4 hour propagation); Microsoft Learn, Planning your SharePoint hub sites; Microsoft Learn, Introduction to SharePoint information architecture (500 child links per level). Verified 1 September 2026. See the full SharePoint limits table for platform-wide figures.
A conflict worth knowing about Microsoft’s own PowerShell documentation describes associated sites per hub as unlimited. Several widely-read third-party guides state a cap of 1,000 or 2,000. We have not found that figure in current Microsoft documentation, so we quote Microsoft and flag the disagreement rather than pick a side. If you are approaching either number, test in a non-production tenant.
Nesting, and what does not cross the boundary
One level of hub-to-hub nesting is supported: a parent hub with child hubs, each holding its own associated sites. Deeper chains can be configured but behave unpredictably, particularly for roll-up web parts.
The constraint that catches architects out applies even to supported nesting. Hub-to-hub association extends the search scope, but web part roll-ups do not cross it. A News web part on the parent hub set to “all sites in the hub” returns posts from the parent hub’s own associated sites — not from sites hanging off the child hubs. If your information architecture assumes a single company-wide newsfeed aggregating up through a hub tree, it will not work that way.
The four common mistakes
- A hub per team. Hubs represent major organisational groupings, not individual teams. Fifty hubs produces navigation nobody can follow; eight to fifteen usually serves a large organisation well.
- Deciding hubs after associating. A site already associated with a hub cannot be converted into a hub. Choose which sites will be hubs first.
- Deleting a hub without unregistering it. Associated sites are left with stale hub metadata, and their navigation and roll-ups break quietly rather than throwing an error.
- No exit policy. Joining a hub can be gated with an approval flow. Leaving cannot. You need detection and remediation rather than prevention.
Key takeaways
- 4 things only Association inherits navigation, theme, search scope and roll-up That is the complete list. Not permissions, not governance policies, and not a place in the hub menu — hub owners choose that separately.
- 1 hub per site A site can only join one hub, ever, at a time The biggest constraint on hub architecture. A site serving two business units has to pick, and express the other relationship through navigation or search.
- 8–15 not 50 The tenant limit of 2,000 is not a target A hub per team is the commonest mistake. Hubs should map to business units, functions or geographies.
- 99 sites max The real ceiling is in the web parts, not the association Microsoft calls associated sites unlimited, but the Sites web part returns 99 and navigation caps at 500 links per level.
- 1 level nesting Roll-ups do not cross a hub-to-hub relationship Nesting extends search but not content aggregation. A company-wide feed built on a hub tree will not collect posts from child hubs' sites.
- 2–4h propagation Wait before you reconfigure Registration and permission changes take hours to appear. Reconfiguring mid-propagation is a reliable way to create a half-applied mess.
Hubs and how the intranet looks
A hub propagates a theme, which is not the same as propagating a design. Theme inheritance covers colours and logo. It does not make the associated sites look like they belong to the same intranet, because layout, typography, page structure and component treatment are all set per page by whoever built it.
The visible result on most estates is a hub whose navigation bar is consistent and whose twenty associated sites look like twenty different products. That is not a hub configuration problem and no amount of admin centre work fixes it.
Consistency below the navigation bar
ShortPoint is a no-code design layer for SharePoint. It does not change your hub architecture — it gives the associated sites a shared design language, so a hub reads as one intranet rather than a shared menu over twenty unrelated pages.
- Reusable page layouts department owners apply without a developer
- Full theming — fonts, spacing, component treatment — beyond colour and logo
- Roll-ups presented as designed cards and searchable tables
- Site templates so a new associated site starts consistent
Used on 350,000+ SharePoint sites by 12M+ people · Microsoft Solutions Partner · No credit card required
Common questions about hub sites
What is a SharePoint hub site?
A hub site is an ordinary SharePoint site that an administrator has registered as a hub, so other sites can associate with it. Associated sites inherit the hub’s shared navigation and theme, roll their content up into the hub’s web parts, and join the hub’s search scope. Hubs are how modern SharePoint imposes structure on a deliberately flat estate: instead of nesting sites inside each other as subsites, you connect independent sites side by side and each keeps its own permissions, storage and ownership.
How many hub sites can you have in SharePoint?
A maximum of 2,000 hub sites can be created per tenant, a figure Microsoft states in its own PowerShell documentation for the Register-SPOHubSite cmdlet. That ceiling is far higher than any organisation needs in practice. A 5,000-person organisation typically works well with somewhere between eight and fifteen hubs mapped to business units, functions or geographies. Creating a hub per team is the most common architectural mistake and produces navigation nobody can follow.
How many sites can be associated with one hub?
Microsoft’s own documentation describes the number of site collections associated with a hub as unlimited. Several third-party guides state a cap of 1,000 or 2,000 associated sites per hub, but those figures do not appear in current Microsoft documentation, so treat them as unverified. The practical constraint is different anyway: navigation is capped at 500 child links per level, and the Sites web part returns at most 99 sites when set to all sites in the hub.
What does associating a site with a hub actually inherit?
Four things: the hub’s shared navigation bar, the hub’s theme, inclusion in the hub’s search scope, and content roll-up into hub web parts where the source is set to all sites in the hub. That is the complete list. Association does not change the site’s permissions, does not add the site to the hub navigation automatically, and does not inherit retention labels, sensitivity classifications or sharing restrictions. Hub owners decide which sites appear in the navigation.
Can a site belong to more than one hub?
No. A site can be associated with only one hub at a time, which is the single biggest constraint on hub architecture. A site serving two business units has to pick one, and the other relationship has to be expressed through navigation links or a search-driven roll-up instead. A site that is already associated with a hub also cannot be converted into a hub itself, so plan which sites will become hubs before you start associating.
Can you nest hub sites?
One level of nesting is supported: a parent hub with child hubs, each of which has its own associated sites. Deeper chains can be configured but produce unsupported behaviour, and roll-up web parts often fail to aggregate content from sites further down. One important limit applies even to supported nesting: hub-to-hub association extends the search scope, but web part roll-ups set to all sites in the hub stay within their own hub and do not cross the relationship.
How long do hub site changes take to appear?
Microsoft’s documentation notes that hub registration changes can take two to four hours to appear. Hub permission synchronisation is similarly slow, propagating over a period of up to four hours. This matters during a rollout: if navigation or theming has not appeared on an associated site, the usual answer is to wait rather than to reconfigure. Reconfiguring mid-propagation is a common way to create a confusing half-applied state.
What is the difference between a hub site and a subsite?
A subsite lives inside another site in a parent-child hierarchy and inherits its permissions, so moving or resecuring it later is difficult. A hub connects independent sites side by side: each associated site remains its own site collection with its own permissions, storage quota and administration, and can be disassociated at any time. Hubs are the modern replacement for subsite hierarchies, which is why Microsoft’s guidance is to keep estates flat and use hubs for structure.
Sources
- Microsoft Learn — Register-SPOHubSite
- Microsoft Learn — Planning your SharePoint hub sites
- Microsoft Learn — Introduction to SharePoint information architecture