Use case
Staff, roles, and permissions that scale with headcount
Decide who can sell, refund, change prices, message customers, or export money reports—reduce mistakes and fraud as you add people and branches.
Roles that match real jobs on the floor
Job-shaped roles
Cashier, supervisor, manager, finance—not one mega-admin.
Override paths
Sensitive moves require the right PIN or approver.
Branch scope
Limit visiblity per location when needed.
Permission design workshop
- 1
Write job profiles
List what each role must do on POS, backoffice, and messaging.
- 2
Apply presets
Start from retail, food, or service role templates; trim excess access.
- 3
Audit quarterly
Remove ex-staff and tighten overrides after busy seasons.
Common questions
Can one person hold multiple roles?
Yes, but best practice is separate accounts per person for audit trails—even if hats overlap.
Who can issue refunds?
You configure it. Many retailers require supervisor PINs for voids and refunds above a threshold.
Do permissions work across branches?
Multi-branch groups assign roles per location or centrally, depending on your governance model.
Map this workflow to your business
Tell us your country, team size, and top pain—we will show the matching modules and a sane rollout order.