Permissions Reference
Match bot capabilities and Discord role hierarchy to the features you use.
Permission checks are feature-specific
The current SHADO5 invite requests Administrator, and several slash-command setup flows require it. The table below explains important capabilities each feature uses; it is not a promise that every command accepts a reduced-permission installation.
Channel overwrites and role hierarchy remain relevant. Your dashboard access and the bot’s ability to act are separate.
Bot capabilities
| Feature | Important capabilities |
|---|---|
| Verification | Manage Roles; View Channel, Send Messages and Embed Links in verification and log channels; verified role below SHADO5. |
| Anti-Bot / Anti-Alt | Kick Members and sufficient role hierarchy. Logs also need a readable, writable channel where configured. |
| Anti-Words / Anti-Invite | View Channel, Manage Messages and Moderate Members for timeout enforcement; log-channel access. |
| Anti-Nuke | View Audit Log, Kick Members, Moderate Members, View Channel, Manage Messages and Read Message History; hierarchy still applies. |
| Honeypot | Manage Channels; Kick Members or Ban Members for the selected action; view, send, embed, manage messages and read history in the Honeypot channel. |
| Welcome & Goodbye | View Channel and Send Messages; Embed Links for embeds. Auto Role additionally needs Manage Roles and a safe lower role. |
| Giveaways | Access to the giveaway text channel and permission to send its messages and embeds. |
| Server Backup | Manage Roles and Manage Channels, with SHADO5 above the ordinary roles it must manage. |
Who can configure the server?
Owners, Discord administrators and explicitly authorized dashboard roles can use normal server configuration. Only owners and Discord administrators can change Dashboard Access. Backup creation and ordinary management require owner or Discord Administrator access; Full Server Restore and importing require the target owner.
For command-specific user permissions, use the Slash Commands reference.
When a permission appears correct but still fails
- Check SHADO5’s highest role and the target member or role.
- Check the selected channel’s permission overwrites.
- Confirm that the selected role or channel still exists.
- Review the workspace health warning and the module’s latest state.
- Retry once after fixing the permission.