Skip to content
Back to BiteTheMenu Site

Roles and capabilities — bundles of permissions you reuse across the team

A role is a named bundle of permissions — Cashier, Manager, Head Chef — that you assign to a person on the Members page. Instead of choosing thirty individual permissions per hire, you pick one role from a dropdown. The same definitions apply to members who sign in by email and to PIN-only terminal employees: edit Cashier once and every PIN cashier picks it up instantly.

The rule: build roles around jobs, not people. For a one-off tweak (“Marco also handles social this month”), use a personal override on the Members page, not a new role.

How it works

  1. Open Admin → Settings → Roles. The left rail lists every role; the right pane shows the selected role’s label, description, and capability toggles grouped by area (Inventory, POS, Growth, …).
  2. Flip toggles on or off, then Save changes — every person on that role updates immediately.
  3. Use the preset buttons (Owner, Manager, Staff, Clear) as a starting point, then tune.
  4. + New creates a custom role (label, short key like head_chef, seed bundle). It’s assignable on the Members page right away.
  5. Custom roles can be deleted once nobody is assigned to them. The five built-in System roles (Owner, Manager, Shift Lead, Cashier, Staff) can be edited but never deleted.

Good to know

  • You only see permission groups for services your venue subscribes to — a venue without a till won’t wade through POS, kitchen-display, or roster toggles. If a service is activated later, its groups appear with any earlier settings intact.
  • Editing roles is owner territory by default (it changes what everyone on the role can do, including at the till).
  • Presets and the capability counter also respect your subscriptions, so the numbers always refer to permissions you can actually see.
  • Members — assign roles to people; per-person permission tweaks.
  • Audit log — every role change is logged with actor and timestamp.
  • Telegram bot — the bot’s allowed actions are capped by each member’s role capabilities.