Overview
A missing menu or button is not always a Role-permission problem. Some features depend on organization access, some appear only after setup and others are hidden by app-area rules.
Start with the exact feature and surface: Backend, Mobile app or RideOps. A feature available on one surface does not imply that the same menu exists on the others.
At a glance |
|
Who can do this | Super Users or Organization › Administrate for configuration; Mobaro manages organization feature access. |
Where | Configuration, the affected Backend page or Mobile app tile |
Works on | Backend (web) |
Availability | Contact your CSM for organization feature availability. |
💡 Why this matters: Identifying the missing layer helps you change the setting that matters instead of repeatedly granting broader permissions.
Identify what is missing
Symptom | First check |
Whole feature absent or disabled | Organization feature availability and the supported surface. |
Page opens, but no records appear | Location or User scope and list filters. |
Records visible, action missing | Permission for that specific action. |
Mobile tile missing | App-area rules and whether relevant work or content exists. |
Works in another organization | Configuration and feature access in the active organization. |
Capture the menu or action name and the organization you have open. Compare with the current Help Center guide for that feature, including its Availability and Who can do this entries.
Check permissions and setup
1. Check the specific action
Viewing a feature and creating, modifying, approving or deleting its records can require different permissions. Inspect the relevant Role rather than treating access as one on/off switch. Use the Role permissions reference.
2. Check required configuration
Some navigation depends on configured data. For example, Notes needs an active Note Type as well as the relevant Backend access. In the app, Certification Center depends on relevant Processes or Competencies and can also be hidden by an app-area rule.
3. Check mobile area rules
Review Configuration › App Settings and the rules that apply to the User’s groups. These control app-area visibility; they do not grant the underlying work permissions. Follow App Area Availability Rules for the rule behavior.
Check organization feature access
Optional and early-access functionality must be enabled for the organization. A customer Super User role does not provide the Mobaro-only administration controls that change those entitlements.
Inventory requires organization feature access, and its permission controls, Movements and minimum-stock controls may be enabled separately. Check the specific missing control before changing Roles. Follow Inventory availability and contact your CSM or Mobaro Support about access. Use the integrations overview for integration-specific setup.
⚠️ Heads-up: Seeing a feature in another customer’s screenshot or another organization does not establish that it is enabled in yours. Give Support the active organization and exact feature name.
Verify the affected surface
Movements is missing or empty. For a missing Inventory › Movements tab, ask whether Movements is enabled. Where Inventory permissions apply, reports need Stock › View. For an empty report, check the period, filters and membership of the Locations targeted by the Warehouses. Permission to use materials on an Assignment does not by itself grant report access. See Review and export Inventory movements.
Low Stock is missing or shows no shortages. Check whether minimum-stock controls are enabled. For an empty filtered list, check the material’s Minimum stock (all warehouses) and each Warehouse’s Min stock; they are independent. Editing the material minimum needs Materials › Modify, while the Warehouse stock minimum needs Stock › Modify and the applicable Location access. See Set minimum stock and find shortages.
Currencies is missing. Open Organization Configuration › Currencies with Super User access or Organization › Administrate, and confirm Inventory is enabled for the organization. Inventory Stock permissions alone do not grant currency configuration access. See Configure currencies and exchange rates.
After the appropriate configuration change, reopen the affected page or allow the app to receive updated data. If the feature remains missing, record the app version and whether it affects every User or only a particular group. Protect unsent work before any app recovery action.
Protect unsent work before any app recovery action. For a missing record rather than a missing feature, switch to its access or filtering guide instead of requesting an entitlement change.
Best practices
Identify the missing page, action or record before changing access.
Keep organization feature requests separate from User Role changes.
Compare the same organization and surface when reproducing a problem.
Frequently asked questions
Can we get an overview of the features enabled for our organization?
Ask your CSM or Support to review the organization’s enabled features with you. Name the organization and any features you are evaluating; another organization’s setup may differ.
Where is the Timesheets area?
Open Timesheets in the Backend navigation. Reviewing other Users’ entries needs Timesheets › Administrate; the app’s Timesheet views are attached to individual work. See Timesheet reporting.
Can a Super User enable Inventory for our organization?
Inventory feature access is managed by Mobaro. Contact your CSM or Support and follow the Inventory overview for its availability and setup.