Skip to main content

How to Organize Navigation Across SharePoint Communication and Team Sites

Summary​

Navigation is the infrastructure that helps users locate information and resources across your SharePoint environment. SharePoint provides multiple navigation mechanisms—global navigation through hub sites and Viva Connections, hub-level navigation, and site-level navigation—each serving different purposes. Effective navigation planning requires understanding the differences between communication sites and team sites, the role of mega menus, audience targeting, and governance principles that scale across your organization.

SharePoint navigation operates at three primary levels: global navigation, hub navigation, and site navigation. Each level serves a distinct purpose in your information architecture.

Global navigation connects users across your entire SharePoint environment and may extend to external resources or third-party applications. Global navigation typically appears consistently across all sites accessed through Viva Connections or organizational hub sites.

Hub navigation operates at the hub site level and aggregates content and navigation from associated sites. Hub navigation appears when users browse within a hub's scope and provides department-specific or function-specific organization.

Site navigation exists within individual communication or team sites and guides navigation within that site's boundary. Site navigation typically emphasizes that specific site's content and internal structure.

Understanding these levels prevents redundancy and confusion. If the same link appears in multiple places, users may question whether they missed content elsewhere. Strategic use of each navigation level ensures information appears in appropriate contexts.

Hub sites serve as organizational anchors that aggregate related sites and provide organization-wide navigation infrastructure. A hub site connects to associated sites, creating a logical grouping that may reflect departments, functions, or business units.

Hub site navigation appears in the hub switcher and provides users with awareness of sibling sites within that hub. When a user accesses a site associated with a hub, the hub switcher indicates their current location and provides quick access to other hub-associated sites.

In large organizations, multiple hub sites may exist, each representing distinct business functions. For example, an organization might maintain separate hub sites for Finance, Human Resources, Operations, and Product Development. Users accessing the Finance hub's navigation see links to related Finance sites; users accessing the HR hub see HR-related sites.

Configure hub site navigation to reflect organizational structure and user workflow. Navigation should answer the question: "From this hub, where do users typically need to go next?" Place frequently-accessed resources and critical destinations in the primary hub navigation positions.

Viva Connections as Global Navigation​

Viva Connections provides a mobile-first, personalized entry point to organizational information and tools. The Viva Connections dashboard can be configured as your global navigation mechanism, presenting organization-wide resources regardless of which site a user is currently viewing.

Viva Connections navigation typically displays as cards or tiles representing:

  • News feeds from across the organization
  • Quick access to tools and forms
  • Links to major hub sites or key destinations
  • Personalized content relevant to specific user roles

Viva Connections navigation complements hub site navigation. While hub sites aggregate related content within a domain (such as a department), Viva Connections provides cross-organizational access. A user in the Engineering department can access both Engineering hub resources through hub navigation and organization-wide resources through Viva Connections.

Configure Viva Connections to display audience-targeted content so that different user groups see relevant destinations. Sales users might see pipeline tools and customer resources; IT users might see service desk systems and documentation portals.

Communication Site Navigation​

Communication sites present information to broad audiences and typically emphasize content discovery over team collaboration. Communication sites typically organize navigation around content categories, such as Product Information, Customer Resources, and Knowledge Base categories.

Communication site navigation typically appears in two formats: top navigation and left sidebar navigation.

Top navigation displays horizontally across the top of the site below the site title. Top navigation works well for 5-8 primary categories. Beyond 8 items, top navigation becomes crowded and difficult to scan. Top navigation is highly visible and sets user expectations for site structure, making it appropriate for main content categories.

Left sidebar navigation displays vertically along the left side of the page. Left navigation accommodates more items than top navigation and enables nested subcategories. Left navigation works well for sites with complex hierarchies or many secondary sections. However, left navigation consumes horizontal space, which may reduce content area width on smaller screens.

Many communication sites employ both top and left navigation. Top navigation displays primary categories; left navigation displays subcategories and related links within each category. This two-level approach balances discoverability with scalability.

Mega Menus in Communication Sites​

Mega menus expand navigation categories to display subcategories, featured content, and quick links in a structured dropdown layout. Mega menus work particularly well in communication sites where users need to navigate complex information structures.

A mega menu typically appears when users hover over or click a top navigation item. The mega menu displays 2-4 columns of links organized by subcategory, potentially including featured content cards or graphical elements.

Mega menus should remain organized and scannable. Limit each mega menu to 15-25 links total. If a category requires more navigation options, this often indicates the site structure itself needs revision.

Configure mega menus to highlight frequently-accessed content within each category. A customer support mega menu might emphasize quick links to troubleshooting guides, support ticket submission, and knowledge base search, alongside standard subcategory navigation.

Team Site Navigation​

Team sites prioritize team collaboration and shared work, typically serving smaller groups with shared projects or responsibilities. Team site navigation emphasizes the team's working structure rather than broad content discovery.

Team site navigation typically includes:

  • Channels (in Teams-connected sites) representing working areas or projects
  • Shared document libraries and folders
  • Apps and tools for team collaboration
  • Links to related team sites or department resources

Team site navigation in modern SharePoint appears more minimally than communication site navigation. Rather than extensive top or left menu systems, team site navigation emphasizes quick access to shared resources the team uses daily.

When team sites require navigation beyond immediate team resources—such as links to department hubs or organizational policies—this navigation typically appears in the Quick Links web part or in hub-level navigation rather than site-level menu structures.

