Skip to main content
Auto Role can publish a persistent menu that lets each member manage the roles the server has approved. Configure it in Dashboard → Roles → Auto Role or with prefix commands. These panels use a select menu; they are not individual role-bound buttons or reaction roles.
The menu only offers roles Headless can manage that are safe for self-service. Headless hides and rejects @everyone, integration-managed roles, and roles with administrative or moderation permissions, even if someone tries to use an older panel.

​
Groups and selection

A server can save up to 8 groups, with up to 20 roles per group. One Discord select menu can display at most 25 options; when the configuration exceeds that limit, Headless shows only the first manageable options.
  • Exclusive — What happens when a member selects an option: Headless assigns the selected role and removes other manageable roles in the same group. If the member already has the selected role, it stays assigned.
  • Multi-select — What happens when a member selects an option: The selected role toggles: Headless adds it if the member does not have it and removes it if they do.
.autorole group creates exclusive groups. In Dashboard, you can switch a group to multi-select and customize its panel. If a menu combines groups and any group allows multi-select, Discord lets members choose multiple options; Headless still applies each group’s own rule when processing the selection.

​
Publishing and maintaining panels

.autorole panel publishes the main selector in the current channel or in the text channel you specify. Dashboard can also publish an independent panel for each group, with its own channel and styling. When the saved panel is available, Headless updates it instead of creating a duplicate. Configuration is stored in the server’s Auto Role settings. Persistent panels are re-registered after Headless restarts when their channel and message are still accessible. Interactions only work in a server, and Auto Role must be enabled both for the module and in that server’s configuration.

​
Permissions and safety

The person running these commands needs Manage Roles (native or compatible Fake Permissions) and must be the server owner, Headless owner, or a configured Anti-Nuke Admin. Server Administrator by itself does not replace this specific authorization check. Headless needs Manage Roles, and its highest role must be above every role offered by the menu. Integration-managed roles and roles above the bot’s hierarchy are omitted. The bot must also be able to view the publishing channel and send messages there.
When a member changes an exclusive group, Headless assigns the selected role first and then removes the previous roles so a failed assignment does not remove the member’s existing role first. If Discord rejects part of the update, the result may be partial: the member receives an ephemeral notice and should review their roles or ask staff for help; Headless records the error.

​
Setup steps

1

Prepare safe roles

Create roles intended for self-service and place Headless’s role above them. Do not use staff or administrator roles.
2

Create a group

In Dashboard, open Roles → Auto Role and add a group containing the allowed roles. You can also use the group command to quickly create an exclusive group.
3

Choose its selection mode and panel

Keep the group exclusive when members should choose one option, or enable multi-select when they should combine options. Customize the title, message, and channel if needed.
4

Publish and test

Publish the main menu with .autorole panel or publish the group from Dashboard. Test it with a member account and verify that selection changes respect the mode and hierarchy.

​
Commands by workflow

The autorole group is prefix-only; there is no equivalent slash command for managing it. Replace . if your server uses another prefix.

​
Create a role group

​
Publish and customize a panel

​
.autorole panel

Also works: .autorole panel #roles

​
.autorole title

​
.autorole message

group accepts a one-word name followed by role mentions. Creating a group with the same normalized identifier replaces its roles; the command saves up to 20 roles, and a server can save up to 8 groups. Use Dashboard to configure multi-select or a separate panel for an individual group.
Check that the role still exists, is not managed by an integration, and is below Headless’s highest role. The menu omits roles the bot cannot manage; saving a role does not guarantee that Discord lets the bot assign it.
Confirm Auto Role is not turned off in Dashboard or with .autorole off, and that Headless can still access the panel channel and message. If the channel or message was deleted, publish a new panel in the right destination.
This selector does not bind each button or reaction to a role. See Reaction Roles for emoji mappings and Auto Role for roles assigned when members join.