Discord Reaction Roles Bot

Reaction roles connect an emoji reaction on a Discord message to a server role.

When a member reacts with a configured emoji, ReactionBot can automatically assign the corresponding Discord role. Depending on the configuration, removing the reaction can also remove the role.

This gives members a simple way to choose roles for themselves without needing a moderator to manually assign them.

A reaction role bot automates Discord role assignment by watching reactions on configured messages.

Instead of asking moderators to assign roles individually, members interact with a role menu and ReactionBot handles the role change automatically.

Reaction roles are commonly used for interests, game roles, notification groups, regions, access levels, community preferences, verification, and other self-service role systems.

ReactionBot can turn a Discord message into a self-service role menu.

Each configured emoji can be connected to a different Discord role, allowing members to select the roles that apply to them.

This can reduce repetitive moderator work while giving members more control over how they participate in your community.

Role mappings can be combined into organized reaction role menus where members choose from multiple available roles.

For example, a gaming community could offer roles for different games, a creator community could offer notification roles, or a support server could let members identify which products they use.

ReactionBot watches the configured message and manages the linked roles as members interact with it.

Different communities need different role-selection behavior.

Some menus should allow members to choose only one role, while others should allow multiple roles at the same time.

ReactionBot includes role modes that let you control how members can interact with a configured role menu.

Reaction roles can also be used as part of a Discord verification or onboarding flow.

A member can react to a verification message and receive the role required to access additional areas of the server.

ReactionBot's role tools can be combined with requirements and role-removal behavior to create more controlled verification flows.

Role requirements let you control which members are eligible to use a reaction role.

This is useful when a role menu should only be available to members who already have another role or have reached a particular stage of your server's onboarding process.

Requirements give communities more control than a completely open self-role system.

ReactionBot can also manage roles that should be removed as part of a reaction-role action.

This can help build mutually exclusive role selections, verification systems, or workflows where receiving one role should replace another.

Automating these changes reduces the number of role-management tasks moderators need to perform manually.

Role activity can be logged so moderators can keep track of important reaction-role changes.

Logging is useful for verification systems, moderated communities, troubleshooting, and understanding how members are interacting with role menus.

ReactionBot includes dedicated role-logging options alongside its reaction role tools.

A reaction role mapping connects a Discord channel, message, emoji, and role.

Once the mapping is saved, ReactionBot watches that message for matching reactions.

When a member adds or removes a configured reaction, ReactionBot applies the corresponding role behavior automatically.

ReactionBot needs the Manage Roles permission to assign and remove Discord roles.

Discord's role hierarchy also requires ReactionBot's highest role to be positioned above every role the bot needs to manage.

If the bot has Manage Roles but its role is below the target role, Discord will prevent the role change.

Reaction roles make it easier to organize large Discord communities without requiring moderators to manually manage every member's preferences.

Members can choose the roles that are relevant to them, while server owners maintain control over which roles are available and how they can be assigned.

This makes reaction roles useful for onboarding, notifications, interests, gaming groups, access control, verification, and community organization.

ReactionBot supports reaction role mappings, single and multi role modes, verification flows, role requirements, automatic role removal, grouped role menus, role logging, and additional role-management options.

These features can be combined to build anything from a simple self-role message to a more structured onboarding or verification system.

Start by deciding which Discord roles members should be able to assign themselves and which message should act as the role menu.

Then create a reaction role mapping that connects the message, emoji, and Discord role.

The rest of the Roles documentation explains mappings, role modes, verification flows, requirements, logging, permissions, and troubleshooting in more detail.