Documentation Index
Fetch the complete documentation index at: https://docs.stellarbot.dev/llms.txt
Use this file to discover all available pages before exploring further.
Stellar requests only the permissions it needs to operate, but Discord’s permission model means the right access must be granted at the right level — both to the bot itself and to the users invoking commands. This page breaks down exactly what Stellar and your server members need, organized by feature, so you can configure the minimum required access for each module you use.
The simplest setup is to grant Stellar the Administrator permission. This eliminates all permission-related issues and is fine for most servers. The breakdown below is for server owners who prefer a security-conscious setup and want to grant only the minimum permissions each feature requires.
General (always required)
These permissions are needed for Stellar to function at all, regardless of which features you use.
| Permission | Who needs it |
|---|
| Send Messages | Stellar (bot) |
| Embed Links | Stellar (bot) |
| Read Message History | Stellar (bot) |
| View Channel | Stellar (bot) |
Moderation
Ban and unban
The /ban and /unban commands both require Ban Members on both sides — Stellar needs it to execute the ban via the Discord API, and the user running the command needs it to prove they’re authorized to take that action.
| Permission | Who needs it |
|---|
| Ban Members | Stellar (bot) + invoking user |
Kick
| Permission | Who needs it |
|---|
| Kick Members | Stellar (bot) + invoking user |
Soft ban
A soft ban bans and immediately unbans a member to delete their recent message history without keeping them banned. It uses the same permission as a regular ban.
| Permission | Who needs it |
|---|
| Ban Members | Stellar (bot) + invoking user |
Purge
The /purge command can only delete messages up to 14 days old (a Discord API limitation). Stellar needs View Channel to read the message history, and both Stellar and the invoking user need Manage Messages to delete them.
| Permission | Who needs it |
|---|
| Manage Messages | Stellar (bot) + invoking user |
| View Channel | Stellar (bot) |
Lock and unlock
/lock and /unlock modify channel permission overwrites to prevent or restore member messaging. This requires Manage Channels on both sides.
| Permission | Who needs it |
|---|
| Manage Channels | Stellar (bot) + invoking user |
Warnings
| Permission | Who needs it |
|---|
| Manage Messages | Invoking user |
Channel management
Clone channel
/clonechannel (also available as /clone) creates a copy of a text channel, including its permission overwrites, topic, and position.
| Permission | Who needs it |
|---|
| Manage Channels | Stellar (bot) + invoking user |
Poll
/poll sends a formatted poll embed to the current channel. Discord routes this through the Manage Channels permission.
| Permission | Who needs it |
|---|
| Manage Channels | Invoking user |
Member management
Auto-role
Stellar assigns a role to every new member who joins. For this to work, Stellar’s own role must be positioned above the role it is assigning in your server’s role hierarchy — this is a Discord requirement, not a Stellar one. If Stellar’s role is below the target role, the assignment will fail silently.
| Permission | Who needs it |
|---|
| Manage Roles | Stellar (bot) |
| Manage Guild | Invoking user (to configure) |
After changing the autorole configuration, verify your role hierarchy under Server Settings → Roles. Stellar’s role must appear above the autorole target in the list.
Verification
The verification system assigns a role to members after they complete a challenge. Like auto-role, the verified role must be below Stellar’s role in the hierarchy.
| Permission | Who needs it |
|---|
| Manage Roles | Stellar (bot) |
| Send Messages | Stellar (bot) |
| Manage Guild | Invoking user (to configure) |
Logging
Stellar posts moderation and event logs to a designated channel. It needs permission to view and send messages in that channel. If the log channel has restricted access, add a permission override granting Stellar access explicitly.
| Permission | Who needs it |
|---|
| Manage Permissions (for the log channel) | Stellar (bot) |
| View Channel (for the log channel) | Stellar (bot) |
| Manage Guild | Invoking user (to configure) |
Content moderation
Chat filter
The chat filter automatically removes messages that match configured rules. Stellar must be able to delete messages in the channels where filtering is active.
| Permission | Who needs it |
|---|
| Manage Messages | Stellar (bot) |
| Manage Guild | Invoking user (to configure) |
Server features
XP system
| Permission | Who needs it |
|---|
| Manage Guild | Invoking user (to configure) |
Giveaways
| Permission | Who needs it |
|---|
| Manage Guild | Invoking user (to configure) |
Sticky messages
| Permission | Who needs it |
|---|
| Manage Guild | Invoking user (to configure) |
| Permission | Who needs it |
|---|
| Manage Messages | Invoking user |
Tickets
The ticket system uses a separate role-based access model. You designate a ticket support role in the dashboard; any member with that role can view and respond to open tickets. No additional Discord permissions are required beyond what Stellar needs to create and manage channels.
| Permission | Who needs it |
|---|
| Ticket support role | Staff members who manage tickets |
