Invite your team
Add your team so staff can call the next person from a computer or tablet at the counter.
Your team page
The Team page shows everyone two ways — By location (the default — owners, then each location's managers and staff, then anyone not placed yet) and Everyone (a searchable list).
| Thing | What it means |
|---|---|
| The counts up top | People, Managers, Staff and Online. |
| A calendar button on each person | Opens a calendar (not shown on another owner's row). On yourself it opens My calendar. On someone else it opens the Schedule week, filtered to that person. It is greyed out, with the reason on hover — “Not on a location yet, so there is no calendar to show” — for a person who is not placed anywhere yet. |
| A Metrics button on each person | Opens that person's numbers (“Metrics — name”). Not shown on an owner's row. Greyed out for a manager when the owner has switched off “See analytics & reports” for managers: “The owner has turned this off for managers.” |
| A Manage button on each person | Opens their tiles: assign to locations, edit details, resend the invite, change role, reset counter PIN, remove. |
| "Invited" | Shown next to someone who hasn't signed in yet — on their name tile in the default By location view, and in the Everyone list. |
| A manager's list | Shorter than the owner's — only teammates at a location they manage, plus anyone not yet placed anywhere. Merely serving at a location, without managing it, doesn't add its people to the list. That is not a filter they can turn off. |
Adding someone
Invite asks for a short Username they'll sign in with, a role (Staff or Manager), and the places they work — at least one, since it decides which lines they can serve.
| Field or rule | What it does |
|---|---|
| Sign-in email (optional) | Only for people who sign in by email link. Staff sign in with their username and PIN, not a link. |
| The line shown to a manager filling this in | If you're not the owner, the form adds: “Staff sign in with their username and PIN, not a link.” An owner filling in the same form doesn't see that sentence — it's shown based on your role, not the role you're picking for them. |
| Inviting a manager | Owner-only. A manager can add a staff member at a location they run, but the Role list simply doesn't offer Manager to them — and the server refuses it too. |
The username you type isn't the whole username. turnda puts your business's own 4-letter code in front of it automatically — invite "karthik" at Luxe Hair Studio and the actual sign-in username is luxe_karthik.
Roles, PINs & details
Open a person and you get their tiles — assign them to locations, edit their details, resend their invite, change their role, reset their PIN, or remove them.
| You press | What happens | Who can |
|---|---|---|
| Change role | Owner-only. A manager can't promote, demote or change anything about another manager. It takes effect on the person's very next action — they do not have to sign out and back in, and their PIN and sessions are untouched (a role is never stored in their sign-in). They can still SEE a fellow manager on the team list for a location they run — the handle, the sign-in email, whether they're signed in. Seeing is not changing. | Owner |
| Reset counter PIN | Clears their PIN and gives out a fresh one-time code — see PIN sign-in & counters. Nobody, owner included, ever sees somebody's PIN. | Anyone on the team |
| Resend invite | Emails their sign-in link again. If they have no email on file the tile is greyed and says "Add an email first". Pressing it twice on purpose sends two emails; pressing it again because the first seemed to hang does not. | Anyone on the team |
Changing where somebody's sign-in email goes is the owner's, or a manager's only if they run every location that person works at.
What the owner sees. Under the email box the page says “The new address must confirm a link we email to it before the change takes effect — until then the old address keeps working.” After you save it says “We've sent a link to” the new address and that the change happens when it's confirmed, and shows “Waiting for” that address “to confirm” with a Cancel change button. The link works once and runs out at the time the screen shows (24 hours after you ask, by default). Asking again for the same owner replaces the earlier request, and there is a limit on how many requests one owner can make in an hour (5 by default) — past it you are asked to try again later. The owner, the person who asked, or the owner of the business can cancel a waiting request.
What the old address receives. A short email saying a change of sign-in address was asked for, and how to stop it: sign in, open the Team page and cancel the request — or contact support. For the main owner this goes to both the sign-in address and the recovery address; for a co-owner it goes to their own old address. The activity log records that it was asked, cancelled, refused or confirmed (never the address itself).
When the new address confirms. The confirm page needs no sign-in — the link from the new inbox is enough, because the person may have lost the old address. It shows a Confirm button rather than confirming by itself, so an email scanner that opens the link cannot do it for you. On confirming, the sign-in moves, every tablet signed in as that owner with a username and PIN is signed out, any unused PIN reset code stops working, a hand-over the main owner had asked for is cancelled, and both the old and the new address are emailed. The new address must be a real email address that nobody else in turnda signs in with, and it cannot be the business's recovery address. These checks run again at confirm time. If anything has changed since — the person is no longer an owner, or their sign-in is no longer the address the request was made from — the page says “This confirmation link isn't valid any more. Ask for a new one from the Team page.”, and the real reason is in the activity log only. An expired, used or wrong link says the same.
| What the screen says | What it means |
|---|---|
| This teammate hasn't been given a location yet, so only the owner can change where their sign-in email goes. You can still rename them or set their PIN. | Only the owner can move the sign-in email; anyone can still rename them or set their PIN. |
Taking someone off — two different things
| Off one location | Off the business | |
|---|---|---|
| What you do | Set that location to "Not here" in their location list | "Remove from team" |
| What happens | They stay on the team, just not at that place. Removing their last location leaves them on the account, unplaced. | It asks first — they "will lose access to every place they're assigned to", and you're told you can bring them back from Removed people for a while. They're signed out everywhere, taken off any counter they were on, and their sign-in stops working immediately. Their sign-in record at our sign-in provider is deleted in the next nightly clean-up, unless the same address is still used to sign in somewhere else. |
| What it says | Where |
|---|---|
| Only manager of Northside — add another manager there first | The greyed Remove tile a non-owner sees, naming the location. |
| They are the only manager of “Northside”. Give that location another manager first. | What the server says if a non-owner gets past the greyed tile anyway. Add another manager to that location, then remove them. |
| Remove / Make staff here — “Priya is the only manager here. After this nobody manages this location — you run it until you assign someone.” | The owner's confirmation, from the Team page or the location panel. Cancel leaves everything as it was. |
| No manager here — you run this location until you assign one. | The location panel, once its last manager is gone. |
A removed or signed-out person's browser forgets the business. The moment someone is removed, or signs out, the copy of the business's data their browser had saved (Queue, team, activity) is wiped — not merely hidden — so pressing Back or reopening the tab shows them nothing of it.
While someone's invite is still pending, their tile reads "Cancel invite" instead of "Remove from team" — same idea, its own confirmation ("Cancel this invitation?").
- Invited the wrong person, or made a typo? Cancel it — their code stops working the moment you do, so the invite can't be used. Then invite the right person.
- The mistyped username is now spent for good, the same as if you'd removed them after they'd started.
- When somebody is serving a visitor at the moment you remove them, that visitor isn't forgotten — they show up on the dashboard as "being served by nobody", so whoever is on the floor can finish or hold them.
Removed the wrong person? Bring them back
Under the team there is a Removed people list: everyone taken off the team recently, with a Restore button. How long someone stays on it is set by turnda, not by you (thirty days at the moment); the sentence above the list always states the number in force.
| You press | What happens |
|---|---|
| Restore | Puts the person back on the team with their role and their places as they were, and shows you a fresh one-time code, once. Give it to them with their username; they use it to choose a new PIN. A restore never revives a way in. Their old sign-ins stay ended, and the sign-in email and PIN that removal cleared are not brought back — if they use an email to sign in, add it again from their row. |
| Who sees what | Detail |
|---|---|
| The owner | Everyone removed in the window, including managers. |
| A manager | Only plain staff members who worked nowhere outside the locations they manage — the same people they could have removed. Someone who also worked at another location, or a manager, is the owner's to bring back. |
| The "team" switch | If the owner has turned team management off for managers, a manager sees no list and no Restore. |
- Nothing extra is billed — staff are never charged per person. How many staff you can have depends on your package: see Package limits.
- Their old username comes back with them. It was never given to anyone else, so their past work is still under their name.
- A person removed longer ago than the window drops off the list and cannot be brought back from here — invite them again instead (with a new username).
- Pressing Restore twice, or two people pressing it at once, brings them back once; the second press is told they are already back.
- It is written to the activity log with your name.
Somebody who works at several locations
Each person's row lists every location with their role there — "Northside · Manager · Riverside · Staff". Somebody with no location yet shows "Not assigned to a location yet".
What they see — only the locations they're actually on. They move between them with a location switcher that lives on the page itself (the Dashboard, Locations and so on each carry their own — there's no single picker in the top bar any more).
- The switcher lists each location's lines with a live waiting count — picking a line switches the location too.
- It remembers where you were next time in that browser, and is deliberately forgotten when you sign out or switch accounts on that device.
- On the Queue, a staff member doesn't get a picker at all — they see their line's name as plain text, because they serve the one line.
Searching, cancelling, removing
| What happens | What it means |
|---|---|
| Find someone | Use the search box on the team page. |
| A teammate was added but not placed at a location | The page tells you and offers to retry. |
| Cancel an invite | Withdraw a sign-in link you sent so it stops working (Manage). |
| Remove someone with upcoming appointments or visitors waiting | You are asked whether to move them to the first available person, to a person you choose, or leave them as they are. |
| They were the cover for someone's leave | Removal warns you that leave will then show No cover. |
| Adding someone to a place with rosters | Choose the weekly roster they follow, works-whenever-we-are-open, or decide later. |