Required Permissions
Strom Bot needs the following permissions to function correctly. Missing permissions won’t crash the bot, but the affected features will silently fail or return errors. We recommend reviewing this list carefully before inviting the bot to a production server.
| Permission | Used By | Why It’s Needed |
|---|---|---|
| Manage Roles | Role Rewards, Reaction Roles, AutoMod, Welcome Auto-Role | Assign and remove roles from members. The bot’s own role must be higher in the hierarchy than any role it manages. |
| Manage Channels | Channel Lockdown, Auto-Setup, Slowmode | Lock/unlock channels during incidents and configure slowmode without manual admin intervention. |
| Kick Members | Moderation — /kick | Remove members from the server. Cannot be used on members with equal or higher roles. |
| Ban Members | Moderation — /ban, /unban | Permanently ban members and unban by user ID. Required separately from Kick. |
| Moderate Members | Moderation — /timeout | Apply and remove Discord-native timeouts (communication restrictions). |
| Send Messages | All features | Every bot response, command reply, announcement, and log message requires this in the target channel. |
| Send Messages in Threads | Logging, AutoMod, Giveaway | Required separately if any log or response channel uses threads. |
| Embed Links | Welcome, Levels, Logging, Giveaway, AutoResponder | All rich responses use Discord embeds. Without this, messages fall back to plain text or fail entirely. |
| Attach Files | Levels — Rank Card | Sending the /rank image card requires file attachment permission in the channel. |
| Read Message History | Logging, Purge, AutoMod, AutoResponder | Required to read prior messages for bulk-delete (/purge), context-aware responses, and message edit/delete logging. |
| Manage Messages | Purge, AutoMod | Delete messages in bulk and remove messages that trigger AutoMod rules. |
| Add Reactions | Reaction Roles, Giveaway | Add the initial reaction to reaction role messages and giveaway entry embeds. |
| Use External Emojis | Welcome, Giveaway, AutoResponder | Display custom emojis from other servers inside bot messages and embeds. |
| View Audit Log | Server Logging, Mod Logs | Fetch audit log entries to attribute actions (e.g. who banned a member, who deleted a message) in log embeds. |
| View Channels | All features | The bot must be able to see a channel to read or write in it. Missing this causes silent failures. |
| Connect | Voice / Music (upcoming) | Join voice channels. Required before any audio permission is meaningful. |
| Speak | Voice / Music (upcoming) | Transmit audio in a voice channel for music and audio features. |
| Mention Everyone | Announcements, Giveaway (optional) | Ping @everyone or @here in giveaway announcements. Disable if you don’t use this feature. |
Role Hierarchy
Permissions alone are not enough — role position matters. Discord enforces a strict hierarchy: a bot can only manage roles that sit below its own highest role.
Granting Administrator permission covers all of the above and ensures no features are accidentally blocked.
If Strom Bot’s role is below Moderator, it cannot assign or remove the Moderator role — even if it has Manage Roles. Always drag the Strom Bot role above every role it needs to control in Server Settings → Roles.
Channel-Level Overrides
Server-wide permissions can be overridden per channel. If a feature stops working in a specific channel, check the channel’s permission overrides:
- Right-click the channel → Edit Channel → Permissions
- Find the Strom Bot role or
@everyone - Make sure the required permission is not explicitly set to ❌ Deny
Common culprits:
Send Messagesdenied in a log channel → logs silently failView Channeldenied → bot cannot see or interact with the channel at allEmbed Linksdenied → all embed responses fall back to plain text
Recommended Setup
Administrator permission covers every permission in the table above and bypasses channel-level overrides entirely. This is the easiest setup for most servers and ensures no feature is accidentally blocked by a misconfigured channel.
Server Settings → Roles → Strom Bot → Enable Administrator
If you’d rather not grant Administrator, add each permission from the table individually and double-check channel overrides for your log, mod, and welcome channels. Use the /debug permissions command (coming soon) to identify any missing permissions automatically.