Roles and permissions
Who can do what in your workspace, and how to restrict someone to particular conversations.
Roles
Owner — created the workspace. Full access including billing.
Admin — everything an owner can do day to day: settings, team, numbers, automations.
Member — works the inbox and the CRM records attached to conversations.
Permissions
On top of the role, each member has individual switches:
| Permission | Controls |
|---|---|
| Reply | Sending messages and reactions |
| Manage contacts | Editing contacts and custom fields |
| Broadcast | Sending broadcasts |
| Manage automations | Creating and editing automation rules |
| Manage team | Inviting and removing members |
| Manage billing | Plan and payment details |
| Export data | Exporting contacts and data |
These are open by default. A new member can do the everyday work immediately; you switch off only what you want to restrict. This is deliberate — a permission system that requires configuration before anyone can work produces a bad first day for every new hire.
Owners and admins are not affected by these switches.
Restricting someone to certain conversations
You can limit a member to conversations carrying particular labels. Everything else is invisible to them: not in the list, not in search, not in counts.
Typical uses: an agency where each account manager sees one client, a contractor working a single product line, a regional team that shouldn't see another region's customers.
Two things worth knowing:
Their own assigned chats are always visible, whatever the label restriction. A restriction can never hide a member's own work from them.
It applies everywhere, not just the list. Bulk actions, search and counts all respect it, so a restricted member can't reach a conversation through a side door.
Removing someone
Removing a member revokes their access immediately. Their notes, assignments and history stay — the record of who did what remains intact.
Still stuck? Email support and tell us what you were trying to do.