Role hierarchy and configuration
Place the bot role above roles it must manage. The configured threshold, enabled features, available backup and Discord API limits affect what can be detected or restored. No setup prevents every attack.
The current invitation requests Administrator. The table explains feature dependencies; it does not claim that narrower permissions are already deployed.
| Permission | Why it is needed | Used by |
|---|---|---|
Administrator | Currently requested by the invite link; grants broad permissions, but does not bypass role hierarchy. | Current invitation for both bots |
ViewAuditLog | Identify who performed administrative actions. | Anti-nuke detection and logs |
ManageChannels | Create channels and manage their structure and permissions. | Recovery, emergency controls, tickets and templates |
ManageRoles | Create, edit and assign roles below the bot role. | Recovery, welcome and role features |
BanMembers / KickMembers / ModerateMembers | Apply configured moderation when permissions and hierarchy allow it. | Moderation and protection |
ViewChannel / SendMessages / EmbedLinks / AttachFiles / ReadMessageHistory | Send panels, alerts and files, and read messages as required by each feature. | Tickets, logging and welcome |
ManageMessages | Delete messages that match configured moderation rules. | Moderation and AutoMod |
ManageWebhooks | Manage webhook integrations used by enabled features. | Logging integrations and protection |
Connect / Speak | Join voice channels and play audio when enabled. | Community Bot music |
Place the bot role above roles it must manage. The configured threshold, enabled features, available backup and Discord API limits affect what can be detected or restored. No setup prevents every attack.
With an available backup and sufficient permissions, structure recovery can recreate deleted roles and channels and repair supported saved permissions on existing roles and @everyone. Results depend on the recovery path and what the snapshot contains.