Who on your team needs a Tablevoice login — and at what permission level. Smaller is better; you can always add later.
Permission levels
Level | Who | What they can do |
Super-admin (multi-venue groups only) | Owner, head of operations, head of reservations | Edit any venue, billing, user management. |
Venue admin | GM, AGM | Edit their venue's configuration. Manage notifications. Add other users at their venue. |
Venue user | Hosts, reservationists, FOH staff | Use the Inbox. Reply to guests. Flag calls. Cannot edit configuration. |
Recommended starter list
For a single venue:
1 Venue admin (GM)
2–3 Venue users (head host + back-up)
1 generic Venue user account for the front-of-house iPad
For a multi-venue group:
1–2 Super-admins (owner + head of ops)
1 Venue admin per venue
2–3 Venue users per venue
Adding a user
Configuration → Team Members → Add User.
Email address (becomes the login).
Role (super-admin / venue admin / venue user).
Venue assignment (for non-super-admins).
Click Send Invite.
The invitee gets an email with a setup link. Once they set their password, they're in.
The shared-iPad account
Most venues create a generic account for the front-of-house iPad — something like iPad-[venue]@yourcompany.com. This way:
Whoever is on shift uses the iPad.
The account doesn't get tied to a person who might leave.
Push notifications go to the device, not a personal phone.
Use a real email you control (so you can do password resets and receive notification emails).
Removing access
Same screen, same flow. Remove. Their login stops working immediately. Past activity remains in the audit log.
Best practices
Don't share logins. Each person, each device that needs access, gets their own.
Use the shared-iPad account only for shared iPads — never as a personal login.
Audit quarterly. Remove ex-employees. Check that super-admins are still the right people.