> For the complete documentation index, see [llms.txt](https://docs.clashperk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.clashperk.com/others/bot-manager.md).

# Bot Manager Role

Give clan leaders the Bot Manager role so they can run ClashPerk admin commands like logs, rosters and auto roles without Manage Server permission.

Most ClashPerk setup commands — clan logs, auto-roles, reminders, linking players for other people — need the **Manage Server** permission on Discord. That permission also lets someone change your whole server, so you may not want to hand it to every clan leader or co-leader.

The **Bot Manager** role solves this. Anyone with the role can use all of ClashPerk's admin commands, but gets no extra Discord permissions.

{% hint style="info" %}
**Typical use:** give it to your clan leaders and co-leaders so they can set up logs, manage rosters, and link members — while only server admins keep Manage Server.
{% endhint %}

## Set it up

{% stepper %}
{% step %}

### Run the command

<mark style="color:blue;">**/config**</mark> <mark style="color:purple;">**bot\_manager\_role:**</mark> `@Bot Manager`

You need **Manage Server** or an existing Bot Manager role to run it, so only hand the role to people you trust.
{% endstep %}

{% step %}

### Add more roles or remove one (optional)

Run <mark style="color:blue;">**/config**</mark> on its own and press **Manage Permissions**. Pick the role type, then choose one or more roles. Clear the selection to remove them all.

You can also change these from the dashboard's server settings.
{% endstep %}
{% endstepper %}

## Who can use admin commands

A member can use an admin command if **any** of these is true:

* They have the **Manage Server** permission.
* They have the **Bot Manager** role.
* They have the narrower manager role for that command (below).

***

## Narrower manager roles

Need someone to handle just one job? Give them a scoped role instead of full Bot Manager.

| Role               | Lets members                                                                                                                                | Set with                                                                                                           |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| **Roster Manager** | Create, edit, clone, delete, post and ping [rosters](https://docs.clashperk.com/features/rosters.md), and manage roster members and groups. | <mark style="color:blue;">**/config**</mark> <mark style="color:purple;">**roster\_manager\_role:**</mark> `@Role` |
| **Links Manager**  | Link and unlink players for other members, and refresh another member's auto-roles.                                                         | <mark style="color:blue;">**/config**</mark> <mark style="color:purple;">**links\_manager\_role:**</mark> `@Role`  |
| **Flags Manager**  | Create and delete [flags (bans/strikes)](https://docs.clashperk.com/features/flags-ban-strike.md).                                          | <mark style="color:blue;">**/config**</mark> <mark style="color:purple;">**flags\_manager\_role:**</mark> `@Role`  |

{% hint style="info" %}
Want to open just **one** command to someone? Use the [whitelist](https://docs.clashperk.com/others/whitelist.md) instead.
{% endhint %}


---

# 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://docs.clashperk.com/others/bot-manager.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.
