Staff roles
A role answers two questions at once: what a staff member can do with an order, and which orders they see at all. The second matters more than it seems: in a shop with several points of sale, the operator at one point should not be working somebody else's queue, and a courier has no business seeing orders from the next town.
How to open it
Settings, the Team group, a role card, the Edit button. The page also opens through cabinet search by the word "roles".
The section is visible only to the shop owner and only when staff are included in the plan.
What you can do
- Create your own roles and rename the ready ones
- Tick permissions: view, statuses, editing, money, cancellation, printing, comments
- Limit the order visibility scope
- Delete roles nobody works under
How the list starts
On first opening the shop gets four ready roles. This is not a rigid set but a starting point: they can be renamed, reconfigured and deleted.
| Role | What it can do |
|---|---|
| Administrator | Everything, money included |
| Order manager | Statuses, items, delivery, printing, comments. Not money |
| Operator | Statuses, printing, comments |
| Courier | View orders and change the status |
Order visibility scope
Four conditions, any of which may be left empty.
| Condition | Which orders match |
|---|---|
| Points of sale | Pickup orders from the chosen point, plus those delivered from it (the food and water delivery profiles determine the point themselves) |
| Delivery methods | Orders with the chosen delivery method |
| Payer type | Orders from individuals or from legal entities |
| Locations | Orders from the chosen cities |
Two rules worth keeping in mind:
An empty field means "no limit", not "nothing is visible". A role with no conditions sees every order in the shop. The opposite would mean a forgotten filter silently hides work, and the owner would learn about it from a staff member.
Filled conditions apply together. A role of "point A plus legal entities" shows orders matching both conditions, not either of them.
An order with an empty attribute (no point of sale, say) does not match a restriction on that attribute: "sees orders of point A" does not also mean "sees all the orphan ones".
The restriction applies beyond the list. Somebody else's order cannot be opened by direct link, printed or edited: it answers "order not found". The set counters above the list count the same selection: a set promising three orders and opening one is worse than no counter at all.
Scenarios
An operator at one point of sale
- "New role", named for example "Operator at Lenina".
- Tick the permissions: view, status change, printing, comments.
- In "Points of sale" choose the point and leave the other conditions empty.
- Save and assign the role to a person in Staff.
A courier for one city
Permissions are view and status change; in Locations choose the city. Add a delivery method if the courier only drives their own route rather than collecting from pickup points.
Limits
- A role assigned to staff cannot be deleted: move them to another role first.
- The visibility scope does not apply to the shop owner: they see everything, and they are the one who assigns these scopes.