ReactionBot Documentation
Role Requirements
Control who can receive roles by requiring existing roles or automatically removing conflicting roles.
Role Requirements allow you to control who can receive a reaction role. You can require members to already have a specific role before receiving another, or automatically remove conflicting roles when a new one is assigned.
Required Role
The Required Role option prevents members from receiving a role unless they already possess another specified role.
If a member does not have the required role, ReactionBot will ignore the reaction and no role will be assigned.
When to Use Required Roles
Require members to complete verification before selecting community roles.
Restrict staff-only reaction menus.
Prevent new members from accessing advanced server areas until they meet certain requirements.
Remove Existing Role
The Remove Existing Role option automatically removes another role whenever the configured role is assigned.
This is useful when two roles should never exist together.
Common Examples
Selecting the Blue Team role automatically removes the Red Team role.
Choosing a new notification role removes the previous notification role.
Assigning a Verified role removes an Unverified role.
Combining Both Features
Required Role and Remove Existing Role can be used together.
For example, members may first need the Verified role before selecting a color role, while selecting one color automatically removes any previously selected color.
Required Permissions
ReactionBot requires the Manage Roles permission.
Its highest role must also be above every role it assigns or removes.
Common Issues
If a role is not assigned, verify the member already has the required role.
If an old role is not removed, confirm ReactionBot has permission to manage both roles.
Managed Discord integration roles cannot be removed by any bot.