SharePoint Hub Site Architecture: Connecting Department Sites the Right Way

SharePoint hub site architecture: a flat structure instead of subsites, the number of hubs, navigation layers, hub registration with PowerShell and steps for moving sites during a reorganization.
Technical summary
Technology
SharePoint Online, Hub Sites, SharePoint Online Management Shell, PnP PowerShell
Topic
A hub-based intranet site topology
Level
Intermediate–advanced
Prerequisites
  • SharePoint administrator role
  • SharePoint Online Management Shell installed
  • Knowledge of modern communication and team sites
In this article8 sections

Once the number of department sites passes twenty, the problem in a SharePoint intranet is no longer the content; sites become disconnected from each other, menus become inconsistent and users can’t find what they’re looking for. A classic subsite tree hides this mess in the initial setup. The first time the org chart changes, it turns into a structure that can’t be moved. Below, we describe from a field perspective a topology that can grow with a flat site structure and hub association: the decision on the number of hubs, navigation layers, PowerShell commands and reorganization steps. Before setting up the intranet, define the limits on guest and external partner access within the framework of SharePoint and OneDrive external sharing security.

A flat structure instead of subsites

In the old method, nested subsites such as /sites/intranet/hr/payroll were opened under a single site collection. Permissions, navigation and theme are inherited from the parent site; in the first week it looks practical. The problem is that the parent site is embedded in both the URL and the permission chain. When the payroll team moves from HR to Finance, moving the subsite means rebuilding URLs, permissions, library links and flows. This is the picture we see most often in the field. Nobody dares to move it.

In modern SharePoint, the structure is flat: each department, team or project is its own site collection (/sites/hr, /sites/payroll, /sites/finance). The logical relationship between sites is established not by the URL but by hub association, and it changes with a single setting. What a flat structure means in practice:

  • Independent lifecycle: One site is archived, deleted or placed under a retention policy; the others aren’t affected.
  • Separate permission boundary: Each site has its own owner, member and visitor groups; there’s no inheritance chain.
  • Site-level settings: External sharing, storage quota and sensitivity labels are managed per site.
  • Easy reorganization: Associating a site with another hub takes minutes, and the URL doesn’t change.

When moving away from an existing subsite structure, subsites are usually migrated to new site collections with a migration tool. This takes as much effort as rebuilding; the hub design should be finished on paper before the migration. The SharePoint intranet checklist is a good start for general planning items; here we focus only on the site topology.

What a hub does and doesn’t do

A hub is created by registering an existing communication or team site as a “hub”. Associated sites aren’t moved under the hub; they’re only connected to it. If you don’t set expectations right from the start, the first complaints are about permissions:

Topic Does the hub provide it? Explanation
Shared navigation Yes The hub navigation bar appears above all associated sites.
Theme Yes Associated sites take on the hub theme.
Search scope Yes A search from within the hub covers the associated sites.
Content aggregation Yes The News, Sites and Highlighted content web parts work within the hub’s scope.
Applying a site template Optional A site template defined for the hub is applied on association.
Permission inheritance No Association doesn’t change permissions; each site keeps its own permissions.
Hierarchical URL No Site addresses are independent of the hub.

The most common wrong assumption is that a site associated with a hub is automatically opened to the hub’s members. It isn’t. Aggregated news and documents are filtered according to the user’s permissions; a user without permission never sees that site’s news in the news web part on the hub home page. Hub owners can use the option to sync hub visitors with associated sites (hub permissions sync). This is read access only, and the owner of an associated site can turn it off for their site. The details of the permissions side are in the SharePoint permission model guide.

A site can be associated with only one hub at a time. Hubs, however, can be associated with each other (hub-to-hub); this relationship doesn’t merge navigation and themes, it only widens the search and content aggregation scope.

How many hubs, which grouping

User behavior determines the number of hubs more than the technical limit does. The per-tenant hub limit is rarely a bottleneck in practice (verify the current value on Microsoft’s SharePoint limits page). The real cost is this: every hub brings separate navigation, a separate theme and a separate ownership burden. Before deciding on the grouping, answer four questions:

  1. How do users look for content? If an employee thinks “something to do with HR”, functional grouping is natural; if they think “the Gebze plant”, location grouping is.
  2. Who will manage the hub? The navigation of a hub without an owner goes stale within a few months. Each hub should have a named owner.
  3. Who is the news feed for? The hub home page aggregates the news of associated sites; sites that will be read together should be in the same hub.
  4. How permanent is the structure? A separate “Projects” hub for frequently changing projects lives longer than hubs mapped one to one to the org chart.

A typical starting point for a mid-sized industrial company might be: a corporate main site (home site), a “Corporate Services” hub (HR, Finance, Procurement, IT), an “Operations” hub (Production, Quality, Logistics, OHS) and a “Projects” hub. Team sites connected to Teams can be associated with the relevant hub. Associating a team site with confidential content with a hub doesn’t open up the content; the site isn’t added to the hub navigation automatically either, and the hub owner manages the links by hand. The rule is simple: only sites open to a broad audience go into the hub navigation. Otherwise users land on an “access denied” page every day and lose trust in the intranet.

Hub navigation and global navigation

In modern corporate intranets and web portals, three navigation layers work together. If their roles get mixed up, the menu bloats:

Layer Where it appears Purpose
Global navigation SharePoint app bar Access to the main sections across the whole intranet
Hub navigation Above the hub and associated sites Sites in the hub family and shared resources
Site navigation The site’s own menu The site’s pages and libraries

