Skip to content

Bot Permissions

Control who can view, edit, and manage each bot with per-bot roles — owner, admin, editor, and viewer — granted from the bot's General Settings.

On this page

Organization roles decide who runs your workspace; bot permissions decide who can touch each individual bot. This article covers the four per-bot roles, the difference between explicit grants and automatic access, and how to grant or revoke access.

The four bot roles

When you grant someone access to a bot, you pick one of four roles:

Role

Access level

Viewer

Read-only — can open the bot and see its dashboard, activity, and conversations

Editor

Can edit — viewer access plus working with the bot's content day to day

Admin

Full access — everything above, plus changing bot settings and managing this permissions list

Owner

Full control — everything above, including deleting the bot

Two of these are assigned automatically:

  • Owner goes to whoever created the bot. The owner entry can't be removed from the permissions list.
  • Admin goes to every organization admin, on every bot in the organization (see below).

In the current release, changing a bot's settings, managing its permissions, and deleting it all require the admin or owner role (or organization-admin status). Viewer and editor grants are the right choice for teammates who monitor conversations and work with content but shouldn't reconfigure the bot.

Explicit grants vs. organization access

The permissions list distinguishes two sources of access:

  • Explicit — someone granted this person access to this specific bot, with a chosen role. This is how organization members get access to anything.
  • Organization — automatic access that comes with being an organization admin. Org admins receive admin-level access on every bot without anyone granting it.

On the bot's permissions screen these appear as two lists: Organization admins (automatic access) and People with access. Automatic entries can't be revoked from the bot — the list notes "Cannot revoke — change org role". To remove an org admin's access, change their organization role on the Users page instead.

Granting access

  1. Open the bot and go to its Settings tab (General Settings).
  2. Scroll to the Permissions section — "Manage who can access and configure this bot."
  3. Click Grant Access.
  4. In the Grant Bot Access dialog, use Select User to pick an organization member. Only members without access are listed — org admins don't appear because they already have automatic access.
  5. Choose a Bot Role: Viewer (read-only), Editor (can edit), Admin (full access), or Owner (full control).
  6. Click Grant Access.

The person can use the bot immediately — no acceptance step needed, since they're already in the organization.

Revoking access

In the People with access list, click the X next to a person's entry and confirm. Their access to that bot ends immediately.

Two entries can't be revoked this way:

  • The owner — the list shows "Owner — can't be removed."
  • Organization admins — their access comes from their org role, not from this list.

Common questions

I granted someone editor access but they can't change the bot's settings

That's expected. Settings changes and permission management require the admin or owner role. Re-grant them as admin if they need it.

Does a viewer or editor use up anything on my plan?

No. Permissions are free and unlimited on every plan — only interactions and bot count are metered.

Someone left the company — is removing their bot access enough?

Remove them from the organization on the Users page. That ends all their access at once; per-bot revocation alone still leaves them in the organization.

Can I transfer ownership of a bot?

Not from the dashboard today. Grant the new person admin access — it covers everything except deletion — or contact support for a transfer.

Was this article helpful?