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

# Role buttons plugin

Toggle roles with button components on a message. Create a new panel or add buttons to an existing message.

## Configuration

```yaml
plugins:
  role_buttons:
    enabled: true
    overrides:
      - level: ">=50"
        config:
          can_create: true
          can_delete: true
```

## Commands

| Command              | Permission   | Description                                           |
| -------------------- | ------------ | ----------------------------------------------------- |
| `/rolebutton create` | `can_create` | Add a role toggle button to a new or existing message |
| `/rolebutton delete` | `can_delete` | Remove role buttons from a message                    |

## Requirements

* The bot needs **Manage Roles** and **Send Messages** in the target channel.
* The bot's highest role must be above toggled roles.
* Button interactions are handled automatically while the bot is online.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dreamliner.gitbook.io/dreamliner-docs/docs/plugins/role_buttons.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.