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

# CSRP Moderation

CSRP Moderation is the staff management system behind California State Roleplay. It is two halves of one product:

* A **Discord bot** your team uses day to day: going on duty, logging punishments, filing leave, running the ER:LC server from Discord.
* A **web dashboard** where management configures all of it, reviews the records the bot produces, and handles applications.

Both read and write the same database, so a shift started with `>duty manage` in Discord appears on the dashboard immediately, and a quota changed on the dashboard applies to the next command run in Discord.

## Where to start

| You are                                         | Start here                                           |
| ----------------------------------------------- | ---------------------------------------------------- |
| A staff member who just needs the commands      | [Bot commands](/bot-commands/bot.md)                 |
| Setting the server up for the first time        | [First-time setup](/getting-started/setup.md)        |
| Management configuring the system               | [Dashboard](/dashboard/dashboard.md)                 |
| Trying to work out who can do what              | [Permission levels](/getting-started/permissions.md) |
| After the desktop app rather than a browser tab | [Desktop app](/the-rest-of-the-site/desktop.md)      |

## Conventions in this book

Commands are written with the default `>` prefix, as in `>duty manage`. If your server changed the prefix, substitute yours. Almost every command is also available as a slash command, so `>duty manage` and `/duty manage` do the same thing.

The **Who can use it** column in each command table is the minimum level required. Management can run everything an administrator can, and administrators everything staff can.


---

# 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://csrpmoddocs.officialcaliforniastateroleplay.com/readme.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.
