A role is the ceiling. Venue access is the reach. Both matter, and they are set separately — see Venue access for the second half.
The roles
Owner — everything. Settings, billing, users, every venue. The account that answers for the organization.
Org admin — everything operational: settings, thresholds, user management, every venue. This is the working admin role.
Org manager — sees every venue, reads every report. Cannot manage users or change organization settings. For someone who oversees the group without running it.
General manager — full operational access, but only on their assigned venues. Sales, reports, forecasts, inventory, recipes, invoices — for their venues, never the group.
Manager — narrower than a GM, on their assigned venues. Day-to-day numbers without the settings.
Chef — the kitchen: recipes, inventory, suppliers, invoices, food cost. Not the full P&L. For someone who needs to know what a dish costs, not what the group made last quarter.
Accountant — financial reports and exports. Read-only where it matters.
Choosing
The question is not "how senior are they". It is "what do they need to do their job today".
A chef who also runs the floor needs a GM role. A GM who never touches inventory still gets it — the role does not slice that finely, and that is fine.
Give the narrowest role that works. You can widen it in thirty seconds when someone's job changes. Widening after an incident is a different conversation.
Roles and venues are independent
This trips people up.
A general manager with one venue assigned sees one venue. A manager with twelve assigned sees twelve — but with a manager's depth on each.
The role decides what. The venue list decides where. Setting one without the other gives you an account that is either useless or too broad.
Changing a role
Open their card in Settings → Team, change the role, save. It takes effect on their next page load.
Changing a role does not touch venue access. If you promote a manager to GM, they still have exactly the venues they had before.
Cost center children
If a venue is a child of a shared POS account — a hotel restaurant, say — assign the child, never the parent. The parent is not a restaurant, it is a POS account. See Key concepts.
Next
Venue access — the other half.