Multi-location setup
Run two restaurants or twenty — Onboard scopes every module per location while keeping team, billing and brand identity centralized.
A workspace can contain any number of locations. Reservations, tables, menu items, vouchers, shifts, knowledge entries and analytics are isolated per location. Team members can be assigned to one location, several, or all of them — their role and module access apply per assignment.
A workspace is the top-level container. Locations live inside it. Billing, the team directory and brand defaults are workspace-level; everything operational is location-level.
What is scoped per location
When you create a new location, the following are independent by default:
- Reservations, the floor plan, sections and table combinations
- Menu items, categories, specials and the public menu widget configuration
- Vouchers (codes are location-scoped unless a workspace-wide template is used)
- Shifts, time entries, certifications and onboarding tasks
- Knowledge base entries, including who has to acknowledge what
- Widget settings (hours, fields, policies) and the AI-bookings opt-out flag
- Reservation sources for attribution (each AI client gets its own entry per location)
What is shared at workspace level
- Subscription and invoices — billing is one stripe customer for the workspace
- Active modules — entitlements apply to every location in the workspace
- Team directory — a person is invited once, then assigned to locations
- Brand identity defaults (logo, accent color) — locations inherit, can override per widget
Assigning staff to locations
Every team member has one role (admin, manager or employee) and one or more location assignments. Hosts and servers usually map to a single location; managers might be assigned to two or three; admins typically have access to all locations in the workspace.
Switching between locations
The location switcher in the top bar is visible to anyone with access to more than one location. Module pages re-render with the selected location's data; the picker remembers the last selection per device.
AI assistant across locations
The AI assistant scopes tools to the location the user is in. Asking "How many covers tonight?" answers for the active location only. To get a cross-location report, switch to a workspace-level view from the dashboard — only admins see it.
AI booking gateway and locations
The MCP server returns each location as a separate restaurant_id in search results. AI API keys are workspace-wide; the `ai_bookings_enabled` toggle is per location, so a restaurant group can pilot AI bookings at one site before rolling out everywhere.
Rollout pattern
New locations typically follow this order: invite team → import or build the menu → set up the floor plan (sections + tables) → configure widget settings and policies → toggle the public widget on. Most teams ship a new location in a single afternoon.
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| Workspace level | shared | — | — | Billing, modules, team directory, brand defaults. |
| Location level | isolated | — | — | Reservations, tables, menu, shifts, knowledge, widget configuration. |
| Per person / location | assignment | — | — | Role + module access per location. Multiple assignments allowed. |