> For the complete documentation index, see [llms.txt](https://splay.gitbook.io/splay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://splay.gitbook.io/splay/setting-up/reaction-roles.md).

# Reaction Roles

Enable users to select their roles conveniently.

**Steps:**

**1. Adding Roles**

* To add roles to Aeona, use the command `/reactionroles add <name> <role> <emoji>`

  * `<name>` -> The role category name.
  * `<role>` -> Mention of the role.
  * `<emoji>` -> The emoji representing the role.

  *Example:*

  * `/reactionroles add games @minecraft ⛏`
  * `/reactionroles add pings @AnimeNight 🎥`

**2. Creating the List**

*You have two options:*

1. Allow users to select roles by clicking buttons.
   * `/reactionroles button [name] [channel]`
   * *Example:* `/reactionroles button pings #self-roles`
2. Let users pick their roles from a dropdown menu.
   * `/reactionroles menu <name> channel`
   * *Example:* `/reactionroles menu pings #self-roles`

**3. Customizing the Appearance**

*To modify the embed, execute /embed editembed channel messageid.*

* 'channel' refers to the channel containing the embed.
* 'message id' is the ID of the message with the embed.

*Example:* `/embed editembed self-roles` 1039985875490181211


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://splay.gitbook.io/splay/setting-up/reaction-roles.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.