Bot permissions explained
Each bot joins your server with Administrator, so every feature works. The table below lists what each bot uses. Channel overwrites can remove a permission in one channel, so the dashboard checks the bots' effective permissions where it matters and names anything missing.
Contents
Who needs what#
| Bot | Permissions | Why |
|---|---|---|
| BotStacked | View Channel, Send Messages, Read Message History, Embed Links, Connect, Speak, Manage Channels, Manage Roles, Move Members, Change Nickname, Manage Messages, Timeout Members | Post panels and replies, create LFG channels and voice rooms and manage who can use them, move members into their rooms, set its name in your server, and delete a message or time a member out when a moderator asks for it from a confirmed Moderation case. |
| Restify | View Channel, Send Messages, Read Message History, Embed Links, Connect, Speak | Join voice rooms and play. |
Where each feature needs them#
- Music: text access for BotStacked in the panel channel; Connect and Speak for Restify in voice rooms.
- LFG: Manage Channels and Manage Roles in the group category.
- Voice rooms: Manage Channels, Move Members and Manage Roles in the lobby and room category.
- BotStacked's name: Change Nickname.
Privileged intents#
BotStacked reads messages for its ! commands and uses the member list, so it has Discord's Message Content and Server Members intents. Restify uses the same two, to find your voice room.
Why the bots join with Administrator#
With Administrator, no role order or channel overwrite can stop a bot from doing its job, so setup is quicker and there is less to fix later.
The trade-off: Administrator lets a bot do anything in your server. Every feature works with it, and the dashboard treats a bot with Administrator as having every permission.