Roles & permissions
This is the full picture of who can open what.
| What the screen says | What it means |
|---|---|
| You don't have access to this page | Shown for a page outside your role, with a sentence naming who can open it — so you can tell that apart from a genuine broken link. |
The roles at a glance
turnda has three roles — plus one earned hat.
| Role | What they can do |
|---|---|
| Owner | Full access everywhere, never scope-limited — billing, brand, every location, every page below. |
| Manager | An account-level role that runs locations day-to-day. Managers can do everything at the locations they run, unless the owner switches a specific capability off. |
| Staff | Serves people at the places they're assigned — the queue, bookings, chat, and their own numbers. |
| Location-manager | Not a fourth role — a staff-role person made manager of one or more locations. See below. |
A location-manager gets the location-scoped manager pages (Dashboard, Locations, Visitor pages, Displays, Analytics, Reports, Activity) for their locations only — never the account-wide pages like the account Team page, the message channels or Settings.
They still run their own branch's team, though — from the Locations hub they can see the roster, invite staff, change roles and remove people at the locations they manage. That lives inside Locations, not on the account-wide Team page.
- Maya now sees a dashboard and the Locations hub showing Northside only, and can tune its lines, design its visitor pages, read its activity, and manage Northside's own team from there.
- At Riverside, where she just serves, she's plain staff — she still can't open the account-wide Team page, Billing or Settings, because those belong to the account, not a location.
What everyone shares
Serving is the shared core.
- Everyone — including staff — gets the Queue (call, serve, hold, transfer, add a walk-in), Bookings, Team chat and My Metrics, at the places they're assigned.
- Staff don't get a dashboard — it's a manager's overview — so their home page is the Queue.
Page by page: the matrix
Every page in the app, and who can open it. "At their locations" means the page appears, scoped to just the locations that person manages.
This leaves out two pages that sit on every role's own account menu regardless — My sign-in and Support — noted below the table.
| Owner | Manager account role | Location-manager staff who runs ≥1 location | Staff | |
|---|---|---|---|---|
| Dashboard | ✓ | ✓ | At their locations | no — taken to the Queue |
| Queue | ✓ | ✓ | ✓ | ✓ |
| Bookings | ✓ | ✓ | ✓ | ✓ |
| Locations | ✓ | ✓ | At their locations | — |
| Journeys | ✓ | — | — | — |
| Visitor pages | ✓ | ✓ | At their locations | — |
| Displays (board designer) | ✓ | ✓ | At their locations | — |
| Devices (paired screens) | ✓ | ✓ | — | — |
| WhatsApp & Email pages | ✓ | ✓ | — | — |
| Team (account-wide page) | ✓ | ✓ | — | — |
| Team chat | ✓ | ✓ | ✓ | ✓ |
| My Metrics | ✓ | ✓ | ✓ | ✓ |
| My sign-in | ✓ | ✓ | ✓ | ✓ |
| Support | ✓ | ✓ | ✓ | ✓ |
| Get started (setup wizard) | ✓ | — | — | — |
| Analytics & Reports | ✓ | ✓ | At their locations | — |
| Activity | ✓ | ✓ | At their locations | — |
| Settings | ✓ | ✓ | — | — |
| Queue defaults (priority tiers, transfers, weekly email) | ✓ | — | — | — |
| Billing | ✓ | — | — | — |
| Brand | ✓ | — | — | — |
| Manager permissions | ✓ | — | — | — |
| Profile / Data & privacy | ✓ | ✓ | ✓ | ✓ |
| Close account | ✓ | — | — | — |
Notes the table can't fit
| Thing | Detail |
|---|---|
| Team (account-wide page) — location-manager | No — but runs their own branch's team from Locations. |
| Owner-only levers beyond the pages above | Creating a line, creating or deleting a location, authoring journeys, transferring a visitor to another location, minting or demoting a manager, and the get-started wizard. |
| Managers do everything at their locations by default | The owner can revoke nine specific capabilities (messaging, team, branding, renaming, deleting lines, journey mode, TV boards/displays, activity, analytics) from Manager permissions. Routine line settings are never gated. |
| Queue defaults, including priority tiers | Owner-only, full stop — there is no manager capability for it at all, for either kind of manager. An older version of this table listed it as a manager capability the owner could revoke; that capability was removed from the product, so the whole page is owner-only now. |
| Activity for location-managers | Shows only their locations' entries — never account-wide events. |
| Devices — the one menu-only limit | A location-manager who somehow reached the Devices screens endpoints would be let through by the server (it uses the same location check as the rest of Locations) — they simply have no menu item or link to get there. Everywhere else in this table, "no" is checked by the server itself. |
If you're a manager or staff and see the banner with no button
| Case | What to do |
|---|---|
| No fix button on the banner | That's expected — tell the owner, you can't clear it yourself. |
| One branch just stops taking new visitors, no banner for anyone | That branch's subscription has already ended. If a branch has gone quiet and nothing on screen explains it, the owner should check Billing. |