How to Add a Bot to Discord (Beginner's Guide)
The three things every Discord bot install actually needs — the right authorization, correct role placement, and a real test — explained once.
Quick answer
Adding a bot to Discord means authorizing it through Discord's own OAuth flow from the bot's official invite link, then placing its role correctly relative to the members and roles it needs to manage. Most install problems trace back to one of two things: using a look-alike invite link instead of the official one, or leaving the bot's role too low to actually do what it's configured to do.
What you'll learn
- What actually happens when you click 'Add to Discord'
- Why role placement matters as much as the invite itself
- How to verify an install actually worked, not just assume it did
- Red flags that mean you're not looking at an official invite
- What to check first when a newly added bot doesn't seem to work
Why bot installs go wrong more often than they should
Adding a bot looks like a one-click action, and mostly it is — but two invisible steps happen right after the click that determine whether it actually works: Discord's permission grant, and where the bot's role lands in your server's hierarchy. Skip verifying either one and a bot can look 'added' while being unable to do most of what it's supposed to.
What Discord's install flow actually does
Clicking an official invite link takes you through Discord's own OAuth2 authorization screen — you choose which of your servers to add the bot to (only ones where your account can authorize integrations are listed), review the requested permissions, and approve. Discord then adds the bot as a member and creates a role for it, positioned at the bottom of your role list by default.
The two things that actually matter after clicking invite
Every bot works the same way at a mechanical level — Discord doesn't have a special 'good install' path. What separates a working install from a broken one is what you do in these two steps.
1. Use the official invite link, every time
Do not authorize look-alike applications or invite links copied from unknown servers or messages. An official invite always comes from the bot's own website or a source you specifically trust.
2. Move the bot's role above whatever it needs to manage
Discord prevents a bot from managing a member or role positioned at or above its own highest role — regardless of what permissions it has. A newly added bot's role sits at the bottom by default, which is why role-dependent features (auto roles, moderation, verification) fail immediately after install until you move it.
Do it right the first time
- Open the official Add to Discord link and select the intended server — Discord only lists servers where your account can authorize integrations.
- Review the requested permissions on the authorization screen before approving.
- Return to the server and confirm the bot appears in the member list.
- Open Server Settings → Roles and move the bot's role above any member, verified, or moderation-target roles it will need to manage — while keeping owner and administrator roles above it.
- Run a harmless command (like /help) to confirm it's actually responding before configuring anything further.
Common mistakes
- Authorizing an invite link from an unofficial source — always start from the bot's own website.
- Leaving the bot's role at the bottom of the list and being confused when role-based features don't work.
- Placing the bot's role above your own admin roles — keep privileged human roles above it, not below.
- Assuming the install worked because the bot appears online, without testing an actual command or feature.
Troubleshooting
The bot appears offline right after inviting it
Give it a minute to fully connect, then try a basic command. If it's still offline, check the bot's own status page before assuming the install failed.
A command exists but I can't run it
Confirm application commands are allowed in that channel and that any command-specific permission requirement is met — commands can also take a moment to finish syncing after the bot first joins.
Role-based features aren't working at all
This is almost always role placement. Move the bot's role above whatever it needs to manage, then retry.
Related guides
Discord Bot Permissions, Explained
The three permission layers that actually control what a bot can do — server permissions, channel overwrites, and role hierarchy — and how they interact.
Read guideYour First 10 Minutes With Airwavy
A practical checklist for the first ten minutes after adding Airwavy — role placement, first feature, and validating it actually works.
Read guide