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

# Configuration

Configuration is done via Discord slash commands. Only administrators should be able use these.

<mark style="color:$primary;">The default permissions needed for config commands is</mark> <mark style="color:$primary;"></mark><mark style="color:$primary;">**Admin**</mark><mark style="color:$primary;">.</mark>

### Basic Setup

* Invite the bot to all servers you want to connect.
* Run `/config sources-of-truth` to add trusted users/bots (their bans are treated as authoritative).

### Key Settings

* **Incoming Bans**: Enable/disable syncing bans from other servers to this one.
* **Outgoing Bans**: Enable/disable sharing this server's bans with others.
* **Unban Mode**: Choose "Automatic" (auto-unban) or "Review" (manual decision via logs).
* **Logging Channel**: Set a channel for unban notifications. **This is needed when the Unban Mode is set to "Review"!**

Changes are saved to the database automatically. The bot cleans up old data on startup (guild configurations which are not present anymore in the loaded env-file).

{% hint style="danger" %}
If you start up the bot without the correct command, which doesn't use the correct env-file, the bot will delete old guild configuration (not bans). So make sure to use the correct commands if you're not using the `pnpm` commands.
{% 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://crossban.thelukez.com/docs/configuration.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.