Least-privilege tools for Discord bots
Your bot doesn't need Administrator.
Administrator turns off every safety check in a server. Find the few permissions your bot actually uses, and check any bot before you add it.
The difference
With Administrator
- Every permission, including ones Discord adds in the future
- Ignores every channel restriction a server owner sets
- A leaked token can delete channels, ban members and plant phishing webhooks
- Server owners cannot limit what the bot can reach
With scoped permissions
- Only the permissions your features use
- Owners can keep the bot out of private channels
- A leaked token is limited to what those permissions allow
- Clear, reviewable, and trusted by bot lists
Tools
Permission calculator
Pick exactly what your bot uses. Get the value, an invite link and code for your library.
Invite analyzer
Paste any bot invite to see what it grants and what it could do if compromised.
Permission reference
All 52 permissions with risk levels, values and safer alternatives.
Bot examples
The real permission sets for 10 common bot types, with a reason for each.
Guides
Overwrites, role hierarchy, bitfields and handling missing permissions in code.
README badge
Show server owners your bot asks for less, generated from your real invite.
What real bots need
All 10 examplesModeration bot
Kicks, bans, timeouts and message cleanup.
Music bot
Plays audio in voice channels.
Ticket bot
Private support channels or threads per request.
Reaction & button roles
Members pick their own roles.
Each bar is one permission, coloured by risk. None of these bots request Administrator.
Learn
All guides4 min read
Why your bot should not request Administrator
What Administrator actually grants, why it is dangerous, and what to do instead.
4 min read
How permission values work
Why permissions is a single number, how it is built, and why you must use 64-bit integers.
3 min read
Channel overwrites and why Administrator ignores them
How Discord resolves a bot's effective permissions in a channel.