Restaurant Staff Roles and Permissions Explained
6 min read ·
An employee needs the tools required for their job, not every screen in the system. Giving everyone owner-level access may seem convenient during opening, but it makes responsibility harder to trace later. Start with actual tasks, separate routine execution from sensitive approvals and review access whenever someone changes responsibilities or leaves the restaurant.
Define access around work, not trust alone
List the actions each role performs: taking orders, collecting payment, preparing food, delivering orders or reviewing accounts. Identify decisions that need oversight, such as cancelling an order or changing business settings. Clear limits are not a statement of distrust. They also protect employees from performing unfamiliar actions or being held responsible for decisions outside their remit.
In ORO’s permissions map, owners can access branch administration, settings and staff-role assignment. Managers have access to areas including menu management, staff, reports and daily operations, but assigning roles is not a default manager permission. Treat these defaults as a starting point and check the account’s effective access, particularly where permission overrides have been configured.
Match operating screens to each responsibility
ORO’s default map gives cashiers access to POS, orders, delivery and reservations. Waiters can access orders and reservations; chefs can access orders and the kitchen display; drivers can access delivery; accountants can access reporting and audit areas. POS order cancellation is a separate permission from operating POS, so the ability to sell does not automatically mean permission to cancel.
Turn that division into a usable service procedure. A cashier who needs a cancellation should know who can approve it and how to reach them during a rush. An accountant who needs operational context should request it rather than borrow a manager’s login. Avoid shared accounts used to bypass restrictions, because they blur who performed an action and why.
Keep PIN verification separate from authorization
Identity checks and working permissions solve different problems. Confirming who an employee is does not mean they should see payroll or business settings. Give each person their own account and establish a practical process for shared devices or forgotten credentials. Borrowing a colleague’s account should not become the fallback whenever someone has trouble signing in.
Where PIN verification is enabled, treat the code as personal information and do not display it beside the terminal. Do not assume it independently replaces every sign-in step or changes the permissions attached to a role. Test the actual login journey with the employee, then check that the required tools are available and unnecessary sensitive tools are not.
Review access when responsibilities change
Make access review part of hiring, promotion, transfer and departure. When someone moves into a new role, consider what to remove as well as what to add. Otherwise, employees can accumulate access that no longer matches their work. Assign responsibility for completing the review before the first shift in the new position and for handling departing employees’ accounts.
Schedule periodic checks of accounts and roles with operational and financial leads where appropriate. Ask why each sensitive permission is needed and who provides cover when an approver is absent. Keep a short exception procedure so service pressure does not become a permanent reason to broaden access. The aim is clear responsibility without making ordinary work unnecessarily difficult.
Frequently asked questions
Can managers assign staff roles by default?
The reviewed permissions map reserves role assignment for owners and the platform administrator, rather than granting it to managers by default.
Does POS access include order cancellation?
No. ORO separates POS operation from cancellation; default cancellation access is assigned to owners, managers and the platform administrator.
Does a PIN determine an employee’s permissions?
No. PIN verification concerns identity at login; available tools depend on the roles and permissions applied to the account.