In brief
The Access and permissions screen defines who is allowed to do what: the rights of each role, the sensitive actions subject to a threshold, and who can validate an override.
Who / when
For the Admin, when setting up the security policy, then to adjust it.
How to access
Admin → Permissions.
Requirements
🔑 Manage permissions (reserved for the Admin)
Screen tour
Four tabs:
| Tab | Content |
|---|---|
| Roles | The list of roles with their number of active rights. |
| Rights | The detail of the rights, enabled per role. |
| Sensitive actions | The operations subject to a threshold/approval (discount, refund…). |
| Manager validation | Who can approve an override (Validator badge). |
Permissions are assigned to roles and applied to employees. Some sensitive permissions require an explicit grant, even for an administrator. Check the saved policy: permission counts depend on the saved policy. A permission does not replace an active module or a required manager approval.
Step-by-step
Modify the rights of a role
Roles tab, tap a role (e.g. Cashier).
In Rights, enable/disable the permissions.
Save the changes.
Define a sensitive action and its threshold
Sensitive actions tab: choose an action (e.g. refund, discount).
Set the threshold beyond which an approval is required.
Designate the validators
Manager validation tab: indicate which roles can approve (Validator badge — typically Manager and Administrator).
Link with day-to-day operation
It is this policy that triggers the "Authorization required" screen seen at the register: for example, a Cashier who refunds must have it validated by a Manager/Admin (see Receipts, void & refund and Discounts & promo codes).
Messages & edge cases
Tips
Calibrate the thresholds according to trust: a low discount threshold forces approval and limits abuse, without blocking the small common discounts.