Customize Your Site Menu
The navigation bar at the top of your community website is fully under your control. This article covers the single task of reshaping it in Manage Menu: adding and removing items, reordering and nesting them, and choosing which roles see each one. For labeling and structure best practices, see the Manage Menu article.
Before You Begin
Menu editing uses the same permission as website pages — if your role can manage pages, you can manage the menu. Open the Community Admin Center and use the Manage Menu card; if the card is missing, ask a community administrator to review your role's pages permissions.
What You're Looking At
The Manage Menu interface displays your current navigation structure. Each entry corresponds to a page, the blog, the calendar, or an external link, and items can be nested to create drop-down submenus.
Adding and Removing Items
- Add: Click Add Menu Item. Select one of your existing pages or paste an external URL, then choose the display label residents will see in the navigation bar.
- Remove: Click the item's delete icon. Removing a menu item does not delete the page it points to — the page stays reachable at its URL; it just no longer appears in the navigation.
New pages are not added to the menu automatically, so revisit Manage Menu whenever you publish one — see Create a Custom Page.
Reordering and Nesting
Drag and drop items to adjust their position. The left–right indentation controls nesting: indent an item under another to make it a child in a drop-down submenu. For example, a "Committees" parent item could hold child items for "Architectural Review Committee" and "Social Committee".
Order matters — put frequently used destinations like Calendar and News near the beginning, and keep the number of top-level items small, grouping related pages into submenus.
Per-Item Role Visibility
For each menu item, you can specify which roles can view it. Public pages should be visible to all visitors, while internal resources might only appear for signed-in residents or administrators. Role-based visibility keeps each audience's navigation relevant — and keeps members-only links out of the public menu.
Remember that menu visibility controls the navigation entry, not the destination itself; manage the content's own visibility in its module (for example, a page's public/hidden switch).
Save and Verify
Save your changes, then view the site as a resident would to confirm the menu reads well and behaves as expected on both desktop and mobile. If navigation feels cumbersome, reorder or rename items and check again.
Tips
- Mirror your site structure: Arrange items to reflect how important and how frequently used each destination is.
- Short labels win: "Documents" beats "Document Library Repository". Consistent, plain labels teach residents where to look.
- Review after every content change: New pages, retired pages and renamed pages all deserve a quick menu pass.