> 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/how-ban-synchronization-works.md).

# How Ban Synchronization Works

### Ban Process

1. A user is banned in Server A.
2. The bot records the ban in its database, noting the reason and executor.
3. It checks connected servers (those with "incoming bans" enabled).
4. If auto-ban is on, it bans the user there. Otherwise, the server is skipped. *Maybe this will be changed to "review" in the future.*

### Unban Process

1. A user is unbanned in Server A.
2. The bot marks the user as "no longer banned" in the database for this server.
3. For connected servers:
   * Auto mode: Unbans immediately.
   * Review mode: Sends a log message with options to "Unban locally" or "Ignore".

### Truth Sources

* These are trusted users (e.g., server owners, moderation bots).
* Only the bans and unbans of trusted sources are synced.
* Manage via `/config sources-of-truth`.

The bot ignores a special user ID because of an agreement with the owner of this bot.


---

# 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/how-ban-synchronization-works.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.