Branch admin
The branch admin workspace runs one branch. It is the widest workspace in Sitora Pro, and the only one that can change who works there.
The tabs
Section titled “The tabs”| Tab | What it holds |
|---|---|
| Overview | Branch health, pressure, and what needs attention |
| Team | Everyone with access here, and their roles |
| Menu | Availability, price and prep time for this branch |
| Stock | Branch stock risk and the items affected |
| Control | Branch-level actions, and the audit trail |


Overview
Section titled “Overview”Branch facts grouped by area — Service, Payments, Kitchen, Released — plus what needs attention.
When nothing needs you, it says so. An empty attention list is an answer, not a missing screen.
Everyone with access to this branch: name, contact, roles, and whether the membership is active. Counters show how many memberships are active out of the total and how many carry warnings.
Filter by All status, Active, Inactive, or Warnings. Search by staff, contact or role.
Adding someone
Section titled “Adding someone”Add staff brings a person into this branch and gives them a role. They need a Sitora account first — you are granting access to an existing account, not creating one.
Once added, they see this branch in Sitora Pro when they next open it, or after Recheck access.
Changing or removing access
Section titled “Changing or removing access”Opening a person shows their memberships, roles and warnings, and the access actions available.
Every access change is governed: it asks for a reason, asks you to hold rather than tap, and is recorded permanently against your name.
Warnings
Section titled “Warnings”A membership with a warning is one worth a look — a role that no longer resolves to a workspace, an account that cannot sign in, coverage that has fallen through. The list is short by design. Work it.

Branch-level control over three things:
- Availability — whether guests here can order it
- Price — what it costs at this branch
- Preparation time — what guests are told to expect
These are this branch’s settings. Another branch of the same restaurant can sell the same dish at a different price. That is the point of branch-level control.
Items carry stock warnings — Low, Out, Mismatch — so you can see when a price change is beside the point because the item is not sellable anyway.
Mismatch means the item is on sale but its stock says it should not be. Fix one side or the other; leaving it is how guests order something that does not exist.
The branch’s stock risk and the items affected — a summary view, not the working surface. The day-to-day belongs to the inventory manager, and Open inventory workspace takes you there.
Control
Section titled “Control”Branch-level control actions, and the audit trail.
Every governed action in this branch is in the audit trail: who did it, when, what changed, and the reason given. It is readable and permanent — there is no edit and no delete, by design.
When something is disputed, this is the answer.
Day-to-day recipes
Section titled “Day-to-day recipes”A new person starts today. Have them install Sitora Pro and sign in first, so the account exists. Then Add staff and give them the role. Have them Recheck access.
Someone left. Remove their access the same day, with a reason. Access that outlives employment is the one access problem that is genuinely dangerous.
Someone needs to cover a different job tonight. Add the second role rather than swapping. They can switch between roles themselves during the shift.
A dish is mispriced at this branch. Fix it in Menu. It applies here only.
We are out of something all evening. Switch it off in Menu or have the inventory manager do it. Either works; doing neither means guests keep ordering it.
Someone says they cannot see anything in Pro. Check three things in order: are they in the right branch, do they have an active membership here, and does that membership carry a warning.
Someone asks me to change history. You cannot, and neither can anyone else. Record a correction instead.
What a branch admin cannot do
Section titled “What a branch admin cannot do”- Work across branches. One branch at a time; switch to work in another.
- Change plans, billing or subscriptions. Owner, in Sitora Biz.
- Edit the audit trail.
- Confirm payments. Cashier.
- Act while offline. Branch control actions are online only.