--- title: How to customize menus and personas canonical: "https://cloudmonitor.ai/docs/how-to/how-to-manage-personas-and-navigation/" description: "Rename and arrange the shared menu, then choose which pages and links each persona sees." --- Menu customization uses one editor for the whole saved menu. Choose **Organization menu** to set the shared names, sections, order and organization-wide availability. Choose a persona in the same menu navigator to keep that person's menu focused on their job by selecting from the available pages. Neither scope grants access to a feature, route, action, or cost group. :::note[Admins only] Only the current **Organization Owner** can open or save this screen. Other admins can still manage the settings their role permits, but they cannot change shared personas. ::: ## Where Settings ▸ **Menu customization**. On a wide screen, use the menu navigator on the left to choose **Organization menu** or a persona. On a smaller screen, use **Edit menu for** above the editor instead. While editing the organization menu, use **Preview as** to see the draft through any active persona. While editing a persona, the preview follows that persona automatically. The preview updates as you edit; on a smaller screen, select **Preview menu** to open it in a side sheet. ## Shape the menu for everyone Select **Organization menu** in the left navigator, or from **Edit menu for** on a smaller screen, to edit the shared starting point for every persona. The editor heading remains **Menu structure**. - Rename **Overview**, any built-in section, or any page. A page rename appears in both the menu and that page's main heading. Its route and access rules do not change. - Move sections up or down, move pages within a section, or choose a different section for a page. - Switch a section or page off to hide it from every persona menu. **Overview** and **Ask Finn** stay available because they are product navigation invariants. - Select **Add section** to create another top-level section. Move pages or persona links into it as needed. A custom section can be deleted only after it is empty. - Select **Reset structure** to restore the built-in section and page names, order and visibility. Your custom sections and personas are kept. Microsoft 365 and AI Spend child pages are editable rows too. Their entitlement and persona checks remain anchored to their parent page, even if you rename or move them. If a persona's saved landing page is globally hidden or currently unavailable, that persona opens on **Overview** instead. Re-showing the page restores the saved landing choice. ## Tailor each persona Select a persona from the same left navigator, or from **Edit menu for** on a smaller screen. The organization menu's names, order and placement flow into every persona; the persona scope controls which available pages that persona can discover. A globally unavailable page remains visible in the editor as disabled and marked **Hidden in organization menu**. Its saved persona selection stays intact and takes effect again if the page is made available in the organization menu. ## Start with the SYSTEM personas Every organization starts with four SYSTEM personas. You can change their name, description, landing page and menu. You can also archive one, provided at least one active persona remains. SYSTEM personas automatically inherit a new native report page when CloudMonitor ships one. Removing a page records an explicit exclusion, so it stays removed when other pages are added later. ## Create a customer persona Select **New persona**. It starts with every current native report page selected. A customer persona does not automatically inherit report pages shipped later. For the selected persona: 1. Enter its name and optional description. 2. Choose **Overview** or one included report as its **Landing page**. 3. Select the native report pages it should show. **Overview** stays pinned and cannot be removed. 4. Review the live **Menu preview**, which follows the selected persona automatically. Settings pages remain product-owned and are not configurable persona items. ## Add your own links Under **Your own links**, add destinations outside CloudMonitor: your own reports, a support desk, a runbook, or an internal wiki. 1. Select **Add link**. 2. Enter a **Link name**. This is shown exactly as you type it. 3. Enter the **Web address**. It must be a full address starting with `https://`, and it must not contain sign-in details. A query string or a fragment is fine, so you can link a filtered report. 4. Choose an icon and the **Menu section** the link belongs to. 5. Use the arrow buttons to order links within a section. A link appears at the end of its chosen section, after that section's report pages. You can move native pages separately under **Organization menu**. Each link is marked as leaving CloudMonitor, and hovering it shows the destination host so people can see where it goes before selecting it. Selecting one opens it in a new browser tab and leaves CloudMonitor open. :::note[Links are not access] A link is not a CloudMonitor page. It cannot be a landing page, it never appears under Settings, and it grants nothing. The destination does its own sign-in: CloudMonitor never sends your credentials, filters, or session to it, and never loads anything from it until someone selects the link. ::: If a saved address later fails these rules, CloudMonitor leaves the link out of the menu rather than opening it. ## Save, cancel, default and archive Changes across the organization menu and persona scopes stay in one local draft until you select **Save menu**. **Cancel** restores the last saved structure and persona configuration together. A failed save leaves your draft intact. Persona lifecycle actions join that same draft: - **Set as default** stages the fallback for users with no valid active selection. - **Archive** stages removal from user selection while retaining the persona's configuration. You cannot archive the final active persona. If you archive the default, another active persona becomes the staged default automatically. - Switch from **Active** to **Archived** and select **Restore** to stage its return. - **Duplicate** creates an editable customer-persona copy in the draft. None of these actions affects other users until **Save menu** succeeds. If a change removes a native page from the final active persona that contained it, CloudMonitor names the affected page and asks for confirmation. After confirmation, it disappears from every persona menu. Existing authorized direct links still work. ## What happens for users Each user chooses an active persona under **Profile & preferences**. After the organization menu is saved, the new structure and persona choices apply. If a user's selected persona is archived, CloudMonitor falls back to the organization default. Feature switches, roles, cost-group scope, and route checks are always applied after persona membership. A persona can hide a permitted page from the menu; it cannot reveal a page or data the user is not allowed to access. ## Current limitation A link belongs to the persona you add it to. To show the same destination in more than one persona, add it to each one.