Skip to main content

Inviting your team

What this is for​

Everyone who uses Restodesk needs their own login. Their role decides what they can see and do — a waiter takes orders, a manager reads the numbers, a chef works the tickets.

Before you start​

Decide the roles first. It's much easier than changing everyone's permissions afterwards.

Adding a member of staff​

  1. Go to Staff.
  2. Select Add Member.
  3. Fill in:
    • Member Name
    • Email address — this is what they sign in with, and it must be unique.
    • Phone number, with the country code.
    • Role
    • Password — a starting password. Tell them to change it.
  4. Save.

They get a welcome email with their sign-in details.

Roles and what they can do​

Go to Settings › Roles.

Each role is a named set of permissions. Restodesk ships with sensible ones — administrator, branch head, chef, waiter — and you can change what any of them is allowed to do, or add your own.

Permissions are grouped by area: menu, orders, POS, customers, staff, payments, expenses, reports, settings. Tick what that role should reach.

A few worth thinking about deliberately, because they cost money when they're wrong:

  • Applying discounts — who can knock money off a bill.
  • Refunds and cancellations — who can void a paid order.
  • Removing items from a kitchen ticket — this is recorded, and it's a common source of waste.
  • Editing menu prices — usually owner and manager only.
  • Reports — most restaurants keep earnings figures to management.

Good to know​

  • A staff member has one role. If someone genuinely does two jobs, give them the role with the permissions they need for both.
  • Changes to a role apply to everyone who has it, immediately.
  • If someone can't see a screen, it's almost always their role. Check Why can't I see this screen? before assuming something's broken.
  • When someone leaves, deactivate their account rather than deleting it. Their name stays attached to the orders they took, which is what you want if you ever need to look back.
  • Staff belong to a branch. Someone who works across two locations needs access to both.

Next​

Your setup is done. Now build the thing you actually sell: How menus, categories and items fit together.