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. 1

    Write job profiles

    List what each role must do on POS, backoffice, and messaging.

  2. 2

    Apply presets

    Start from retail, food, or service role templates; trim excess access.

  3. 3

    Audit quarterly

    Remove ex-staff and tighten overrides after busy seasons.

Common questions

Can one person hold multiple roles?

Yes. Still give each person their own login so you can see who did what.

Who can issue refunds?

You choose. Many shops need a supervisor code for voids and big refunds.

Do permissions work across branches?

Yes. You can set roles per shop or for the whole group.

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.