Troubleshoot missing module menus
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Check role capabilities and schema rather than editing navigation files.
Where to goAdmin Area → Setup → Staff → Roles
What this guide helps you do
Check role capabilities and schema rather than editing navigation files. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.
Follow these steps
- Check module active and schema ready.
- Check View permission.
- Check specialised Dispatch, Finance, Compliance or Integrations permissions.
- Sign out/in and retest.
Fields and options
This action uses the values already stored on the selected source record. Review that record before continuing.
Rules and limits
- Menu registration deliberately hides specialist workspaces without their capability.
Check it worked
- The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.
Security, audit and operational checks
- Use the exact record and least-privilege role before changing any state.
- Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
- Use protected document and image routes rather than exposing server filesystem paths.
- Keep customer, driver, provider, financial and credential data within the authorised workflow.
- For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.
Related guides
Was this guide useful?Your response is stored only in this browser.