Two levels exist in Tablevoice. Knowing which is which prevents you from accidentally changing one venue when you meant to change another, or fragmenting your brand voice unintentionally.
Org-level — the umbrella
Settings that span the whole group:
Setting | Why it lives at org level |
Billing | One Stripe account by default. Or several if you've asked for separate invoices per venue. |
Super-admin user accounts | Owners and ops leads who need every-venue access. |
Brand-wide playbook templates | The default late-arrival message, complaint-handling script, language mode — starting point for each venue. |
Cross-venue analytics | The Compare Locations dashboard. |
Venue-level — each restaurant
Settings that vary per venue:
Setting | Why it lives at venue level |
Hours, menu, address, parking | Different per venue. |
Voice & language | Can vary — a French-Canadian voice for the Montréal location, an American voice for Toronto. |
Phone routing | Each venue has its own number, its own forwarding rule. |
OpenTable / Resy connection | Each venue has its own. |
Notification routing | Different team per venue. |
Per-venue overrides of brand templates | When you want the late-arrival message to read differently at one venue. |
How they interact
An org-level template defines the default for any venue that hasn't overridden it.
A venue-level setting overrides the org default for that venue only.
Removing a venue-level override falls back to the org default automatically.
In practice: define brand voice and tone at the org level. Define hours, menu, and phone at the venue level. Override at the venue level only when you have a strong reason.
Switching between levels in the app
To edit org-level
Sidebar dropdown set to "Organization" or your org name.
Settings shown are org-wide.
To edit venue-level
Sidebar dropdown set to a specific venue.
Settings shown apply only to that venue.
Always check the dropdown before saving. It's the most common error: you mean to edit Toronto's Hours, but the dropdown is set to Montréal. We've seen seasoned ops leads do this. Glance at the venue name above your edits.
Inheritance pitfalls
"Why is my new venue using the old playbook copy?" — it's inheriting from org-level. Update at org-level if you want all venues to change; venue-level if just this one.
"Why didn't my org-level change apply to existing venues?" — it does, unless those venues had a venue-level override. Check.
"I added a new venue. Why is it missing settings?" — venue-level fields like hours and menu are required per venue; org-level templates supply the rest. New venues need the venue-level fields filled.
When to add to org-level vs venue-level
For a new policy or template:
Will it apply to every venue? → org-level.
Is it specific to one venue? → venue-level.
Is it specific to most venues? → org-level + venue-level overrides on the exceptions.