Navigation, dashboard and staff permissions

Troubleshoot a missing Enterprise POS menu

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Check module activation, View capability and administrator status without editing unrelated navigation code.

Audience: Administrators, managers, cashiers and reporting staffPermission: One or more Enterprise POS capabilitiesModule v1.0.0 · code-inspected

Jump to steps

Where to goEnterprise POS

What this guide helps you do

Check module activation, View capability and administrator status without editing unrelated navigation code. This section maps every live administrator work area and the exact capability gates registered by the module.

Follow these steps

Go to Enterprise POS and open the workflow that matches “Troubleshoot a missing Enterprise POS menu”. Confirm the page or record context before making a change.
Go to the administrator sidebar.
Expand Enterprise POS.
Verify only the work areas allowed by the current user’s role are present.
Go to the relevant work area and verify the page-level permission check.
Adjust the staff role in the host role editor when access is missing or too broad.

Fields and options

Guide focus: Check module activation, View capability and administrator status without editing unrelated navigation code.
10 registered capabilities
13 administrator work areas
Client Shop menu appears only when the store is enabled
Administrators bypass staff capability restrictions in the standard host manner

Rules and limits

Menu visibility is not the only control; controllers also call access checks.
A staff member without View does not receive the parent menu.
Each child menu is independently filtered by its required capability.
Settings controls API credentials and webhooks, so it requires Manage settings.

Check it worked

The specific outcome described by this guide is visible and remains tenant-scoped.
Each role sees only intended POS functions.
Direct route access is rejected when the required capability is absent.
The dashboard shows tenant-scoped totals and recent activity.

Safety checks and troubleshooting

Apply least privilege.
Separate Sell, Refund, Settings, Reports and Audit duties where appropriate.
Do not use menu hiding as a substitute for capability enforcement.

Stay within the supported module flow

Use the supplied UI, host module lifecycle and documented endpoints. Do not bypass tenant filters, permissions, CSRF, idempotency, rate limits, audit evidence or transaction checks. A stored table or field does not imply that version 1.0.0 exposes a management screen for it.

Was this guide useful?Your response is stored only in this browser.