Roles and Permissions for Multi-Outlet Restaurant Teams

Restaurant staff roles and permissions decide who can see an order, change a price, cancel a delivery, refund a customer or read last month's revenue. In a single outlet you can get away with everyone sharing one login. Once you run three or four kitchens, that shortcut becomes the most common way money leaks, menus drift between branches and nobody can say who cancelled an order at 9 pm on Saturday.

This post lays out the roles a multi-outlet team actually needs, which permissions belong to each role, how to scope access by outlet rather than only by job title, and the mistakes owners make when they set this up in their ordering software.

Why one shared login stops working at outlet number two

With one shared account, every action is attributed to "the restaurant". A discount, a cancellation, a price edit and a refund all look the same in the log, so when something goes wrong you are left asking staff who did it. Most of the time the answer is nobody.

Staff churn makes it worse. When a cashier leaves, you either change the password for everyone and re-share it on a WhatsApp group, or you leave the door open. Neither is a system.

Take a realistic example. An outlet manager in Indore marks 14 online orders as cancelled across one weekend. Your dashboard shows ₹21,000 less revenue than the kitchen's KOT count suggests. If everyone used the same login, you cannot tell whether those were genuine customer cancellations, duplicate orders cleaned up, or food that went out the door unbilled. With a per-person login and a role that limits who can cancel, the question answers itself.

The wider operating model for a chain, including how menus, pricing and reporting should be centralised, is covered in our guide to multi-outlet restaurant management. This post goes deep on one piece of it: access.

The five roles a multi-outlet restaurant needs

You do not need twenty roles. Five cover almost every chain under ten outlets.

Owner or head office admin

Sees everything across all outlets: orders, revenue, customer insights, payment settings and staff accounts. This is the only role that should be able to add or remove users, change bank or payment gateway details, and edit the brand menu. Keep this to one or two people.

Outlet manager

Runs one branch. Accepts orders, updates status, handles complaints, marks items out of stock, and views that outlet's daily revenue. A manager may be allowed to cancel an order or apply a discount, but every such action should carry their name. They should not see other outlets' numbers unless you deliberately want that comparison visible.

Kitchen and counter staff

Need to see incoming orders for their outlet, print KOTs, and move orders from accepted to preparing to ready or served. They do not need revenue, customer phone numbers beyond the order itself, or menu editing. This role is where a staff app with loud new-order alerts matters more than dashboard access.

Accounts

Read-only access to revenue, settlements, GST bills and invoices across outlets. Accounts staff should never be able to change an order or a price.

Marketing

Can create and send WhatsApp campaigns, set coupons and promo banners, and read customer insights. They should not be able to touch orders or prices. If campaigns draw from a prepaid wallet, the owner should be the one topping it up.

A permissions matrix you can copy

Use this as a starting point and adjust to your structure. "Own outlet" means the person sees only the branch they are assigned to.

The matrix is the easy part. The discipline is reviewing it every time someone joins, changes outlet or leaves.

Scope access by outlet, not only by role

A role answers "what can this person do". Outlet scope answers "where". Both matter once you have more than one kitchen.

The manager at your Koramangala outlet should see Koramangala orders and nothing from Indiranagar. Your central kitchen supervisor, on the other hand, may need to see prep orders from three outlets at once. A regional manager might need two outlets but not the rest. This is why many chains want software that assigns a person to one or more outlets independently of their role. It is a common need, and how it works depends on how your tool separates outlets.

Where each outlet runs as its own store with its own WhatsApp number, as it does in Tezzu today, you add each person to the staff of the store they work at and give them a role there, while head office reads reporting across all stores. People who genuinely work across outlets, like a regional manager, are the case to plan for before you set anything up, because they do not fit neatly inside one store.

If you let outlet managers set their own prices, scope that too. The cleanest pattern is one brand menu owned by head office, with outlet managers allowed to change prices only within a band you set and only at their own outlet.

Permissions that protect your money

Four permissions deserve extra care because each one is a direct path to leakage.

• Cancellations and refunds. Allow them at manager level, never at counter level, and insist the system records who did it and when. A weekly look at cancellations by person takes five minutes and ends most problems before they grow.
• Price and menu edits. Keep these with head office. A ₹20 "temporary" price cut at one outlet quietly becomes permanent, and a month later your margin on that item is gone.
• Payment and bank details. Owner only. Nobody else needs to see where settlements go.
• Campaign spend. Marketing can draft and send, but the prepaid balance they draw from should be topped up by the owner, so spend is a conscious decision each time.

Common mistakes when setting up staff access

• Everyone is admin "for now". "For now" lasts years. Set roles on day one; downgrading someone later feels personal and rarely happens.
• Ex-staff still have access. Make removal part of the exit checklist, the same day as the final salary. Remove the staff app login too, not only the dashboard.
• One phone for the whole kitchen. If three people share a device for order alerts, you are back to a shared login. Give each shift a named user, even if the phone stays at the counter.
• Over-restricting the kitchen. If kitchen staff cannot move an order to "ready", they call the manager for every order, and your manager becomes a bottleneck. Status updates belong with the people doing the work.

For the single-outlet version of this topic, including how to think about who sees what on a small team, see restaurant staff management: roles, permissions and who sees what.

How Tezzu handles staff roles across outlets

Tezzu follows the role side of the pattern above. You add staff accounts to your dashboard and assign each person a role that limits what they can see and do, so the owner keeps menu, pricing, payment and staff settings while outlet teams handle orders. Each team member logs in as themselves, which means cancellations and status changes carry a name.

Kitchen and counter staff work from the Tezzu staff app, which gives new-order alerts so nobody has to watch a screen during a rush. Details are in our guide to the Tezzu staff app.

For chains, Tezzu runs each outlet as its own store profile under one account, with its own WhatsApp number, store page, menu, delivery zones and staff. You add each person to the store they work at with a role there, and head office sees reporting across all stores. Owner and admin accounts stay with the owners. The live dashboard shows orders, revenue and customer insights, which is what your accounts and marketing roles read from.

Two common needs work differently today: one login covering a chosen set of outlets, for a regional manager or central kitchen supervisor, and one shared menu that head office edits for every outlet. In Tezzu each outlet is its own store with its own staff and menu, so bring your org chart to a demo and we will walk through what fits.

Frequently asked questions

What roles should a restaurant have in its ordering software?

Five roles cover most chains under ten outlets: an owner or head office admin with full access, an outlet manager per branch, kitchen or counter staff who only handle orders, a read-only accounts role for revenue and invoices, and a marketing role for campaigns and coupons. Add roles only when a real person needs a combination these do not cover.

Should an outlet manager be able to see other outlets' sales?

Usually no. Scope each manager to their own outlet so they focus on their numbers and you avoid awkward comparisons on the floor. Head office sees all outlets side by side. If you run a friendly competition between branches, share a weekly summary on purpose rather than giving everyone full visibility by default.

How do I stop staff from giving unauthorised discounts?

Keep price edits with head office, allow discounts and cancellations only at manager level, and make sure every such action is logged against a named login. Then review cancellations and discounts by person each week. Most leakage stops once staff know the log exists and is read.

Do delivery riders need a login?

Only if they update order status themselves. Many small chains have the outlet mark "out for delivery" and "delivered", so riders need nothing beyond the address. If riders do update status, give them the narrowest role possible at their outlet, with no access to revenue or menus.