Restaurant staff roles: what should each person see?
Picture a Thursday rush: kitchen tickets are printing, a customer wants a refund, and the cashier is using your owner login. That account gives them more authority than the task calls for.
Nexara gives restaurants named staff roles and branch assignments as a restaurant order and operations platform built in Amman, Jordan. Kitchen preparation uses printed tickets rather than a dedicated kitchen-display role. Match cashier, manager and owner access to their responsibilities, then test each intended account's allowed and blocked actions before service.
What does least access mean during a restaurant shift?
Least access means giving someone the information and authority needed for their job. Start with the work. A cashier needs to handle the branch's orders; changing company settings belongs with whoever is responsible for the company.
The matrix below is a recommended operating policy. The final column records verified Nexara capabilities and restrictions. Detailed screen access and approval rights belong in the account tests before service.
| Responsibility | Recommended visibility | Recommended authority | Verified Nexara basis |
|---|---|---|---|
| Cashier | Assigned-branch orders, payment details and cash-close information | Handle routine order and cash work; refer refunds and price exceptions to the designated approver | cashier role; branch-bound payments; cashier net sales and reconciliation |
| Kitchen | Preparation tickets for the station, including items and modifiers | Prepare orders and flag shortages to the shift lead | Arabic and English tickets; category routing; templates assigned per printer |
| Manager | Assigned-branch orders, unresolved complaints and close discrepancies | Handle agreed shift exceptions and local availability decisions | branch_manager, area_manager and manager roles; branch_manager payments are branch-bound |
| Owner | Company performance, branch comparisons and financial reports | Approve access policy and company-wide menu or commercial changes | company_owner and franchise_owner roles; franchise, company and branch hierarchy |
Nexara has a permissions module and user-to-branch assignment. It is the order and operations layer beside the till. Review till permissions and Nexara permissions separately, including who may view an order and who may change or refund it.
Which staff roles does Nexara actually have?
Nexara has twelve role identifiers. Verified roles and recommended assignment checks are listed below. Choose roles according to responsibility and location, even when one person covers several jobs.
| Verified role | Recommended assignment check |
|---|---|
| super_admin | Reserve for an established platform-level need. |
| franchise_owner | Identify the franchise and companies overseen. |
| company_owner | Identify the company the person owns or oversees. |
| manager | Define operational duties and branch scope. |
| area_manager | Name the branches in the person's area. |
| branch_manager | Specify the branch and shift-exception responsibilities. |
| cashier | Assign routine order handling and cash-close work. |
| call_center | Assign phone-order work and relevant customer lookup. |
| inventory_manager | Define stock responsibilities and locations. |
| central_inventory | Specify central stock responsibilities. |
| driver | Define delivery duties and necessary delivery information. |
| waiter | Assign branch and table-service responsibilities. |
The platform hierarchy is franchise, company, branch. Write the actual company and branch names beside each supervisor's responsibilities. The related guide on branch and franchise roles explains that organisational distinction.
What should cashier permissions include?
A cashier's recommended view should centre on the orders being handled at their branch and the information needed to close the shift. Keep company settings and unrelated branch information outside routine cashier work. Name the person who approves refunds or price exceptions so the cashier knows where to send a disputed order.
Nexara binds cashier, waiter and branch_manager roles to their own branch for payments. Order visibility and report access should be separate entries in your acceptance checklist because each concerns a different part of the job.
Nexara includes Cashier Reconciliation and End of Day report tabs, with cashier net sales and cash reconciliation. The cashier records the day's net sale at close. Your policy should identify who enters that figure and who investigates a discrepancy against the till.
For a relief cashier moving between locations, the handover should include the branch assignment and the name of the shift approver. Keep the owner's login with the owner. A busy counter is a poor place to discover that a temporary assignment was never reviewed.
Why does kitchen access start with printed tickets?
The kitchen needs preparation instructions it can read at the station. Nexara routes printed tickets by branch and printer group, with product-category routing and per-printer category toggles. A grill printer can receive its assigned categories while a different printer handles another preparation area.
Nexara supports Arabic thermal printing with English on the same ticket. Its visual template builder handles kitchen tickets and receipts, with templates assigned per printer. Give the cook a preparation-focused printout and keep receipt layout decisions with the person responsible for checkout.
For the ticket-template check, print an order containing Arabic item names and modifiers. Confirm that the cook can read the preparation choices without referring to a dashboard. Compare the printed categories with the station's responsibilities, and include a table QR order to check the printed table number if you use dine-in ordering.
Have the station lead read the sample at the actual printer location. A ticket that looks clear at an office desk may be awkward beside the grill. The Nexara feature overview covers the order board and printing tools.
How should manager, owner and specialist access differ?
A branch manager's recommended view is the branch's unfinished work: orders needing attention, complaints and close discrepancies. The owner's view should support company decisions and comparisons between branches. Nexara distinguishes branch_manager, area_manager, manager and company_owner, and includes report tabs across money and operations.
Write down which shift exceptions the manager may resolve and which company-wide changes require owner approval. Give menu pricing responsibility to a named person. Nexara supports per-branch availability, so your policy should also identify who decides an item is unavailable during service.
Phone-order staff need customer information relevant to the call. Nexara's call-center screen retrieves saved addresses and past orders from a phone number and supports complaint logging. Keep that responsibility with staff taking orders or resolving customer issues. Call center is a Pro-plan feature; call-center order taking explains the work involved.
For stock staff, recommended visibility includes counts and branch stock requests within their responsibility. Nexara provides both, with inventory_manager and central_inventory among its roles. NexaraFlow provides task lists by role and is a Pro-plan feature; within those tasks, central_inventory is treated as inventory_manager. Stock-screen access and task assignments need separate entries in the access policy.
How do you test staff access before the first busy shift?
Use a written acceptance checklist with the person responsible for setup. Nexara provides named roles, branch assignments and a permissions module. The acceptance test should establish both whether staff can finish their work and whether sensitive actions stay within your agreed boundaries.
Approve service access after the intended accounts pass the agreed checks.
- Write each person's duties and branch scope, using the recommended matrix as a starting point.
- Assign the proposed roles and confirm the plan includes the features needed for the job.
- List required screens and permitted actions, then list actions that must be blocked. Include unrelated branch payments and sensitive company changes.
- Sign in with the intended staff accounts. Check active and historical order visibility, cash recording and reconciliation access. Request controlled demonstrations of refund and price-change permissions.
- Print the kitchen sample and record every access or ticket mismatch. Resolve these before approving the setup for service.
- Review access whenever someone changes branch, changes responsibility or leaves.
Keep sensitive tests outside live customer work. Use a controlled demonstration for refund permissions rather than issuing a real refund to discover whether a button works.
Nexara's founder, Issa Al-Dalu, answers support in Arabic and English on Amman hours. The Nexara company and founder background identifies the business behind the platform. For the closing WhatsApp conversation, prepare job titles and branch responsibilities, leaving out customer details and passwords.
You can start at nexaratech.io or message the founder on WhatsApp.
What to remember
- Assign access to the job and branch, using a written visibility and authority policy.
- Prepare station-specific kitchen tickets with readable items and modifiers.
- Cashier, waiter and branch_manager payment access is branch-bound.
- Test allowed and blocked actions with the intended staff account before service.
Questions people ask
What roles should a restaurant system have?
Start with cashier, kitchen, manager and owner responsibilities, then add specialists for phone ordering or stock work. Nexara has twelve named roles and user-to-branch assignment.
Can a Nexara cashier take payments for another branch?
Cashier, waiter and branch_manager payment access is bound to the assigned branch. Include that boundary in the account acceptance test.
What should kitchen staff see on their tickets?
Give each station readable preparation items and modifiers for its assigned categories. Nexara supports category-based printing and Arabic and English tickets.
Can I assume a manager can issue refunds?
Confirm refund authority with the intended manager account in a controlled demonstration. Nexara supports HyperPay refunds, and your acceptance checklist should identify who is permitted to use sensitive payment actions.
Should restaurant staff share the owner's login?
Use individual staff accounts with reviewed access. Nexara supports named roles and user-to-branch assignment, so routine work can be set up around staff responsibilities.
Does assigning a role activate a paid feature?
Feature availability also depends on the subscription. Call center and NexaraFlow are Pro-plan features.