Typical errors:
"You don't have permission to use this command" or "The bot doesn't have enough permissions".
Identify the type of error
- User without permissions: Discord or the bot itself rejects the command.
- Bot without permissions: Roody replies that it's missing a permission.
- Hierarchy: Roody can't act on a user whose role is above its own.
- Per-channel permissions: Roody is muted or can't see the channel.
The bot's essential permissions
At a minimum, Roody needs the following permissions at server level:
- View Channels
- Send Messages
- Use Application Commands
- Manage Messages
- Embed Links
- Attach Files
- Read Message History
- Add Reactions
Extra permissions per module
| Module | Permissions needed |
|---|---|
| Moderation | Kick Members, Ban Members, Moderate Members, Manage Roles |
| Tickets | Manage Channels, Manage Roles, Embed Links |
| Welcome / Goodbye | Attach Files (for the image card), Embed Links |
| Levels | Manage Roles (for level rewards) |
| Music | Connect, Speak |
| Logs | View Audit Log |
Quick check
- Open Server Settings → Roles.
- Find Roody's role.
- Check that it has the permissions from the list above.
- Make sure Roody's role sits above the roles it has to manage.
Hierarchy:
Roody can never moderate users with a role equal to or above its own, nor the server owner.
Per-channel permissions
Even if Roody has server-level permissions, a channel can override them. Check:
- Right-click the channel → Edit Channel → Permissions.
- Add Roody's role if it isn't listed.
- Grant at least View Channel and Send Messages.
Fixes by specific error
- Work out which module is failing (from the bot's message).
- Grant the module's permissions (table above).
- If it involves roles or channels, move the bot's role up in the hierarchy.
The command requires a server permission you don't have. For example, /ban requires
Ban Members. Ask an administrator to assign you the right role, or configure the command's
permissions from Server Settings → Integrations → Roody.
The user has a role equal to or above Roody's, or they're the server owner. Move the bot's role above the roles you want to moderate (keeping it below your human staff if you prefer).
For tickets, auto roles and levels, Roody needs Manage Channels and Manage Roles.
These permissions live on the roles page, not the channel's.
Checklist
Re-inviting Roody
If everything above fails, try re-inviting the bot with the official link: your dashboard settings are kept.
You don't need to kick the bot first: Discord reuses its managed role and adds any missing permissions, so
the role's position in the hierarchy is preserved. Even so, check afterwards that it's still
above the roles it has to manage.
Comments
Share your experience or ask anything about this article.
Join the conversation
Sign in to leave comments and take part in the conversation.
Sign in