Team and roles

Why separate logins#

Because a shared password knows nothing about roles. Whoever needs the kitchen screen does not need the billing, and whoever drives out should not be able to change prices.

Everyone signs in with their own account. What they see is decided by their role, and not only in the interface: the boundary sits in the database. A driver does not get to see a pickup order even when they know its identifier.

The five roles#

• Owner: everything, including plan and billing. Whoever created the restaurant is the owner, and the last owner cannot be removed.
• Manager: everything except plan and billing.
• Front of house: orders, reservations, tables and the kitchen display.
• Kitchen: kitchen display and orders. Nothing else.
• Driver: deliveries only.

Changing a role or removing someone#

Under Team, right on the person. There is no save button: switching the role or setting a tick saves straight away, and the note at the bottom edge confirms it.

Both take effect immediately, on someone else's device too. The server checks the permission on every single request, so anyone you remove can do nothing from that same moment; the app notices within a minute at the latest, and at once as soon as it comes back to the foreground, and from then on shows only what the new role is allowed.

That is the case that matters: an invitation went to the wrong address and a stranger accepted it. Removing them is enough, and it works right away. You do not have to ask anyone to sign out.

Inviting someone#

In the dashboard under Team. All you need is the email address.

1. 1

   Address and role

   Enter the person's email address and pick one of the five roles.

   Dashboard, Team

2. 2

   Fine-tune it

   If no role fits exactly, switch “Areas” to your own selection and tick them one by one.

3. 3

   Invite

   Tap “Invite”. The person gets an email with a link that is valid for fourteen days.

4. 4

   If nothing arrives

   Copy the link from the list of open invitations and pass it on another way.

How an invitation runs#

Under Team you enter the email address, pick the role and send the invitation. The person gets a mail with a link; the link is valid for fourteen days and can be redeemed only once.

The invitation is for exactly the address you typed in. Forwarding the link gives no access away: only someone signed in with that address can join. Everyone else reads which address the invitation is for and can sign in correctly straight away.

They set their own password and confirm their address. The confirmation mail can be opened on any device, on the phone too when the account was created on a computer.

After that they land straight in your restaurant, not in setting up one of their own. No plan is asked for either: your subscription covers your team.

If the mail does not arrive, you copy the link in the dashboard and send it yourself. It sits next to every open invitation.

Anyone who already runs their own restaurant on Flavoso and works for you as well gets a picker in the sidebar and switches between the two there. It shows only their own restaurants, never a colleague's access.

Setting areas one by one#

The role is the default, not a straitjacket. Per person, ten areas can be switched on and off one by one: Orders, Kitchen display, Deliveries, Reservations, Menu, Tables & QR, Numbers and visitors, Settings, Manage team and Plan and billing.

The usual case for it is the driver who also works the counter in the evening: role Driver, plus Orders ticked.

As long as you tick nothing, the role applies. That is something different from an empty selection: an empty selection expressly means nothing at all.

Requirements for access#

As the owner you decide what someone has to bring in order to get into your dashboard at all. The box sits under Team, above the member list, and only you see it: a manager may invite people, but not change the rule they stand under themselves.

There are two rules, and neither of them applies to you as the owner. That is deliberate: a restaurant whose only owner locks themselves out would have nobody left to undo it.

• Two-factor sign-in: for nobody, for managers or for everyone on the team, as you like. Anyone without it is sent to set it up the next time they open the dashboard and gets no further until they have. An authenticator app on the phone is enough.
• Sign-in expires: after 7, 14, 30 or 90 days everyone has to sign in again. Meant for devices that live in the restaurant and are shared by several people. Out of the box a sign-in does not expire.

What a driver sees#

A list of their deliveries, nothing else. The address at the top, large, next to it the amount and whether it has already been paid online. One button opens the route in the maps app, one dials the guest's number.

Two taps: I am heading out, and delivered. They cannot cancel and they cannot change prices.

If there is a tip on the order, they see it there, so they know what to collect.

The list keeps itself up to date, in the browser as in the app: a run that becomes ready appears without anyone reloading the page. On top of that they get a notification on their phone as soon as a delivery is ready to go out, as long as they left it on under Account, tab Notifications.