Guide
Add a Discord bot without admin permissions: the safe way
Almost every guide out there says the same thing: tick Administrator, done. Convenient. And the reason a single stolen bot token can empty a whole server. Here is what you actually hand over, in which order, and what to check afterwards.
No Administrator permission required. Set it up in the web dashboard.
Why this goes wrong
Administrator is not one permission among many; it is the switch that turns every other check off. A bot with that tick reads every private channel, including the one where your team talks about members, and no channel setting stops it. You never notice, because everything simply works. The danger is rarely the person running the bot. It is the token. Whoever gets hold of it inherits exactly that power. There is a quieter second cost as well. While everything is allowed, you never learn which permission a feature really needs, so on the day you tidy up, half of it breaks and nobody can say why. And the audit log shows the same all-powerful role behind every action: a mistake looks like an attack there, and an attack looks like a mistake.
What to decide first
Sort out three things before you click the invite link. First, which jobs is the bot meant to do? Each one maps to a concrete permission: handing out roles, cleaning up messages, timing someone out, writing in threads. What you do not plan to do, you do not need. Second, where does the bot role sit? Its position decides more than any tick. It has to sit above everything the bot should hand out or moderate, and below your lead roles. Third, who is allowed to invite the bot again? Permissions are only set on joining, so a fresh invite is the only route if one is missing later. Our invite asks for 1633027484887: twenty-two individual permissions, and the Administrator bit is not among them. Manage Server, mentioning @everyone and joining voice channels are deliberately absent.
Step by step
- Open the invite link and read the list Discord shows you before you confirm. That list is the actual agreement, not the page that led you there.
- Afterwards drag the bot role in Server Settings under Roles above every role it should hand out or moderate, and keep it below your lead role.
- Walk through the channels it is supposed to work in and look for red minus signs: an exception set on the channel beats the permission from the role.
- Try everything once with a second account in a test channel (hand out a role, set a timeout, post a card) before you rely on it in the main channel.
- Then set the modules up in the dashboard on its-netting.com; the setup assistant tells you there when a chosen role sits above the bot role or when it may not write in the chosen channel.
The mistakes almost everyone makes
The most common mistake is the Administrator tick set just for the setup that nobody ever touches again. The second most common is forgotten hierarchy: a bot with the ban permission whose role sits too far down bans nobody who sits above it. That looks like a defect and is a position in a list. Just as often people miss that an invite only sets permissions at the moment of joining. If a permission is added later, an existing server does not get it retroactively. When a feature reports missing permissions after an update, that is almost always the cause. Add two confusions to that: the member’s permissions and the bot’s are two separate checks, and the permission overview of a role says nothing about what survives inside a single channel.
Frequently asked questions
No. On our side the entire feature set runs on twenty-two individual permissions and the Administrator bit is not set. If a bot still demands it, the fair question is: for which feature exactly? No answer to that is itself the answer.
Because role hierarchy counts on top of it. The bot’s highest role has to sit above the target’s highest role, otherwise Discord refuses. The server owner is never affected, whatever the positions are.
No, kicking is not needed and no settings are lost either way. You either give the missing permission to the bot role by hand, or you run the invite link for the same server once more. Both take about a minute.
Server Settings show the base on its role, the individual channel shows the truth. Open the channel permissions and look up the bot role there: what the channel denies, no generous role brings back. That is exactly why both views are worth a look.
Does a Discord bot need Administrator for everything to work?
No. On our side the entire feature set runs on twenty-two individual permissions and the Administrator bit is not set. If a bot still demands it, the fair question is: for which feature exactly? No answer to that is itself the answer.
Why can the bot not ban a member although the permission is set?
Because role hierarchy counts on top of it. The bot’s highest role has to sit above the target’s highest role, otherwise Discord refuses. The server owner is never affected, whatever the positions are.
The bot is missing a permission but it is already on the server. Do I have to kick it?
No, kicking is not needed and no settings are lost either way. You either give the missing permission to the bot role by hand, or you run the invite link for the same server once more. Both take about a minute.
How do I see which permissions a bot really has?
Server Settings show the base on its role, the individual channel shows the truth. Open the channel permissions and look up the bot role there: what the channel denies, no generous role brings back. That is exactly why both views are worth a look.