Roles and Why Actions May Be Unavailable
Use this guide when someone can open a page but cannot see the action they expected.
What usually controls action visibility?
Most missing actions come down to one of four things:
- the user's role
- the tenant or client they are allowed to work in
- the current status of the record
- whether an admin is impersonating another user
So a missing button does not always mean the user is on the wrong page.
Role summary
| Role | Typical access |
|---|---|
| Super-admin | Broadest access, including some repair tools, unless impersonating another user |
| Owner / Admin | Tenant-wide operational and admin access within their scope |
| Operator | Day-to-day warehouse work within scope |
| Client user | Own-client access only, mostly planning, tracking, and read-only operational visibility |
What client users can usually do
Client users can usually:
- view their own client records
- register expected deliveries for their own client
- submit assembly requests where that workflow is available
- follow progress on orders, inbound work, and returns
Client users do not usually:
- post receipts
- complete warehouse receiving
- create normal shipments
- run warehouse-only stock changes such as repacking
Common reasons a button is missing
The record is in the wrong stage
Examples:
- Start Receiving only appears before the receipt has already moved into active receiving
- Complete Receiving only appears while the expected-delivery receiving flow is still active
- shipment correction actions only appear when that correction is still valid for the shipment
The user has the wrong scope
Even when the role is correct, the record still needs to belong to the tenant and client the user is allowed to work in.
The user is impersonating
Some admin-only actions disappear while impersonating because ParcelPilot respects the permissions of the user being impersonated.
Common questions
Why can't this user create a receipt?
Client users are normally view-only on receipts. Warehouse and admin users can create receipts within their allowed scope.
Why is Complete Receiving missing?
Check whether the receipt came from an expected delivery and whether the receiving step is still active. Standalone receipts use Post Receipt instead.
Why can't this client user build an assembly?
Client users may be able to request assembly work, but the warehouse completes the actual build.
Why can't this user run repacking?
Repacking is a warehouse workflow. Client users do not complete repacking jobs.
Why is a shipment action missing?
Some shipment buttons are hidden because of the order or shipment status, not just because of role. Use Why Can't I Create a Shipment? for shipment-specific checks.
Why can't I use Reverse Dispatch?
Reverse Dispatch can be hidden because:
- the shipment never committed stock
- the shipment has already been reversed
- no reversible shipment remains on the order
- the current user is not allowed to run shipment correction
Use Correcting a dispatched order for the full correction path.
Why can't I delete this order?
Hard Delete is not the normal correction workflow for orders that have entered fulfilment.
It is limited to tenant admin and real super-admin, and only for mistaken manual orders with no meaningful operational history.
If shipment, reservation, allocation, picking, inventory, fulfilment, or other durable operational evidence exists, ParcelPilot keeps the record and expects correction or cancellation instead of deletion.
Use Correcting a dispatched order when the real goal is to unwind a dispatch safely.
Quick checks before escalating
- Confirm the user's role.
- Confirm the active tenant and client.
- Check the record status.
- Check whether the admin is impersonating.
- Refresh the page after any status change that should unlock the next action.