POS Roles
POS Roles control what staff are allowed to do on the till. A role can define the staff-facing name, which branches that role can be used in, and which restricted actions the role is allowed to perform.
Renaming a role will reflect historically on your sales reports, so change role descriptions carefully.
Edit tab
The Edit tab stores the core identity of the role.
- Reference: internal code for the role, for example 006.
- Description: the role name shown in the system, for example STANDARD USER.
Use this tab when creating a new role or renaming an existing one.
Branch Restrictions tab
The Branch Restrictions tab controls which branches the role applies to.
- Open the role.
- Go to Branch Restrictions.
- Click Add Branch.
- Select the branch or branches the role should be limited to.
- Save the role.
If a branch is listed here, the role is restricted to those locations only.
Restrictions tab
The Restrictions tab defines which sensitive POS actions the role can access.
Examples include:
- BLIND-REPORTS
- VOIDAFTERPRINT
- VOIDALL
- VOIDRESTORE
To add a restriction:
- Open the role.
- Go to the Restrictions tab.
- Click Add Restriction.
- Select the action to allow for that role.
- Save the role.
| Restriction | What it controls |
|---|---|
| BLIND-REPORTS | Access to blind reporting functions on POS. |
| VOIDAFTERPRINT | Ability to void after a receipt or order output has already been produced. |
| VOIDALL | Ability to void all items or clear a sale in restricted scenarios. |
| VOIDRESTORE | Ability to restore previously voided transactions or items where allowed. |
When to use separate POS roles
- Create different roles for supervisors, managers, and standard staff.
- Limit sensitive functions such as voids and reports to trusted users only.
- Use branch restrictions where some users should only operate in one site.
FAQ
What happens if I rename a POS role?
The role name will update historically in sales reports, so rename roles with care.
Can a role be limited to one branch?
Yes. Use the Branch Restrictions tab and add the branch or branches where the role should apply.
What are restrictions used for?
Restrictions control access to sensitive POS functions such as voids and certain report actions.
Should every user have the same role?
Usually no. It is better to separate standard staff and managers so sensitive actions are only available where needed.