Team and roles
Updated October 31, 2026
Every person who works in your kitchen gets their own access to Sahen, with a role that decides what they can see and change. You manage the whole team in one place: Business → Team in the console.
The four roles
| Role | Where they work | What they can do |
|---|---|---|
| Owner | Console | Everything. There is exactly one owner per kitchen. |
| Admin | Console | Full console access, including Business settings and Team. |
| Operations | Console | Runs the kitchen day: cutoff, menus, production, deliveries, catalogue, customers, subscriptions and invoices. |
| Driver | Driver app only | Delivers meals. Drivers cannot open the console. |
Owner
The owner is the person the kitchen was created for. A kitchen always has one owner, never two and never none. The owner can do everything an admin can.
Admin
Admins have full console access. Give this role to a partner or manager who needs to change Business settings (operations, delivery zones, payments, Catalog defaults) or manage the team.
Operations
Operations staff run the daily work: building and publishing the weekly menu, managing meals, watching the daily cutoff, printing the production sheet and receipts, handling deliveries, customers, subscriptions and invoices. They do not see Business settings or Team. This keeps prices, payment details and access in fewer hands.
Driver
Drivers use only the Sahen Driver app, one app for all kitchens on iOS and Android. They sign in there, see the stops for the day and scan bags as they go out. A driver needs a display name, and you can add a phone number when you invite them. A driver who tries the console is turned away.
Inviting someone
- Open Business → Team and choose to invite.
- Enter their name, work email and role. For a driver, add their phone number.
- Send the invitation.
The person receives an email with a link. They open it, confirm their name, and only then are they a member of your kitchen. Until that moment the invitation is pending: it shows on the Team page, but the person cannot sign in yet. If the email gets lost, you can send a fresh invitation, and you can revoke one that was sent by mistake.
You can also invite your first colleague in the last step of the setup wizard. See Getting started.
One email, one kitchen
For now, one email address can belong to one kitchen. The same address cannot join, or hold a pending invitation for, a second kitchen. Ask staff who help several kitchens to use a separate work email for each.
Signing in
There are no passwords. To sign in, a team member enters their email and receives a six-digit code by email, then types the code. The console also offers Google sign-in. The driver app uses the same email code.
The console only accepts emails that are already on a kitchen team. An email that has only a pending invitation is refused until the invitation is accepted.
Transferring ownership
Because a kitchen has exactly one owner, ownership changes hands only by transfer. The owner can transfer ownership to an existing Admin or Operations member from Business → Team. Accept the invitation first: a pending invite cannot receive ownership, and drivers cannot become owners.
Good practice
- Give each person their own email. Shared logins hide who changed what.
- Use Operations for kitchen staff who do not need to touch prices or payments.
- Keep at least one Admin besides the owner so someone can manage the team when the owner is away.
Terms used here are explained in the glossary. Questions about roles go to support@sahenos.com.