Team, roles & approvals
Inviting people, exactly what each of the four roles can do, and how the approval queue lets members draft sends that admins review.
Open TeamOne organisation, one owner, and as many people as your plan allows. How your members send depends on your organisation's number mode:
- Personal numbers (the default for new organisations): everyone sends from their own WhatsApp number, and a member's send goes out directly — there is no shared number and no approval queue.
- Shared number: the whole team sends through one organisation number, and a member's send becomes an approval request. This is how a committee member can help without being able to broadcast to the entire association unreviewed.
- Both: each send picks the shared number (members: approval) or the sender's own number (direct).
The owner changes the mode in Settings → Numbers.
Roles#
Four roles. They're fixed — there's no permission matrix to configure, which is deliberate: role-based is easier to reason about than per-user checkboxes, and an org chart nobody understands is how accidents happen.
| Owner | Admin | Member | Viewer | |
|---|---|---|---|---|
| Send on the shared number (Shared number / Both modes) | direct | direct | needs approval | no |
| Send from their own number (Personal numbers / Both modes) | direct | direct | direct | no |
| Change the number mode | yes | no | no | no |
| Create events, campaigns, scheduled sends | yes | yes | needs approval | no |
| Approve or decline requests | yes | yes | no | no |
| Manage groups, categories, caps | yes | yes | no | no |
| Invite people | yes | yes | no | no |
| Promote or demote admins | yes | no | no | no |
| Billing and plan changes | yes | no | no | no |
| Delete the organisation | yes | no | no | no |
Notes:
- The owner is the person who signed up. You can't reassign it by editing a user's role — but the owner can hand it over deliberately, via transfer ownership in Settings. That's the route to use at a board handover.
- Admins can do everything operational — send, approve, manage groups and categories, invite. They can't touch billing or change who else is an admin.
- Members are the interesting case: they can build and draft everything, but on the shared number their actions become requests. See below. In Shared number mode they can't link a personal number at all.
- Viewers read. Useful for a treasurer or a board member who wants visibility with no ability to send.
Inviting people requires an active subscription, and the number of seats depends on your plan — see Plans & billing.
Inviting people#
Open Settings → Team & roles and click Invite team member; the invite goes out by email. The invitee gets a link, sets a password, and lands in your organisation with the role you chose. What they see first depends on the number mode: in Shared number mode (and for viewers) they go straight to My hub; in Personal numbers mode they get a one-step screen to link their own WhatsApp number (they can do it later from Settings → Numbers); in Both they can link one or Skip — use the shared number. They never see the owner's setup wizard. You can change a role later, or remove someone — removing a user immediately revokes their access, including any API tokens they'd created.
The approval queue#
This is the mechanism that makes a shared number safe. It applies in the Shared number and Both number modes; in Personal numbers mode there is no shared number, so nothing goes through it.
When a member sends, schedules, repeats, fires a campaign, or requests an event launch on the shared number, nothing goes to WhatsApp. Instead a pending request is created, and admins see it in Approvals.
An admin reviewing a request sees the actual thing: the message, the audience it resolves to, the schedule. Approve and it proceeds exactly as if an admin had done it. Decline it (optionally with a note) and it doesn't; the member sees Declined and your note on their hub.
A scheduled send whose time has already passed can't be approved as it is. Instead of declining it, you can choose Approve at new time (pick a future time) or Send as soon as possible; the number's quiet hours and the daily caps still apply to the re-timed send.
Details worth knowing:
- Event launch requests can't be double-submitted. Once one is in, the button reads "Pending approval" and stays disabled until it's decided. Compose requests have no such guard, so a member who clicks twice can create two pending requests — approve one and decline the other.
- Members can withdraw. A pending request shows a Withdraw button on the member's hub; withdrawing it means an admin no longer sees it and nothing is sent.
- Admins bypass the queue entirely — an admin's send is a send.
- A member with their own number doesn't need approval for that number. The queue exists to protect the shared one.
- Approval doesn't skip the gates. An approved send still passes caps, cooldown, and quiet hours like any other — unless the member asked for it to send during quiet hours, which the request shows as Skips quiet hours so you see it before approving.
- Some requests can't be approved as they are. If a scheduled send's time has already passed, the event or campaign it refers to is gone, or a send-now or event launch resolves to no groups (or, for a send-now, every group is blocked right now), the request shows why instead of an Approve button. Nothing is sent and it stays pending: decline it with a note so the member can send it again — for example with a new time.
When to use it#
Use approvals whenever more than about three people can send. The failure mode it prevents isn't malice, it's a committee member with good intentions sending the fourth message about the same party to a year group that has already muted you.
If your whole team is trusted and small, make them admins and skip the ceremony.
My hub#
Members get a simplified home, labelled My hub in the sidebar, showing what they can actually do: their drafts, their pending requests, and what's been approved. It exists so a committee member isn't dropped into an operator dashboard full of controls they can't use.
A worked setup: Shared number, many senders.