Bot permissions
See which Discord permissions the bot asks for, why, and who in your guild can change bot settings.
This page lists the Discord permissions the Guild Pro bot requests and what each is for. It is for admins and server owners deciding which install to use.
The two installs
| Permission | Full install (default) | Minimal install |
|---|---|---|
| View Channels | Yes | Yes |
| Send Messages | Yes | Yes |
| Embed Links | Yes | Yes |
| Attach Files | Yes | Yes |
| Read Message History | Yes | Yes |
| Manage Channels | Yes | No |
| Manage Roles | Yes | No |
| Manage Events | Yes | No |
| Create Events | Yes | No |
The bot never asks for Administrator, and never for kick or ban.
- The five shared permissions let the bot post signup sheets, rosters and recaps, attach pictures, and edit its own posts.
- Manage Roles is what lets role pickers hand out roles. See Reaction roles.
- Manage Channels, Manage Events and Create Events let the bot create and organise channels and events for you, including through a connected assistant. See MCP.
Check or upgrade the install
Admins can see which install a server has on the MCP page (/g/your-guild/mcp, where “your-guild” is your guild’s address), under Discord management. Each server reads full management or posting only.
To move a server from posting only to full management:
- Open the MCP page.
- Next to the server, select Upgrade permissions.
- Approve Discord’s consent screen. It shows exactly what changes.
Guild Pro records the tier of your most recent install. If you run the minimal install on a server that had the full one, it is treated as posting only.
Permissions in each channel
Server-wide permissions are not enough if a channel overrides them. To post in a channel the bot needs all four of:
- View Channel
- Send Messages
- Embed Links
- Attach Files
In channel pickers on the site, a channel the bot cannot fully post in is marked with a warning sign. The Bot page also lists broken routes under Needs attention, naming the missing permissions. Nothing posts to a channel the bot cannot write in.
To hand out a role, the bot’s own role must also sit above that role in Server Settings → Roles in Discord.
Who can change bot settings
Authority comes from your role in Guild Pro, not from Discord permissions.
| Action | Role needed |
|---|---|
| View the Bot, Welcome, Reaction roles and Automations pages | Officer |
| Change channel routes, welcome messages, role pickers, automations | Admin |
Post a signup sheet with /raid, or a roster call with /rostercall | Officer |
| Open the MCP page and decide proposals | Admin |
Admins assign officers on the Members & alts page. See Ranks and admins.
Destructive changes need approval
When a connected assistant asks to delete something in your Discord, nothing is deleted. The request is filed as a proposal. An admin sees it on the MCP page under Waiting on you and selects Approve or Deny. Decided proposals are listed under Decided with the result.
Related
Still stuck? Ask in the Discord.