A bot, up close
An account with a token, and three doors that stay shut
release-bot
Bot · not a billable seat
- System consoleRefused in words
- Minting a tokenIncluding its own
- Encrypted roomsNever a member
Bot or personal token
Who the automation speaks as
| Bot account | Personal access token | |
|---|---|---|
| Created by | An administrator, from the console | Any member, for themselves |
| Speaks as | Its own identity, with a bot badge | You, with your roles |
| When the author leaves | Keeps working | Goes with them |
| Expiry and storage | Mandatory expiry, stored as a hash | Mandatory expiry, stored as a hash |
In a room
What can a bot do?
Whatever the rooms it belongs to allow, and no more. There is no separate bot permission model: give the bot a role in a channel and the ordinary rules decide what it may post, react to or read. Its messages carry a real author, so search, audit and export treat them normally.
What it does not do
The edges, before you find them
FAQ
Bot accounts: questions
- Yes. An administrator creates a bot in the console and mints an access token for it. The bot is a real account and a real channel member, so the room’s ordinary permission model governs what it can do.
- No. A billable seat is an active member of the organisation, which excludes bots, guests and deactivated accounts.
- No. Bots can only be members of managed rooms. An end-to-end encrypted room holds no server-side key, and adding a bot to one would require adding a visible member to the encryption group, which is not built.
Bring your team over this afternoon
Free for up to 10 people, with encrypted direct messages and video calls. No payment card, no time limit, no server to run.
For businesses and organisations only — not available to consumers.