Hedwig can only do what Discord allows in the current channel, and Discord’s role hierarchy always wins.
Minimum useful permissions
For the full feature set, Hedwig generally needs:
- View Channels
- Send Messages
- Send Messages in Threads
- Embed Links
- Attach Files
- Read Message History
- Add Reactions
- Manage Messages
- Manage Channels
- Manage Roles
- Kick Members
- Ban Members
- Moderate Members
- Connect and Speak
The invite link in this project requests a broad set of bot permissions because
Hedwig includes moderation, channel management, role panels, tickets, logging,
and voice playback. If you use a custom invite, grant permissions only for the
features you actually enable.
Some systems need additional permissions, and you can run /permissions to inspect a member’s permissions in context.
Role hierarchy
Move Hedwig’s role above:
- Roles it should assign through autorole, selfrole, or moderation commands.
- Members it should moderate.
- Channels it should manage.
Hedwig cannot manage a role that is equal to or above its own highest role, even if the bot has the Manage Roles permission.
Treat /antinuke reset, /automod reset, /logging reset, and /leveling reset as destructive configuration actions. Review the confirmation shown by Discord before submitting them.
Troubleshooting denied actions
- Check the command’s required Discord permission.
- Check the channel override for Hedwig.
- Check whether Hedwig’s role is above the target member or role.
- Check whether the channel is ignored with
/ignore.
- Retry with the slash command so Discord can show the available options.
If Hedwig cannot send a response at all, grant View Channel and Send
Messages in that channel first. For logging setup, also grant Manage
Channels if using automatic channel creation and Manage Webhooks if
Hedwig should create its logging webhooks. For tickets, it needs to create and
manage private text channels and permission overwrites. 
