About the Navigation Menu
Navigation Menu controls how partners, customers, and employees move through your Magentrix portal. Each portal can have one or more Apps (top-level containers), and each App contains a hierarchical tree of Menu Items that can include folders, entity links, Active Pages, external links, embedded web pages, and feature-driven items.
All configuration is done from Setup > Create > Navigation Menu, with two tabs: Apps and Menu Items.
Where Configuration Lives
- Apps list:Setup > Create > Navigation Menu > Apps - Create, clone, edit, and delete Apps; set the landing menu item.
- App editor: Opens when you edit an App - shows the App's hierarchical Menu Item tree with drag-and-drop reordering, folder nesting, per-item editing, and per-item sharing.
- Menu Items list:Setup > Create > Navigation Menu > Menu Items - A flat list of all Menu Items for direct editing across Apps.
Menu Item Types
| Type | What It Points To | Created By |
|---|
| Entity | An entity list view (Accounts, Contacts, custom entities, etc.). | Administrator |
| Active Page | An Active Page in your portal. | Administrator |
| Link | An internal portal URL or external website (opens in current or new tab). | Administrator |
| Web | An external page embedded in an iframe within the portal layout (HTTPS only). | Administrator |
| Folder | A container that groups other Menu Items under a single expandable item. Can be nested. | Administrator |
| Feature | A platform-managed item generated automatically by a feature (for example, Training, Articles). Cannot be edited or deleted. | System |
How Visibility Is Determined
A Menu Item appears for a given user only when ALL of the following are true:
- The App containing the item is accessible to the user's security role.
- For Web and Link items: the user's role or one of their groups is in the item's sharing list.
- For Entity items: the user's role has Read permission on the underlying entity.
- For Active Page items: the user's role or group has access through the Active Page's own sharing settings.
- For Feature items: the user's role has access to the underlying module (for example, the Training feature menu only appears when the user has Training access).
If a Folder contains no items the user can see, the folder is hidden automatically.
Use Cases
- One App per audience. Run separate Apps for partners, customers, and internal staff so each group gets a tailored top-level navigation.
- Group related items into a Folder. Add a "Resources" folder containing Menu Items for Articles, Documents, Wikis, Resource Collections, Marketing Assets, and Training instead of keeping them as separate top-level items.
- Tier-aware partner navigation. Add a Link Menu Item for an MDF Request form and share it only with the Gold Partners user group, while keeping a different MDF item shared with Platinum Partners.
- Make a record list the landing page. Set the Partner Dashboard Active Page or an Account list as the App's default landing item so users see it on every visit.
- Quick rollout to a new partner segment. Use Clone App to duplicate an existing App and adjust just the items that need to differ for the new segment.
- Embed a third-party tool. Use a Web Menu Item to embed an external dashboard or training portal directly inside your Magentrix layout.
Apps and the Default (Landing) Menu Item
Each App has a Default Menu Item that determines what users see when they first open the App. If the default is a folder, the folder's first child item is opened. The default can be changed at any time in the App editor.
Sharing Model
Sharing applies to Web and Link Menu Items. Each item can be shared with any combination of:
- Security Roles - All users assigned to the role see the item.
- User Groups - All members of the group see the item, regardless of role.
For Entity, Active Page, and Feature menu items, visibility derives from the underlying object's permissions, not from per-item sharing.
Migration from Pre-v2025.8.0 Apps
If your portal was set up before nested navigation was introduced, existing Apps are upgraded automatically to the new hierarchical model. Top-level items remain top-level. Items that were previously hidden behind an overflow indicator are grouped, as a one-time migration step, under an automatically created folder named More. After the upgrade, this is a regular folder you can rename, reorganize, or delete. Permissions and sharing settings are preserved during the upgrade.
Troubleshooting Tips
- A user does not see an item you expected them to see. Check the App's role access first, then the Menu Item's sharing (for Web/Link), then the underlying entity or Active Page permission. The item is hidden when ANY layer denies access.
- A folder appears empty for some users. The folder is intentionally hidden when it has no visible children for that user's role and group membership. Add an item the user has access to, or move the user into a permitted role/group.
- You cannot delete a Menu Item. Standard (Feature) Menu Items are generated by the platform and cannot be deleted from the admin UI. The delete action is hidden for these items.
- App-level changes are not visible after save. Browser cached an older version of the page. Hard-refresh the browser (Ctrl+Shift+R or Cmd+Shift+R).
For symptom-by-symptom resolutions across the whole module, see Navigation Menu Troubleshooting.
Navigation Menu Checklist >>