Bot permissions

The most common cause of "the bot doesn't do anything" is missing Discord permissions.

❓ Why this happens

The YAWBDB invite link asks Discord for the permissions the bot needs. Discord's screen lets you untick any of them, and a server admin can change the bot's role later, so the bot can still end up without something it needs.

The invite asks for these 17 permissions: View Channels, Send Messages, Embed Links, Attach Files, Read Message History, Add Reactions, Manage Messages, Manage Roles, Manage Channels, Kick Members, Ban Members, Timeout Members, View Audit Log, Manage Server, Move Members, Connect and Speak. It never asks for Administrator. Discord only offers the invite for servers where your account has Manage Server.

🛎️ The warning on your server card

The panel asks the bot which permissions it holds on each of your servers. When one is missing, the server card shows a warning with the list. Team members who can moderate the server, and the team owner, see it. The one-click re-invite below needs Manage Server on that Discord server.

• Fix in Discord opens Discord's screen for that server with the permissions already ticked: confirm, then come back to the panel.
• Check again asks the bot again, for example after you changed its role yourself.
• "The bot is not on this server. Add it again.": the bot was removed from the server; Fix in Discord adds it back.
• "The bot's permissions could not be checked right now. Try again in a moment.": the bot could not answer just now. This says nothing about your permissions.

The check reads the bot's role on the whole server. A channel override can still deny something in one channel: see step 5 below.

🚨 Symptoms

• Slash commands respond with errors, or the bot stays silent
• Automod doesn't delete messages
• Moderation actions (ban, mute, kick) fail
• Reports or tickets don't create threads
• The bot can't join a voice channel for recording

🔧 How to fix

1. Open Server Settings → Roles in Discord.
2. Find the role created for YAWBDB.
3. Grant the permissions needed by your enabled features — the full list is in Feature permissions.
4. Make sure the YAWBDB role is above the members and roles it needs to manage.
5. Check the specific channel: a channel permission override can deny what the role allows. Compare with a channel where the bot works.

🆘 Still stuck?

• Kick the bot and re-invite it, then re-grant permissions.
• Test in a brand-new channel with no overrides.
• If only one feature misbehaves while others work, it is almost always that feature's extra permission (e.g. Manage Roles for Leveling rewards) — see Feature permissions.