Docs · Getting started
Bot permissions
The invite link asks for the smallest set of permissions Tournabot can actually work with. Nothing here is optional-but-nice: each one backs a feature you will use on your first night.
Why setup can stall
If the bot is in your server but missing one of these, setup will say so rather than half-work. Re-invite with the link from the wizard — it always requests the full set — and the check clears on its own.
| Permission | What it is for |
|---|---|
| Manage Channels | Creates the scrim category, registration channel, and slotlist channel when you press the one-button setup on the website. |
| Add Reactions | Powers reaction-shaped community surfaces such as polls and reaction roles. |
| View Audit Log | Finds who added the bot so the right person gets the install follow-up. It does not read your message history. |
| View Channel | Sees the channels it must post into — registration panels, slotlists, and boards. |
| Send Messages | Posts panels, welcome messages, room cards, and scoreboards into those channels. |
| Embed Links | Sends the embed cards organisers and players actually read — instructions, slotlists, results. |
| Read Message History | Checks whether a welcome or panel is already there so setup does not double-post. |
| Move Members | Moves people between voice lobbies when your night needs seat moves. |
| Manage Roles | Creates or adopts the Community role and keeps the bot’s managed role above roles it assigns. |
For admins: the invite bitfield
Combined, those permissions are the bitfield 285297872. If you build an invite link by hand, that is the value to use.
- Manage Channels · bit 16
- Add Reactions · bit 64
- View Audit Log · bit 128
- View Channel · bit 1024
- Send Messages · bit 2048
- Embed Links · bit 16384
- Read Message History · bit 65536
- Move Members · bit 16777216
- Manage Roles · bit 268435456
One server, one organisation
A Discord server belongs to exactly one Tournabot organisation. If a server is already bound elsewhere, binding it again is refused — that is deliberate, and it is what stops another organisation claiming a server you run.