Discord Bot Permissions, Explained

Discord's permission system is genuinely three separate checks stacked together, and a feature only works if all three line up. Most 'the bot isn't working' reports are actually one of these three layers silently blocking something, not a bug in the bot itself — which is why methodically checking each layer, rather than guessing, resolves most of them quickly.

These apply to every bot on Discord, not something specific to any one of them.

• Server permissions come from the bot's assigned role(s) — the baseline set of things it's allowed to do anywhere in the server.
• Channel overwrites can allow or deny specific permissions for a specific category or channel, overriding the server-wide default in either direction.
• Role hierarchy limits which members and roles a bot can manage, independent of permission bits — a bot can have Administrator and still be unable to manage a member or role positioned above its own highest role.

Grant permissions according to which features you actually enable — not everything up front.

• View Channel, Send Messages, Embed Links, and Read Message History for most relevant text flows.
• Connect and Speak for music; Move Members for join-to-create or voice moderation.
• Manage Roles for verification and reaction roles.
• Manage Channels for tickets, join-to-create, and channel locks.
• Ban, Kick, Moderate, Mute, or Deafen Members only for the matching moderation actions — and beyond Discord permissions, some commands also require an enabled dashboard feature, an Airwavy staff or DJ role, Premium access, or another eligibility rule shown in its reference entry.

1. Decide which features you're actually enabling before granting permissions — don't grant everything up front.
2. Check each enabled feature's command reference entry for its declared bot permission requirement.
3. Grant only those specific permissions, rather than a blanket Administrator role.
4. Move the bot's role above whatever member roles or target roles it needs to manage.
5. Test each feature with a normal, non-administrator account — an admin account skips exactly the checks you're trying to validate.

• Granting Administrator as a shortcut instead of the specific permissions a feature needs.
• Assuming Administrator bypasses role hierarchy — it doesn't; a bot still can't manage a role or member above its own.
• Checking only server-level permissions and missing a channel-level overwrite that denies access.
• Not distinguishing a Discord permission problem from an Airwavy-specific access gate (feature not enabled, missing Premium, missing staff role).