Effective navigation requires planning before implementation. Start by documenting your organizational structure and user workflows. Which users need access to which resources? What paths do users typically follow to access information?

Map these workflows to navigation structures. If most employees need to access HR policies, payroll, and benefits, these should appear in global navigation or prominent positions in relevant hub sites. If only Finance users need to access budget tracking systems, these can be positioned deeper in Finance hub navigation without appearing in global navigation.

Consider the "three-click rule," though this principle should not be followed rigidly. The three-click rule suggests users should reach any important resource within three clicks. However, some resources appropriately require more clicks if they serve specialized functions. Instead of strictly enforcing three clicks, ensure critical resources are easily discoverable and specialized resources are logical to locate for those who need them.

Create a navigation audit documenting all navigation elements across communication sites, team sites, hubs, and Viva Connections. Identify redundant links, broken links, and navigation items serving obsolete purposes. Remove items that no longer serve active functions.

Audience-Targeted Navigation​

SharePoint supports audience-targeted navigation links that display only to specified security groups or user roles. Audience targeting prevents cluttering navigation with items irrelevant to specific users.

Configure audience targeting for:

  • Department-specific hub links visible only to department members
  • Executive reports or strategic plans visible only to leadership
  • Temporary content such as open positions or event registrations visible only during relevant periods
  • Confidential resources requiring specific authorization

Document audience-targeted navigation clearly. Users should generally understand why certain navigation items do or do not appear. If your IT help desk is targeted only to IT staff, most users won't question its absence, but if navigation mysteriously changes based on group membership without explanation, users may feel confused or excluded.

Avoid excessive targeting that makes navigation inconsistent and unpredictable. A homepage with 15 different targeted sections visible to different user groups becomes unmaintainable and creates poor user experience. Aim for 2-3 primary audience segments with navigation customization, supplemented by personalization through Viva Connections.

Governance and Navigation Maintenance​

Navigation changes impact user experience organization-wide. Establish governance policies for navigation changes.

Centralized approval: Navigation changes affecting global navigation or hub navigation should require approval from a navigation governance team. This prevents individual site owners from making changes that conflict with organizational navigation strategy.

Change documentation: When navigation changes, document what changed, why, and when it takes effect. Communicate changes to users where appropriate so they're not surprised by disappearing or reorganized navigation items.

Regular audits: Schedule quarterly or semi-annual reviews of navigation across all sites. Remove outdated links, update misdirected URLs, and consolidate redundant navigation items.

Naming standards: Establish conventions for navigation item labels so users encounter consistent terminology. If some navigation items are called "Resources" while others are called "Tools," users may not realize they serve similar purposes. Standardized naming improves predictability and discoverability.

Common Mistakes and Pitfalls​

Inconsistent navigation across sites: When each site implements navigation differently, users must learn new patterns for each site, increasing friction. Establish navigation patterns that remain consistent across your environment.

Overpopulated navigation: More than 10-15 top-level navigation items overwhelms users with choices. Prioritize ruthlessly and move secondary items to secondary navigation levels.

Broken links in navigation: Links pointing to moved, deleted, or restricted content frustrate users. Regularly audit navigation links and fix broken items immediately.

Outdated navigation targeting former organizational structures: When departments reorganize, navigation often remains rooted in old structure. Update navigation to reflect current organizational reality.

Hub navigation disconnected from site purpose: A hub site's navigation should reflect the common purposes shared by its associated sites. Navigation that seems random or disconnected from site purpose reduces confidence in the navigation structure.

Confusion between hub switcher and site navigation: Users may not understand the difference between hub-level navigation and site-specific navigation, leading to confusion about where specific links appear.

Mega menus that are too complex: Mega menus attempting to show all possible navigation options become unusable. Focus mega menus on the most critical paths through your information.

Communication sites emphasize content discoverability for broad audiences, so they typically implement extensive navigation with top menus, left sidebars, and mega menus. Communication site navigation should help external audiences or new employees understand the site's content organization.

Team sites emphasize collaboration for defined groups, so they typically implement minimal navigation structures. Team site users already know each other and their shared purposes, reducing the need for extensive navigation to understand site organization.

When connecting team sites to hubs, ensure hub-level navigation is visible while maintaining the team site's focus on collaborative content. Hub navigation should not overwhelm team site navigation.

Frequently Asked Questions​

Q: How many top-level navigation items should we include? A: Limit top-level navigation to 5-10 items. Beyond 10 items, users begin skimming rather than reading, and discoverability diminishes.

Q: Should team sites have navigation similar to communication sites? A: No. Team sites should prioritize collaboration tools and team-specific resources. Extensive navigation appropriate for communication sites often feels like clutter in team sites.

Q: How do we update navigation consistently across multiple sites? A: Use hub-level navigation for items that should appear across multiple associated sites. This centralizes updates and maintains consistency without requiring changes to each individual site.

Q: Can we use mega menus on mobile devices? A: Mega menus work poorly on mobile devices where hover interaction is unavailable. Consider alternative mobile navigation patterns for mobile-heavy user bases.

Q: Should external links appear in navigation? A: Limit external links to frequently-accessed third-party tools. Excessive external linking trains users to abandon your intranet and undermines the intranet as a central hub.

Q: How do we handle navigation when organization structure changes? A: Update navigation to reflect new structure. Archive or redirect navigation items for discontinued departments. Communicate changes to affected user groups.