Restaurant staff roles: what should each person see?

What does least access mean during a restaurant shift?

Least access means a person can do their assigned job without inheriting unrelated authority. Start with the work, then choose the role. A cashier handling orders does not automatically need to edit the menu. A branch manager covering a shift does not automatically need company-wide access.

Separate visibility from actions. Reading an order is different from issuing a refund. Review each action separately with the intended staff account, rather than checking only which screens appear. Test what the account allows and what it blocks.

Nexara has a permissions module and user-to-branch assignment. It handles orders and operations alongside your till; it is not a cash register. If you searched for "restaurant staff roles POS", review the till's permissions separately from Nexara's. Access in one product does not establish access in the other.

Which staff roles does Nexara actually have?

Nexara has the following twelve role identifiers. The assignment checks are recommendations for your access review, not a list of built-in permissions. Use them to prepare the account tests before service.

There is no kitchen role in this list. You do not need to use every available role simply because it exists. A small restaurant can have distinct responsibilities without employing a separate person for each one.

The platform hierarchy is franchise, company, branch. Use that structure when discussing access boundaries, rather than describing every supervisor as a manager. The related guide on branch and franchise roles covers that organisational distinction.

What should cashier permissions include?

As an operating policy, a cashier should see the orders and cash information needed for work at their branch. Keep company settings and unrelated branch information outside that routine work. Decide who can approve refunds or price exceptions, then verify whether the proposed setup enforces your decision.

Nexara binds cashier, waiter and branch_manager roles to their own branch for payments. Test that boundary with the assigned cashier account. Review order visibility separately: a payment restriction does not describe access to every screen. HyperPay supports storefront online card payments; it is not a cashier card-terminal workflow.

Nexara also has Cashier Reconciliation and End of Day report tabs, including cashier net sales and cash reconciliation. The cashier records the day's net sale at close for reconciliation. During setup, check report access with both the cashier's account and the account of the person reviewing the close.

• Check which active and historical orders the cashier can open.
• Test cash recording at the assigned branch and confirm Nexara's branch-bound payment restriction blocks payment actions outside it.
• Ask for a controlled demonstration of refund and price-change access using the intended Nexara cashier account. Record which actions are available.
• Confirm who can view reconciliation information and who handles a discrepancy.

For example, a relief cashier covering another location needs an assignment review before service. Keep the owner login out of that handover; arrange the access needed for the shift instead.

Why does kitchen access start with printed tickets?

The kitchen needs usable preparation instructions. That does not necessarily require dashboard access. Nexara does not offer dedicated kitchen display screens today, and its role list does not include a kitchen display role. Kitchen work is supported by printed tickets instead.

Nexara routes printing by branch and printer group, with product-category routing and per-printer category toggles. A grill printer can receive the categories assigned to that station while another printer handles a different preparation area. Bilingual tickets support Arabic thermal printing with English on the same ticket.

Check what the cook actually receives on paper. Put preparation details first rather than giving the kitchen an owner dashboard. Nexara has a visual template builder for kitchen tickets and receipts, with templates assigned per printer.

If your requirement is for cooks to tap a screen to advance tickets through preparation stages, Nexara does not provide that dedicated kitchen-display workflow today. The Nexara feature overview describes the available order board and printing tools.

How should manager, owner and specialist access differ?

Decide which problems a branch manager should handle without calling you, and which company-wide changes need your approval. Write those boundaries down before assigning accounts. Nexara distinguishes branch_manager, area_manager, manager and company_owner. Test each proposed account against the responsibilities you wrote down.

Customer access deserves its own review. Nexara's call-center screen can retrieve saved addresses and past orders from a phone number, and it supports complaint logging. Those are useful for taking a phone order. They are not reasons to give every kitchen worker access to customer records.

Call center is a Pro-plan feature. Check the subscription before assigning phone-order work: the call_center role does not make the feature available on every plan. See call-center order taking for the work that access needs to support.

Stock responsibilities also need a clear boundary. Nexara includes inventory counts and branch stock requests, with inventory_manager and central_inventory among its roles. NexaraFlow has role-scoped task queues and is a Pro-plan feature. Within those workflow queues, central_inventory is treated as inventory_manager. Review access to inventory screens separately from task assignments.

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. Test whether the intended account can complete its work while blocking actions outside that person's responsibility.

1. Write down each person's job and branch scope. Separate the owner account from daily staff use.
2. List required screens and actions. Distinguish viewing from editing or approving.
3. List actions that must be blocked, including unrelated branch payments and sensitive company changes.
4. Test with the intended staff account, not an owner account demonstrating the same screen.
5. Record any mismatch and resolve it before staff rely on the setup during service.
6. Review access whenever someone changes branch, changes responsibility or leaves.

Keep hypothetical tests outside live customer work. Do not issue a real refund merely to discover whether a button is enabled. Ask for a controlled demonstration of sensitive actions.

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 WhatsApp discussion below, prepare your job titles and branch responsibilities. Leave customer details and passwords out of the message.