Button roles

Post buttons that give members roles

Button roles let members give themselves a role by clicking a button.

Click a button to add or remove a role. Red Green Blue

Setup

You can publish from either the public roles builder or the dashboard:

  • The public builder exports a button-only blueprint. Copy its data into /button-roles.
  • The dashboard’s Settings → Button roles page publishes directly, supports button styles, and can publish a dropdown panel.

For the public builder, pick the roles and labels, then copy the exported data.

Go to the channel you want the buttons in and run /button-roles with that data pasted into the content option.

Clicking a button toggles the role: it adds the role if the member does not have it, and removes it if they do.

Limits and permissions

  • Button roles are a premium feature.
  • The bot needs Manage Roles, and its own role must sit above every role it hands out. Aethor checks this when a member clicks, not when you post the buttons.
  • The /button-roles command accepts buttons only. Dropdown blueprints are rejected by that command; use the dashboard to publish a dropdown panel.
  • A message can contain up to 25 buttons, split across five rows of five.
  • Button labels are capped at 80 characters.
  • The public builder creates Primary, or blurple, buttons without custom emoji fields. The dashboard lets you choose Primary, Secondary, Success or Danger styles.
  • There is no exclusive group. Every button is independent, so a member can hold several of the roles at once.
  • The role mapping lives only in the posted message. If the message is deleted, the setup is gone and there is no server-side copy to restore it.

To verify a panel, click each button with a test account. If a role does not change, check that Aethor’s role is above the target role and that the panel channel still accepts component interactions.