Restaurant User Roles & Permissions
You decide who sees and does what

Role-based access — a separate level for each job.

In RoxPos you define a separate role for each staff group and decide, item by item, which menus and which actions that role can reach. Waiter, cashier, kitchen and manager profiles work with different screens and different permission sets, so everyone sees only the part of the system their job requires. When you add a new employee you simply assign the right role instead of configuring each permission one by one.

Order sub-rights: cancel, discount, comp, move, lock, payment.

Sensitive actions on an order are authorized individually: you can independently turn on or off order cancellation, applying discounts, adding comps, moving tables, locking the check and taking payment. This lets you give a waiter the right to take orders and collect payment while keeping discounts and cancellations off, distributing responsibility at the action level. Thanks to this separation, permission becomes a fine-grained control tool tuned to your workflow rather than a single all-or-nothing switch.

Branch-level rights — a user sees only their assigned branch.

In multi-branch and chain businesses you tie each user to a specific branch, and that person sees only the tables, orders and data of the branch they are assigned to. Other branches' turnover, stock and checks stay completely hidden from that user, so data never mixes between locations. Head office, on the other hand, keeps seeing all branches from a single panel and can compare them against each other.

Operation safety — critical actions are off for unauthorized staff.

Abuse-prone actions such as order cancellation, discounts, comps and check locking stay unclickable for staff who lack the permission, so accidental or deliberate interference is blocked at the source. Because employees can only perform the operations defined for them, it is clear from the outset who can do what on register and check movements. This setup reduces the margin for error and makes each role's reachable actions visible from a single screen.

Letting waiters take orders without discount/cancel rights

You give the waiter permission to open tables, add orders and take payment while keeping discount and order-cancellation rights off, so the service flow stays fast while price tampering is prevented. When a discount or cancellation is needed, an authorized manager steps in, since those actions are open only on the manager role. In this way speed and oversight are both preserved during daily service.

Letting only the manager see reports and revenue

You open access to turnover, profit-and-loss and sales reports only to the manager and owner roles, and fully hide these menus from the waiter and cashier roles. This way sensitive financial data such as daily revenue and costs never appears in front of service staff. The manager, in turn, can follow live reports on screen, export them as PDF or Excel and compare branches against each other.

Limiting staff to their own branch in multi-branch setups

You tie each branch's staff only to their own branch, so a user cannot reach the tables, orders or reports of other branches. The branch manager fully runs their own location while head office keeps seeing and comparing all branches from a single panel. This structure prevents data confusion and unauthorized access at the branch level as the chain grows.

Preventing comp/discount misuse through permissions

You grant the rights to add comps and apply discounts only to a limited number of trusted roles, while these actions stay disabled for the rest of the staff. This prevents revenue from being eroded by unwarranted comps or fictitious discounts from the very start. Because comps and discounts are open only on authorized roles, who can perform them stays limited and clear from the outset.

RoxPos Blog — Guides

All Features