Who can do what¶

Everyone who uses KJB signs in as themselves, and what they can do follows from their role. This page explains how that works and why you sometimes cannot do something you expected to.

Roles carry most of what a person can do¶

Each person has a role — manager, cashier, captain, storekeeper, kitchen, accountant, administrator — and the role carries most of what they can reach. So the answer to "can Priya void this?" usually starts as "can a cashier void this?".

Roles are not the only thing involved. Some actions are supervised and need someone else's approval, and where a restaurant runs more than one outlet a person's access can be scoped further. Those are separate questions from the role itself.

Three different answers to "can I?"¶

When you try something, KJB gives one of three answers, and they are not the same:

Yes — it happens.

Not for your role — the action is not available to you at all. Someone with the right role has to do it. This is not a fault; it is the design working.

Yes, with approval — the action is allowed but deliberately supervised. You are asked for a manager's approval before it goes through. Sensitive actions sit here on purpose, so that they are possible when genuinely needed but never silent.

An approval prompt should correspond to something you just did. Asking to give a discount, void a line, or override a price — those are the moments it belongs to. If one appears when you have not asked for anything, or on screen after screen, that is not the supervision working. Report it rather than getting into the habit of dismissing it: the prompt is the control that guards discounts, voids and price overrides, and it only guards them while people still read it.

A refusal is worth reading before assuming a fault. A missing button or a refused save may be a permission — but it can also be an error, so the wording on screen is what tells you which.

Seeing who has access¶

Setup ▸ Users lists the people who can sign in, with their roles. Reading that list is available to managers as well as administrators, which is what lets a manager answer "who is set up here?" without waiting for anyone.

Adding or changing a user is an administrator's job¶

Creating a user, or changing an existing one, is supervised. A manager attempting it is asked for approval rather than being quietly refused, and cancelling that prompt ends with KJB saying the action is not permitted for their role. Nothing is created or changed in the meantime.

If you need someone added, or someone's role changed, that goes to an administrator.

What to do when someone cannot do their job¶

Check what they were actually trying to do, not the screen they were on. Permission follows the action.
Check their role is the one you think it is — Setup ▸ Users shows it.
If the action is supervised, a manager can approve it in the moment rather than the person having to stop and find someone later.
If it is simply not for their role, changing that is an administrator's decision, and worth thinking about rather than doing reflexively — the restrictions exist to make some things deliberate.

Menu items — an example: captains and cashiers can see the menu but not change prices