Navigation badges and menu visibility
Navigation in MobilityManager is driven by two things: which menu items your role and license allow you to see, and the live count badges that highlight items needing attention. This article explains how navigation is configured and what the badge counts mean.
Required permission
Navigation badges are available to any authenticated user; the counts are scoped to your current tenant. The individual menu destinations, however, appear only when you hold the permission that destination requires.
How the menu is composed
There is no free-form menu editor. Instead, each navigation destination is gated by a combination of:
- Role and permission — routes are guarded by the same
[RequirePermission]checks as their pages, so an item is hidden when your role does not grant the permission. - Module entitlement — module-specific areas (such as Belege, damage management, or maintenance planning) appear only when your license enables that module.
This means the menu a SystemAdmin sees differs from what a FleetManager or Driver sees, and two tenants with different licenses see different modules.
Note: To change what appears in someone's navigation, adjust their role's permissions or the tenant's licensed modules — not a menu list. The menu reflects those decisions automatically.
Navigation badges
Badges are small counts shown next to menu items so administrators can see pending work at a glance. The platform returns a set of counts keyed by destination:
| Destination | Counts |
|---|---|
| Pending requests | Booking requests awaiting manager assignment |
| Pending approvals | Bookings in the pending state |
| Belege review | Beleg receipts currently in review |
Each count is computed live from your tenant's data, so a badge reflects the current backlog for that queue. When there is nothing pending, the count is zero and the badge is hidden.
Tip: Use the badges as a daily worklist. A rising "Belege review" or "Pending approvals" count is a signal that items are waiting on a reviewer or approver.
When badges are empty
If your session has no active tenant context, the badge endpoint returns an empty set rather than an error, and no badges are shown. Once a tenant is selected, counts populate on the next refresh.
Warning: Badge counts are a convenience indicator, not an authorization control. Seeing a count does not grant access to the underlying queue — opening it still requires the relevant permission.
Related
- System configuration overview and access
- Belege configuration overview and publishing a version
- Default language settings (DE and EN)
