# Discord bot permissions worth questioning

> Which permissions a Discord bot genuinely needs for common jobs, and which requests deserve a second look before you approve the invite.

- Canonical: https://discordbots.blog/blog/discord-bot-permissions-to-question
- Published: 2026-08-31
- Author: The Field Guide desk
- Competitor facts checked: 2026-09-01
- Sources:
  - Discord developer docs — Permissions (https://docs.discord.com/developers/topics/permissions) — checked 2026-09-01
  - Discord developer docs — OAuth2 (https://docs.discord.com/developers/topics/oauth2) — checked 2026-09-01
- Publication: The Field Guide, an independent site not affiliated with Discord Inc.

---
A bot's permission request is the clearest statement it makes about itself, and it is made before
you have committed to anything.

## What common jobs actually need

| Job | Permissions that cover it |
| --- | ------------------------- |
| Post announcements | View Channel, Send Messages, Embed Links |
| Reaction roles | Manage Roles, Add Reactions, Read Message History |
| Tickets | Manage Channels, Send Messages, Manage Messages |
| Logging | View Audit Log, View Channel, Send Messages |
| Moderation | Kick, Ban, Moderate Members, Manage Messages |
| Leveling | View Channel, Send Messages, Manage Roles (for rewards) |

None of these is Administrator.

## The three to question

**Administrator.** It grants everything, cannot be narrowed, and bypasses channel overwrites
entirely — a bot with Administrator can read every private channel in the server including staff
ones. It is also forward-inheriting: permissions Discord introduces later are granted
automatically, with no new consent step.

**Manage Server.** This covers the invite list, integrations, the server's vanity URL and its
widget. A bot needing it for one narrow feature — reading invites for an invite-tracking system —
is receiving the ability to change server-level settings as a side effect.

**Manage Roles.** Frequently requested for auto-roles or level rewards. What it actually grants is
the ability to create, delete and edit the permissions of every role positioned below the bot. That
is the correct permission for the job, and it is worth knowing that the job and the grant are not
the same size.

## Permissions are rarely the fix

The most common support ticket in any moderation setup is a bot that cannot ban someone despite
holding Ban Members. Adding permissions does not help, because the block is **role position**: a
bot can only act on members whose highest role sits below its own, and Administrator does not
exempt it.

Before granting anything further, check where the bot's role sits in the list. In a server that has
added roles since installing the bot — which is every server — the bot has usually drifted
downward without anyone touching a permission.

## Trimming after the fact

Permissions granted at install can be edited afterwards on the bot's own role, with no reinstall
and no downtime. If a bot was installed with Administrator during setup and everything now works,
removing Administrator and granting the specific permissions it uses is a short job with a real
security return. The failure mode is loud and immediate — a command stops working — which makes it
safe to do incrementally.