A page, tab, or action is missing

remoteEaze hides many routes, sidebar items, tabs, and buttons when the current authorization snapshot cannot perform the underlying task. Record state and workflow configuration can hide an action even when permission is present.

Check in this order

1. Confirm the correct Company and surface: Dashboard or Workbench.
2. Confirm the user is active and the intended Role is assigned.
3. Check the exact entity/action permission, not the user's job title.
4. Check Dashboard Access or Field Agent Role for the chosen surface.
5. Check data-access scope and Accessible Branches.
6. Check the record status, business status, ownership, and whether it is deleted/inactive.
7. For maker-checker, check required authorization level and maker/previous approver separation.
8. For a workflow command, check the current stage, accepted assignment, Requirements, Review, and configured Action/Transition.
9. Refresh the session after a Role or permission change.

If the API rejects an action that the UI displayed, capture both the visible button and server message. That is a permission-visibility mismatch, not a cue to broaden the user's Role without review.

On Customer records, Stakeholders is Corporate-only and Group is Group-only. Contributions additionally requires Read Group Contribution Balance or Read Group Contribution Entry. Accounts requires Read Account. Balances and History use their permissions independently. Record approval actions remain in the shared maker-checker panel under Record & Audit and only appear while a decision is available; secondary actions are in the header's Actions menu. See View and maintain customer records.