> 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/dashboard/server.md). # Server How the bot behaves inside your Discord server. ## Basic Settings Roles, prefix and documentation. The three role lists here — staff, admin and management — are the foundation for every permission check in both the bot and the dashboard, so set them first. The command prefix (default `>`) is also here. ## Permissions Custom roles deciding who can use what. This replaces the three-level model with fine-grained rules mapping Discord roles onto individual dashboard sections and panel actions. Use it when "staff / admin / management" is too blunt. See [Permission levels](/getting-started/permissions.md). ## Server Overview The public page showing your live server. When enabled, it gives you a shareable page showing current status and who is on duty, without the viewer needing dashboard access. ## Whitelabel Run CSRP Moderation under your own bot branding, so the bot appears in your server under your own name and avatar. ## Anti-Ping Stop members pinging your staff. Nominate the roles to protect and what should happen when somebody pings them anyway. ## Reminders Recurring messages on a timer. Each reminder has its own interval, channel and message. ## Verification Link Roblox accounts and hand out roles. This drives the `>verify` command and the **Link account** button on the site, and can assign roles once somebody verifies. --- # 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/dashboard/server.md?ask=&goal= ``` `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.