People and access
People answers: who has access to my business, and what are they doing with it.
The roster
Section titled “The roster”Everyone across your branches, searchable by name, role or branch, and filterable to All, Active, or Attention.
Tapping a person opens their profile: which branches they work at, in what roles, since when, and what needs attention about their access.
Access alerts
Section titled “Access alerts”The short list of access problems worth acting on — someone with a role that no longer resolves, an account that cannot sign in, a membership that outlived its purpose.
Work this list. Access problems are quiet until they are not.
Role coverage
Section titled “Role coverage”Whether each branch actually has the roles it needs to operate. A branch with no cashier cannot confirm payments; a branch with no kitchen role has nobody on the production board.
Coverage gaps are the most predictable cause of a bad service, and the only screen in Sitora that can see them before they happen.
Staff activity and pay
Section titled “Staff activity and pay”Staff activity & pay shows attributed actions, earnings estimates, and the per-action salary rates behind them.
Two things to be clear about, because they matter:
- It is derived from operational records, not from a clock-in system. It reflects what people actually did in the apps.
- Earnings are estimates. Sitora is not a payroll product, and this is not a wage calculation. It is a way to see how work and pay relate — a starting point for a conversation, not the end of one.
Used well, it answers “who is carrying this branch” with evidence rather than impressions. Used badly, it becomes a stick. It is your call which.
Changing someone’s access
Section titled “Changing someone’s access”Access changes are governed: a stated consequence, a reason, and a hold rather than a tap. Every one is recorded permanently with your name against it.
You can also delegate: branch admins can manage access at their own branch, which is usually what you want at more than two or three branches.
Day-to-day recipes
Section titled “Day-to-day recipes”Someone left the business. Remove their access the same day, with a reason. This is the one access task that is genuinely urgent.
A new manager starts. Have them create a Sitora account and sign in first. Then grant the role — at the branch, or as a branch admin if they will manage access themselves.
Someone says they cannot see anything in Sitora Pro. Check their branch and role here. Then have them use Recheck access.
I want someone to run one branch without seeing the others. Give them branch admin at that branch. Branch roles do not see across branches; that is the owner’s product, not theirs.
Someone’s earnings estimate looks wrong. Look at the attributed actions and the action rates behind it. The estimate is arithmetic over recorded work — if it looks wrong, either the rates or the attribution is where the disagreement actually is.
What you cannot do here
Section titled “What you cannot do here”- Create accounts for people. They sign up; you grant access.
- Edit what someone did. Activity is derived from records, and records do not change.
- Give someone access to a restaurant you do not own.