Permissions
How Solitary checks permissions, and what each module actually requires.
Overview
Solitary invites with a broad default permission set so no feature is blocked out of the box, but most configuration commands still check for a specific Discord permission before running, on top of Solitary's own role-hierarchy checks.
Common Requirements
| Permission | Typically required for |
|---|---|
| Administrator | Fake permissions, security setup, reaction triggers, starboard/clownboard configuration. |
| Manage Server | Welcome, goodbye, sticky messages, autorole, honeypot, reaction roles, logging, giveaways, and most other config-style modules. |
| Manage Channels | Lock/unlock/lockdown, sticky messages, roleplay NSFW toggle, filter (or being the server owner or a filter-specific admin). |
| Manage Messages | Purge, tags, clearsnipe. |
| Manage Nicknames | Nickname, forcenick (forcenick additionally requires Manage Server). |
| Ban Members / Kick Members | Checked internally by ban/kick-family commands rather than solely relying on Discord's own permission gate. |
| Server Owner only | Antinuke and antiraid admin management, fake permissions, backups, snipe access control, massunban. |
Server Owner vs. Admin
A number of the most sensitive commands, most notably backups, fake permissions, and managing antinuke/antiraid admins and trust, are restricted to the server owner specifically. Being a Discord Administrator is not enough for these; the intent is that a single compromised admin account can't disable the server's own defenses.
When a Command Fails
If a command refuses to run, Solitary's error message states exactly which permission or role was missing. If the bot itself is missing a permission it needs (for example Manage Channels to lock a channel), that's called out separately from your own permissions.