Skip to content

Control and approvals

Control is where owner authority lives: decisions waiting for you, and the permanent record of decisions already made.

The control screen with approvals and the audit trail.
Approvals, incidents and the audit trail.

What is waiting for you, with a count. If it says 3 owner actions need attention, three things genuinely cannot proceed without you.

Some actions inside your business require an owner’s decision. They arrive here with what is being asked, who asked, and what happens if you approve.

Opening one shows the full request. You approve or decline, with a reason, and the decision is recorded against your name.

Service incidents that rose above branch level. Each links to the branch it belongs to.

If the same branch keeps appearing here, the answer is usually structural — coverage, configuration, or a role nobody is filling — rather than a run of bad shifts.

Where you stand against your plan’s limits, and what would unblock a limit you are hitting.

Limits are explained rather than merely enforced: the alert says what the limit is, what your usage is, and what would change it. Plan changes go to Sitora’s billing queue — see Account, plan and reports.

Access problems serious enough to reach the owner: accounts with authority that should not have it, or coverage gaps that leave a branch unable to operate.

Courier applications to your restaurant are approved here. See Couriers.

Open owner audit trail shows every governed action in your business: who did it, when, what changed, and the reason given.

It is immutable. There is no edit, no delete, and no owner override — for you as much as for anyone else. A record that the owner can rewrite is a record that proves nothing when it matters.

Filter it by group, by person, or by branch.

Something is blocked and nobody knows why. Check the attention queue. A pending approval that nobody told you about is the most common answer.

I need to know who changed a price / a role / a setting. The audit trail, filtered to that branch or person. It is the only place the answer exists, and it always does.

We keep hitting a plan limit. Read the plan alert — it says what would unblock it — then request the change from your account.

A branch has repeated incidents. Open the branch from the incident. Look at role coverage and readiness together before concluding it is the team.

Someone asks me to remove an audit entry. You cannot, and nor can Sitora. Record the correction instead; both entries stand and the sequence tells the truth.