Invite checker for Discord bots
Paste a bot's invite link and see every permission it asks for, in plain English, with a risk level and an explanation. Or tick the permissions your own bot needs and get the number and the invite link.
Build a permission set
Tick what your bot needs. The number and invite link below update instantly. The presets show what typical bots get by with.
Number and invite link
The application ID from the Developer Portal. Without it there is no invite link to build.
https://discord.com/oauth2/authorize?client_id=&scope=bot+applications.commands&permissions=0Reading the result
Every permission carries one of three levels. Critical exists exactly once: Administrator overrides every other restriction, including the ones set per channel. High marks permissions that can do lasting damage to a server: roles, channels, bans, webhooks, deleting other people’s messages. Everything else is normal: the bot can post, read, react or sit in voice, but it cannot break anything.
The level is not a verdict on the bot’s intentions. It measures how bad things get if the bot has a bug or its token leaks. A moderation bot rated “high” is business as usual; a music bot rated “high” owes you an explanation.
What a bot really needs
For developers: ask for the floor, not the comfort zone. A bot that only responds to slash commands frequently needs no permissions at all, because Discord always delivers the reply to a command. A bot that posts on its own needs Send Messages and, almost always, Embed Links; otherwise its replies arrive as empty boxes.
Administrator is the most common shortcut, and the most common reason a server owner closes the invite tab without clicking. The presets in the calculator show what typical bot types get by with. If your bot is missing a permission, tell the user at the moment it fails: “I need Manage Messages in #general” beats a permission list that asks for everything just in case.
Before you invite a bot
For server owners: go down the list, and for every permission marked “high”, ask which feature of the bot needs it. A welcome bot does not need bans; a levelling bot does not need webhooks. If the list does not match the description, ask in the support server; an honest developer can explain it.
You can untick permissions in Discord’s dialog before confirming, and change them later in the bot’s role. The one thing you cannot rein in afterwards is Administrator: it ignores every channel restriction. When a bot demands it without saying why, this is the one place where “no thanks” is the right answer.
Frequently asked questions
- What does permissions=8 mean in an invite link?
- The number after “permissions=” is a bit field. Every permission has a fixed value, and the link carries the sum of everything the bot asks for. 8 is a single bit (Administrator), so a link with 8 asks for everything at once. Paste it above and the checker spells out what that includes.
- Is Administrator dangerous for a bot?
- It is the most powerful permission Discord has: the bot may do anything, in any channel, regardless of channel-level restrictions. Whether a bot abuses that is up to the developer; whether a bug in the bot causes damage is then up to the bug alone. No bot needs Administrator to function. Ask the developer which individual permissions the bot really uses and invite it with those.
- What is the difference between a scope and a permission?
- A scope describes what the application receives when you authorise it: “bot” adds it as a member, “applications.commands” registers its slash commands, “identify” tells it who you are. Permissions describe what the bot member may then do inside the server: delete messages, assign roles, ban people. Scopes belong to the application; permissions belong to its role in your server.
- Can I change the permissions after inviting the bot?
- Yes. When a bot joins, Discord creates a role for it carrying exactly the requested permissions. You can edit that role in the server settings like any other and take individual permissions away. You can also override permissions per channel, except for Administrator, which ignores every channel restriction.
- Why does the link show zero permissions?
- Because the developer did not request any, or set “permissions=0”. That is not a mistake: a bot that only replies to slash commands genuinely needs no permissions, since Discord always delivers a reply to a command. Only a bot that wants to post, read or moderate on its own initiative needs an entry here.
- Where do the number and the invite link the calculator produces come from?
- Every ticked permission contributes its bit value; the sum is the permissions integer. The invite link places that number, the bot’s client ID, and the scopes “bot” and “applications.commands” into Discord’s authorisation URL. It is the exact format the Developer Portal generates, except here you can see what every number stands for.
Your bot deserves a listing
On Topbot.gg every visitor sees exactly this permission list on the bot's page, reviewed by a person who invited the bot. Listing takes ten minutes and is free.