ReactionBot Documentation
Reaction Control Permissions
Learn which Discord permissions ReactionBot requires to enforce reaction moderation and why each permission is important.
ReactionBot requires several Discord permissions to detect and moderate reactions correctly. Missing permissions may prevent certain Reaction Control features from working as expected.
Required Permissions
ReactionBot requires View Channels, Read Message History, and Manage Messages to fully enforce Reaction Control rules.
These permissions should be granted in every channel where reaction moderation is expected to operate.
If one or more permissions are missing, ReactionBot may be unable to perform certain moderation actions.
View Channels
View Channels allows ReactionBot to access the channels where reaction moderation is enabled.
If the bot cannot see a channel, it cannot monitor or moderate reactions within that channel.
Read Message History
Discord requires Read Message History for bots to properly access existing messages and their reactions.
Without this permission, ReactionBot may be unable to process reaction events reliably.
Manage Messages
Manage Messages allows ReactionBot to remove reactions that violate your configured rules.
This permission is required for Block, Allow Only, Limit Reactions, and Restrict Users to function correctly.
Without Manage Messages, ReactionBot may detect rule violations but cannot remove the offending reactions.
Channel Permissions
Discord permissions can be overridden on individual channels.
Even if ReactionBot has the correct permissions server-wide, a channel-specific permission override can prevent reaction moderation from working there.
If moderation works in some channels but not others, check the channel's permission overrides.
Role Hierarchy
Reaction moderation is generally not affected by role hierarchy in the same way that role management is.
However, ReactionBot's role should still remain reasonably high in your server's role list to avoid unexpected permission conflicts.
Verifying Permissions
The easiest way to verify ReactionBot's permissions is by running the /diagnose command in the affected channel.
The diagnostic report will identify missing permissions and help explain why a feature may not be working.
Common Permission Issues
Most permission problems are caused by Manage Messages being removed or overridden within a specific channel.
Private channels that do not grant ReactionBot access will also prevent reaction moderation from operating.
Review both server-level and channel-level permissions when troubleshooting.
Best Practices
Grant ReactionBot the recommended permissions during installation and avoid unnecessary channel overrides.
After making permission changes, test reaction moderation in the affected channel to confirm everything is working correctly.
Troubleshooting
If Reaction Control is not behaving as expected, first run /diagnose in the affected channel.
Verify that View Channels, Read Message History, and Manage Messages are all enabled for ReactionBot.
If the required permissions are present and issues continue, review your Channel Rules and Global Rules to ensure they are configured correctly.