Skip to main content

Search GiselleBot's commands and docs.

Try /ban, or start with / for commands only.

Press Ctrl K anywhere in the dashboard to open this.

Reaction Roles and Self Assignable Roles

Note

Originally written by NaviKing, updated to reflect the current slash commands and dashboard pages.

See also

Different use cases of the same topic are described in the Configuring the Administration Module guide.

One popular bot feature is self-assignable roles and reaction (button) roles. Self-assignable roles are roles that users can add to and remove from themselves through a bot. Reaction (button) roles assign those roles when someone clicks a button on a specific message.

GiselleBot supports both, and this article covers how to set up your own self-assignable roles and reaction roles. For more on how self-assignable roles work, see the dedicated [Self-Assignable Roles section](/docs/moderation-and-administration/administration) of the full Administration documentation.

Step 1: Create a Role Group

Note

Adding and removing roles from a Role Group is done from your server's Self-Assignable Roles / Voice Roles page on the dashboard.

The first step in creating a self-assignable role is to add an existing role to a Role Group. A Role Group is simply any set of roles grouped together via your server's Self-Assignable Roles / Voice Roles page. For example, adding "Role 1" and "Role 2" to group 1 of your self assignable roles.

You can confirm this with /selfroles list, which shows the current self-assignable roles. You can add or remove roles later the same way.

Users can assign and remove roles with /role get and /role drop as soon as the role is in a Role Group. You can also configure your Role Group settings further and set up a reaction role menu for ease of use.

Step 2: Configure your Role Group

The next step is to configure your Role Group settings. This step is optional, but the default settings are worth knowing, and so are the options available.

You can configure a self-assignable Role Group's advanced options (mode, required roles, and more) right on the same Self-Assignable Roles dashboard page you used to add roles to it. A detailed explanation of each option can be found on the dedicated Self-Assignable Roles section of the full Administration documentation, but a few use cases are described below.

  • Let server boosters choose a color for themselves by creating a Role Group of different colored roles. Set up the Nitro Booster role as a required role and enable the prerequisites check feature.
  • Have people choose their favorite faction in a game by creating a Role Group with a role for each faction. Set the mode to Single and enable removing the existing role when assigning another role in the group. Alternatively, set the mode to Multiple and have people choose up to 2 or 3 of their favorite factions!
  • Have people assign a role to themselves to acknowledge they have read your server rules. Add your verification role to its own Role Group, enable single mode, and then enable requiring one role in the group at all times after the initial assignment. This way people will be able to assign the role to themselves, but not remove it. Note: A verification role only works if your server's role and channel permissions are set up for it, which falls outside GiselleBot. You can read more about this here.

Step 3: Create a reaction role menu

The last step is to set up your reaction role menu with /rolemenu create. Pass the group ID of the self-assignable role group you want to turn into a menu.

/rolemenu create group:1 [style:(auto|buttons|select)]

style defaults to auto: a group of up to 25 roles gets buttons, and anything larger gets a dropdown select menu automatically (so a big group is no longer silently cut down to its first 25 roles). Use style:buttons or style:select to force one form. A select menu can hold up to 125 roles.

After running this command, GiselleBot will send an embed instructing people to press a button to assign a role. Each button will be named after the role it's for. If you want the buttons to be named something else, you can simply rename your roles to what you want the buttons to say, create the role menu, and then change the name of the roles back to normal. This is great for making a self-assignable verification role menu to have the button say "I agree to the server rules" while keeping the role itself named "Member" long term.

If you want to edit the default message, you can use the /send edit command to do so. If you want to make an embed, I suggest using a website like https://discohook.org/ to generate the embed text. More information about the /send edit command is available on its documentation page.

If you modify the roles that are in your role group, you can update your reaction role menu using /rolemenu update. Do note that if you used the trick mentioned earlier to manipulate the names of the buttons such that they are different from the roles, you will need to temporarily update your role names again to match what the buttons say or running this command will also rename your existing buttons to your current role names.

Summary

After you create a self-assignable role group, you can then customize it and turn it into a reaction role menu. Although customizing the default behavior of a role group is optional, remember that you can't create a reaction role menu without a self-assignable role group.

Remember, this guide doesn't cover all of the self-assignable role commands. Be sure to check out the dedicated Self-Assignable Roles section of the full Administration documentation if you get stuck, and feel free to join GiselleBot's Support Server and ask additional questions there if you're still having problems after looking at the documentation!