SharePoint Hub Sites Explained: Architecture, Planning, and Governance

Direct answer: A SharePoint hub site connects related team and communication sites with shared navigation, search scope, and look-and-feel — without merging their permissions or content. Use one hub per audience or function, associate 10-50 related sites, and govern who can create hubs.

For broader SharePoint learning, see the SharePoint tutorials hub. If permissions are new, start with SharePoint Permissions Explained and the beginner tutorial.

How hub sites work

A hub is a SharePoint site (usually a communication site) registered as a hub. Other sites associate with it. Association brings shared top navigation, aggregated search, shared theme, and the ability to roll up news, events, and content. Each associated site keeps its own owners, members, libraries, and permission inheritance.

Think of it as:

Hub site (HR)
  -> Team site: Recruitment
  -> Team site: Onboarding
  -> Communication site: Policies
  -> Team site: Learning

When to use a hub vs a single site

Planning checklist

• Name the audience and purpose in one sentence before registering the hub.
• Limit to 3-7 top navigation links; deeper links live on associated sites.
• Decide search behavior: hub-scoped search helps discovery but needs consistent metadata.
• Assign 1-2 hub owners separate from site owners to control navigation changes.
• Document which sites belong and why; review quarterly.

Permissions and governance

Hub association never grants access. A user who cannot open an associated site still cannot open it via hub navigation — they simply see a link they cannot use or do not see it depending on trimming. Keep permissions at the site/library level as described in permissions, and govern hub creation centrally so departments do not each register competing hubs.

Common mistakes

• Creating a hub per project — use one Projects hub with many associated sites instead.
• Putting 20 links in hub navigation — users stop using it after 7.
• Expecting hub search to fix missing metadata — pair hubs with the patterns in metadata explained and folders vs metadata.
• Migrating files before designing hubs — design IA first, then migrate as covered in migration guide.

Production considerations

Record hub ID, associated sites, navigation owners, and review dates in your IA register. Test navigation as a visitor, not just an owner, and validate search scope after associating sites. For growing libraries inside hubbed sites, apply the document-dump blueprint.

FAQ

Can a site join multiple hubs? No — one hub per site. If a site serves two audiences, link to it from the second hub instead of duplicating it.

Should the hub store files? Keep the hub lean (navigation, news, links). Store working files in associated team sites.

Continue with document libraries, lists vs Microsoft Lists, and the architecture library.