Global navigation is turned on in the home site’s settings after a home site has been defined in the tenant; the home site and the Viva Connections side are covered in the Viva Connections setup guide. The hub owner edits the hub navigation from the hub site’s top menu. A practical rule: global navigation holds only the hubs and a few core organization-wide resources; hub navigation holds that family’s sites and frequently used tools; site navigation holds only that site’s content. If the same link is repeated in all three layers, the design is wrong. Maintenance triples.

By enabling audience targeting on navigation items, some links can be shown only to specific Microsoft 365 or security groups. This isn’t a security control. It hides the link but doesn’t touch the permissions of the target content.

Hub registration and association commands

Only a SharePoint administrator (or higher) can register a hub. It can also be done from the admin center, but we prefer PowerShell for repeatability and record-keeping. The example below works with SharePoint Online Management Shell; the tenant name and site addresses are examples:

Connect-SPOService -Url https://contoso-admin.sharepoint.com

# Register an existing communication site as a hub; limit association rights to a group
Register-SPOHubSite -Site https://contoso.sharepoint.com/sites/corporate-services `
  -Principals "[email protected]"

# Update the hub display name and description
Set-SPOHubSite -Identity https://contoso.sharepoint.com/sites/corporate-services `
  -Title "Corporate Services" -Description "HR, Finance, Procurement and IT sites"

# Associate the department site with the hub
Add-SPOHubSiteAssociation -Site https://contoso.sharepoint.com/sites/hr `
  -HubSite https://contoso.sharepoint.com/sites/corporate-services

# List registered hubs
Get-SPOHubSite

-Principals limits the right to associate sites with this hub to the specified users or groups. If it isn’t given, every site owner associates their own site with the hub. A few months later, you see sites nobody recognizes in the hub navigation and test pages in the news feed. On corporate hubs, limit the right to a group. To add rights later, Grant-SPOHubSiteRights is used, and to remove them, Revoke-SPOHubSiteRights.

The hub site settings also have a “require approval for association” option; when it’s turned on, the request goes to the hub owner through a Power Automate approval flow. For flow design, see the Power Automate approval processes guide.

For teams using PnP PowerShell, the equivalent commands are Register-PnPHubSite and Add-PnPHubSiteAssociation. For bulk association, keep the site list in a CSV and run it in a loop; the change becomes both repeatable and auditable:

# hub-mapping.csv: SiteUrl,HubUrl
Import-Csv .\hub-mapping.csv | ForEach-Object {
    Add-SPOHubSiteAssociation -Site $_.SiteUrl -HubSite $_.HubUrl
    Write-Output "$($_.SiteUrl) -> $($_.HubUrl)"
}

Restructuring after an organizational change

This is where the real value of the flat structure shows. Example: Procurement is split off from “Corporate Services” and attached to the newly formed “Supply Chain” unit. In the subsite model, this is a migration project. In the hub model, it’s a maintenance window:

  1. Impact analysis: List the hub navigation links, News web parts and Power Automate flows that point to the Procurement site. Flows are tied to the site URL; since the URL doesn’t change, they’re usually unaffected.
  2. Prepare the new hub: Create the “Supply Chain” communication site, register it as a hub and define its theme and navigation.
  3. Change the association: First detach the site from the old hub with Remove-SPOHubSiteAssociation -Site <url>, then associate it with the new hub with Add-SPOHubSiteAssociation. Run both commands in the same window so the site isn’t left without a hub.
  4. Clean up navigation: Remove the Procurement link from the old hub navigation and add it to the new hub.
  5. Verify the appearance: The site takes on the new hub’s theme and navigation. If a site template is defined for the new hub, it’s applied; lists and pages added by the old template stay on the site and aren’t deleted automatically.

If the hub itself is to be removed, the order matters: first move the associated sites to their new hubs, then delete the registration with Unregister-SPOHubSite. In the reverse order, the sites are left without shared navigation for a while. Deleting the registration doesn’t delete the site; it only loses the hub feature. If the site name also needs to change, the site address change feature in the admin center creates a redirect for the old address; but separately scan for hard-coded addresses in apps, sync clients and scripts. A redirect doesn’t save everything.

Hub architecture checklist

  • New sites are created as separate site collections, not as subsites.
  • Each hub has a named owner and someone responsible for maintaining its navigation.
  • The hub association right has been limited with -Principals, or the approval flow is turned on.
  • There’s no link duplication between global, hub and site navigation.
  • Sites with confidential content aren’t listed in the hub navigation.
  • The site–hub mapping is kept in a CSV or similar inventory.
  • The re-association procedure for organizational changes is in writing.

The internal structure of libraries is a sub-layer of this topology; the metadata and content type guide is the natural next read for classification. The official design principles are in Microsoft’s hub site planning documentation. Teams who want to plan the topology together can take a look at our SharePoint intranet and employee portal service.

Frequently asked questions

Can a site be associated with more than one hub?

No. A site can be associated with only one hub at a time. If the site needs to appear in different content feeds, hub-to-hub association or site-based filters in web parts are used.

Does associating a site with a hub change permissions?

No. Association affects navigation, the theme and the search scope; the site’s owner, member and visitor groups stay as they are. Hub visitor sync is an optional, separate setting.

Can existing subsites be converted into hubs?

Not directly. Hub registration is done at the site collection level; a subsite can’t be registered as a hub. The subsite’s content is moved to a new site collection, and that site is then associated with the hub.

Does deleting the hub registration also delete the site?

No. Unregister-SPOHubSite only removes the hub feature; the site and its content stay in place. Moving the associated sites to their new hubs first avoids leaving the sites without navigation.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Web

We build and maintain corporate websites, WordPress and CMS platforms, intranet and SharePoint portals, document management, and form and approval workflows, and keep them secure and up to date.

Knowledge Center

Other articles