A good Discord bot handles moderation, roles, music, tickets and game-server status so you do not have to. Adding one is quick, but there is one permission gotcha that trips up almost everyone. Here is the clean way to do it.
Step 1: Invite the bot
Most bots have a website with an Invite or Add to Server button that opens Discord's authorization screen.
- Choose the server to add the bot to (you need Manage Server permission on it).
- Review the permissions the bot is requesting.
- Approve, and the bot appears in your member list.
If you run your own bot, you generate this invite link in the Discord Developer Portal under your application's OAuth2 settings, selecting the bot scope and the permissions it needs.
Step 2: Fix the role order (the gotcha)
This is the step people miss. A bot can only manage roles and members that sit below its own role in the role list. If the bot's role is below the roles it should assign or moderate, its commands silently fail.
In Server Settings, Roles, drag the bot's role above the roles it needs to manage. Without this, "assign role" and "kick or ban" commands do nothing, and you will think the bot is broken.
Step 3: Set its permissions
Give the bot only what it needs. For a moderation bot that usually means Manage Roles, Kick, Ban, Manage Messages and Read/Send Messages. Avoid handing every bot Administrator · it is convenient but risky if the bot is ever compromised.
Step 4: Configure it
Most bots are set up with slash commands (type /) or a web dashboard. Choose your prefix or use slash commands, pick the channels it works in, and enable the modules you want: welcome messages, auto-roles, logging, tickets.
Common problems
- Commands do nothing: almost always the role-order gotcha from Step 2, or a missing permission.
- Bot appears offline: it may be down, or for a self-hosted bot, the process is not running.
- Slash commands not showing: they can take a few minutes to register after the bot joins. Re-invite with the
applications.commandsscope if they never appear.
FAQ
Why are my bot's commands not working?
The most common cause is role order: the bot's role must be above the roles it manages. After that, check it has the specific permission for the command.
Should I give a bot Administrator permission?
Avoid it unless you fully trust the bot. Grant only the specific permissions it needs, so a compromised bot cannot take over your server.
Can I run my own custom Discord bot?
Yes. Create an application in the Discord Developer Portal, host the bot on a VPS so it stays online 24/7, and invite it with the scopes it needs.
Want to host your own bot 24/7? A small Vastrox VPS keeps it online around the clock.