Branches, franchises and roles: who sees what

How do franchise, company and branch fit together?

Nexara's hierarchy runs from franchise to company to branch. The dashboard has separate Franchises and Companies pages, plus Manage Branches and Users. A branch is therefore a level within the business structure, not another name for the company or franchise.

That structure appears in the operational features. Each company gets its own branded ordering website. Orders arrive in one live queue per branch, and menu availability can be changed per branch. A shared catalogue does not mean every outlet has to show the same items as available.

Staff setup has separate parts too: Nexara has named roles, user-to-branch assignments and a permissions module. The branch assignment identifies where a person works; the role identifies their account category. Both belong in the setup record, especially when a manager's responsibilities extend beyond a single outlet.

Nexara handles tens of thousands of orders a month, with dozens of branches across Jordan. These are platform-wide figures, not one restaurant's results. The franchise structure and operations guide for Jordan covers the wider operating context.

Which roles does Nexara have today?

Nexara has twelve named roles. These are the exact identifiers used in the product, including separate roles for franchise ownership and company ownership. Custom roles are not offered today.

The list separates area supervision from branch management and central inventory from inventory management. It also includes the service roles used around orders: call_center, driver and waiter. You do not need to describe every employee as a manager simply because they work in the dashboard.

Use the exact identifier when discussing an account with Nexara. Saying branch_manager is clearer than saying manager when both exist as separate roles. Keep the branch assignment beside it so a later handover records the account's intended location as well as its role.

What can cashiers, managers and owners see?

The explicit payment boundary is own-branch access for cashier, waiter and branch_manager accounts. Nexara also has separate area and ownership roles. The table separates those established controls from broader visibility that cannot be promised from a role name alone.

Nexara includes Product by Branch, Financial, End of Day and Cashier Reconciliation report tabs. Those are concrete reporting tools for branch comparisons and close-of-day work. A full role-by-screen permission matrix, automatic multi-branch visibility for area managers and automatic cross-company revenue access for franchise owners are not established by the verified product facts.

Resolve those specific visibility questions with Nexara during setup, rather than treating the payment rule as a restriction on every screen. The guide to restaurant staff access covers the staff-level discussion.

How do permissions relate to daily branch work?

Live Orders brings phone, website, app, table QR, Talabat and Careem orders into one queue per branch. Open dashboard screens receive live updates. Branch assignment therefore matters to an operation already organised around branch-level order queues, rather than a separate tablet for each ordering channel.

Menu availability is also branch-specific. A local availability change and a catalogue price change are different actions: one concerns whether an outlet can serve an item, the other concerns its selling price. Keep those as separate entries when agreeing on a branch manager's access.

Inventory has branch stock records, stock counting and branch stock requests. These provide concrete work to discuss for inventory_manager and central_inventory accounts, instead of asking for vaguely defined inventory access.

NexaraFlow goes further than naming a role. It uses role-scoped queues and branch assignments for recurring timed tasks. Within workflow, central_inventory is treated as inventory_manager. Seeded templates include Morning Inventory and Daily Inspection, with stages and SLA clocks. The SLA escalation check runs every 5 minutes.

NexaraFlow is a Pro-plan feature. Its role-scoped queues put recurring work into the role structure; branch assignments connect that work to locations. The multi-branch operations guide explains how these features fit into daily branch work.

How should you test access before the first shift?

Keep the acceptance check short and specific. Nexara already provides the hierarchy, roles and branch assignments. The check should establish whether the proposed accounts fit your staff's work, without turning a busy manager into a software tester for every feature.

1. Record the franchise, company and branch names from the proposed Nexara setup. Use those same names on the staff account sheet.
2. Put each account's exact role identifier beside its branch assignment. Distinguish manager, area_manager and branch_manager rather than shortening all three to manager.
3. Check the documented payment boundary using cashier, waiter or branch_manager accounts. Include an own-branch payment action and an attempted payment action for another branch.
4. Ask Nexara to demonstrate the unresolved access requirements with the intended account: the necessary reports, customer records and any editing or CSV export actions.
5. For NexaraFlow, check the assigned branch and the role-scoped task queue. Include inventory work if the account uses central_inventory or inventory_manager.
6. Save the results with the account details. Before temporary branch cover or a staff departure, agree with Nexara which account changes are needed.

For each check, record the action attempted and whether it was allowed or refused. A note such as Financial report opened is more useful than reports work. An unresolved permission should have a named action attached to it, not a request to give the person super_admin.

Does this replace branch manager permissions in a POS?

If you are searching for branch manager permissions in a POS, separate till controls from order operations. Nexara is not a POS or cash register. It is the order and operations layer beside the till, and its roles do not establish control over permissions in your existing till.

At close, the cashier records the day's net sale for reconciliation. Nexara supports cashier net sales and a Cashier Reconciliation report tab. It does not offer accounting or ERP connectors today, so do not plan around a shared accounting permissions system.

Feature availability is separate from staff roles. Call center is a Pro-plan feature; having call_center in the role list does not make it available on every plan. Nexara has a free plan plus paid plans per branch in Jordanian dinar, with current rates on request.

Use the closing WhatsApp option to discuss branch access with Nexara at nexaratech.io. Send your branch structure and the staff roles you need so the conversation can address the actual accounts.