Team roles and permissions
Invite teammates, assign roles and limit which bots they can access.
Roles and permissions
| Role | What it can do | Restrictions |
|---|---|---|
| Owner | All workspace, content, support, integration, token and team operations. | Responsible for billing and ownership actions. |
| Admin | Manage content, integrations, tokens, support and permitted team invitations/removals. | Cannot manage billing, workspace ownership or admin/owner roles. |
| Human Agent | Handle tickets/conversations and manage leads. | Cannot configure bots, integrations, tokens or billing. |
| Member | Read accessible workspace/bot information. | No write capabilities. |
Invite a teammate
- Select the workspace and open Team.
- Enter the teammate’s email and choose a permitted role.
- Send the invitation. The recipient signs in using the invited email and accepts it.
- Review the new member and assign the bots they should access.
- Have the teammate confirm that they can open the intended bot and perform the expected task.
Change or remove access
The owner can change roles and manage administrators. Use bot assignments for staff who should work on only part of your bot portfolio. Removing a teammate removes membership in this workspace; it does not delete their personal account or your bots.
- A seat-limit error means the workspace needs capacity before the invitation can complete.
- If an invitation cannot be accepted, confirm the email, invitation status and workspace.
- A disabled control can reflect your role rather than a problem with the feature.
- Review API tokens and MCP connections separately when rotating access for an integration.