Team

Staff roles and permissions

Five built-in roles with sensible defaults, plus custom roles on Enterprise.

Permissions are role-based. Every team member is assigned exactly one role per restaurant. Permissions are enforced at the API and database level via row-level security — hidden buttons in the UI are never the only line of defense.

Built-in roles

Name	Type	Required	Default	Description
Owner	role	—	—	Full access including billing, integrations, and team management. There can be more than one Owner.
Manager	role	—	—	All operational features. Cannot change billing or assign Owner role to others.
Host	role	—	—	Reservations, floor plan, guest CRM read and write. Cannot view financial reports.
Server	role	—	—	Assigned-table view, mark seated and completed, add notes. Guest contact details hidden by default.
Kitchen	role	—	—	Read-only view of upcoming covers, allergens, dietary notes. No guest contact details, no financial data.

Permission matrix

Name	Type	Required	Default	Description
View reservations	permission	—	—	Owner / Manager / Host / Server (assigned only) / Kitchen (cover counts only).
Create reservations	permission	—	—	Owner / Manager / Host.
Edit floor plan	permission	—	—	Owner / Manager.
View guest contact details	permission	—	—	Owner / Manager / Host. Server only if explicitly granted.
View reports	permission	—	—	Owner / Manager.
Manage billing	permission	—	—	Owner only.
Manage team	permission	—	—	Owner / Manager (Manager cannot create or remove Owners).

Custom roles on Enterprise

The Enterprise plan adds custom roles. Define your own permission set — for example, a Regional Manager with access to a subset of restaurants — from Settings → Team → Roles.