Solara relies on Discord permissions to carry out actions on your server’s behalf — responding to commands, managing roles, deleting messages, and recording audit events. If a required permission is missing in a channel or at the server level, the affected feature will silently fail or return an error. Understanding which permissions Solara needs — and why — helps you avoid those gaps.
Required permissions
| Permission | Why Solara needs it |
|---|
| Send Messages | To respond to slash commands and deliver bot output in channels. |
| Embed Links | To send rich embed responses — most Solara output uses embeds. |
| Read Message History | Required by /purge to bulk-delete messages, and by audit log features to inspect past messages. |
| Manage Messages | Required by /purge to delete messages from other users, and by /slowmode to apply rate limits. |
| Manage Roles | Required for auto-role on join and reaction roles to assign and remove roles from members. |
| Kick Members | Required by the /kick command to remove members from the server. |
| Ban Members | Required by /ban and /unban to apply and revoke server bans. |
| Moderate Members | Required by /mute to apply Discord’s native timeout feature to members. |
| View Audit Log | Required by logging features to capture server-level events such as bans, role changes, and channel edits. |
| Administrator | Grants all permissions above in one step. Recommended for the simplest, most reliable setup. |
The default Add to Discord invite link requests the Administrator permission automatically. This is the easiest way to ensure Solara can access everything it needs without manual permission configuration. Using custom permissions
If you prefer not to grant Administrator, you can authorize Solara with only the specific permissions it needs. Make sure to grant each permission listed above at the server level, and verify channel-level permission overrides aren’t blocking Solara in channels where you want it to operate.
If you use custom permissions and Solara needs to assign or manage roles, its own role must be positioned higher in the role hierarchy than any role it is expected to assign, remove, or modify. Discord prevents bots from managing roles equal to or above their own position.
Troubleshooting
If Solara stops responding in a specific channel, the most common cause is a missing channel-level permission override. Check that Solara’s role has Send Messages and Embed Links enabled in that channel’s permission settings. Server-level permissions can be overridden by channel-specific rules, so a bot with Administrator at the server level can still be blocked in individual channels.