ReactionBot Documentation
Role Permissions
Learn which Discord permissions ReactionBot needs to assign and remove roles successfully.
ReactionBot relies on Discord's permission system to assign and remove roles. Even if your role mappings are configured correctly, Discord may block role changes when permissions or role hierarchy are incorrect.
Manage Roles
ReactionBot requires the Manage Roles permission before it can assign or remove any Discord role.
Without this permission, members can react successfully but no role changes will occur.
Role Hierarchy
Discord only allows a bot to manage roles positioned below its own highest role.
ReactionBot's role must always be higher than every role it needs to assign or remove.
Managed Roles
Some Discord roles are managed by integrations or applications.
Managed roles cannot be assigned or removed by ReactionBot and must be controlled by the integration that created them.
Channel Permissions
ReactionBot must also be able to view the channel containing the reaction role message.
If the bot cannot access the message, it cannot monitor reactions or assign roles.
Testing Your Setup
After configuring a reaction role, test it using a normal member account.
React to the configured message and verify that the role is assigned immediately.
If it isn't, check role hierarchy before changing anything else.
Common Permission Problems
ReactionBot's role is below the role being assigned.
Manage Roles permission is missing.
The selected role is managed by another Discord integration.
ReactionBot cannot view the configured channel.
Using /diagnose
If roles aren't being assigned, run /diagnose to identify missing permissions and common configuration issues.
The diagnostic report is usually the quickest way to identify setup problems.
Best Practices
Place the ReactionBot role near the top of your server's role list.
Create a dedicated role for ReactionBot rather than reusing another bot role.
Review permissions after making major changes to your server structure.