> 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/getting-started/permissions.md).

# Permission levels

Everything in CSRP Moderation is gated on one of three levels. They come from the roles set in **Dashboard → Basic Settings**, and they apply identically to bot commands and dashboard pages.

| Level          | Who gets it                              | Typically can                                                                             |
| -------------- | ---------------------------------------- | ----------------------------------------------------------------------------------------- |
| **Staff**      | Anyone with a configured staff role      | Go on duty, log punishments, file leave, use the in-game tools                            |
| **Admin**      | Anyone with a configured admin role      | Everything staff can, plus administrate other people's shifts and leave, and run sessions |
| **Management** | Anyone with a configured management role | Everything, including configuration, the dashboard and destructive actions                |

Two shortcuts always resolve to Management, whatever roles are set:

* The server owner.
* Anyone with Discord's **Administrator** or **Manage Server** permission.

That second rule exists so the bot and the dashboard agree. Discord elevates every permission for Administrator holders, so if the dashboard did not match, somebody could act through the bot but be refused on the site.

## Custom permissions

Management can replace the three-level model with fine-grained rules in **Dashboard → Permissions**. Custom roles map Discord roles onto individual keys, of two kinds:

* `dashboard.<section>.view` and `dashboard.<section>.manage` — who can see and change one dashboard page.
* `panel.<action>` — who can perform one action, such as `panel.shift.forceEnd` or `panel.shift.void`.

Custom rules widen access; they never take anything away from Management.

## When something is refused

If a command or page refuses you, it is almost always one of:

1. Your roles are not in the staff, admin or management lists in Basic Settings.
2. The feature is disabled for the server on its dashboard page.
3. A custom permission role grants the section to other roles but not yours.


---

# 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://csrpmoddocs.officialcaliforniastateroleplay.com/getting-started/permissions.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.