RDD permissions
Grant only the permissions needed for the features you enable.Minecraft permissions
All /rdd routes are player commands. Operators receive administrative access by default, but the join-gate bypass must be granted explicitly. Discord bot permissions do not grant Minecraft permissions.
Discord permissions and hierarchy
Grant permissions in the selected test or customer guild, and allow the bot in each selected channel. Keep its highest role above roles and ordinary members it manages. Managed integration roles and protected higher members cannot be managed. Administrator is not required.
View Channel, Send Messages and Read Message History for bridged channels and status panels; Embed Links for alert embeds.
Manage Webhooks for player-name/avatar webhook messages. Current connection checks inspect the guild-level permission.
Manage Roles for linked roles, role mappings and voice permission overwrites; Manage Nicknames for nickname sync.
Ban Members for Minecraft-to-Discord bans. Enable each ban direction deliberately and use consenting targets when testing.
Manage Channels, Manage Roles, Move Members and Connect to target lobbies/groups. Mute Members is also needed when lobby muting is enabled.
Human callers need Use Application Commands. Broadcast and resync require Manage Server. Console requires an explicitly allowed staff role and command; Manage Server is not required for console.