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

# Getting Started

Project Overwatch (POW) is a comprehensive moderation and staff management platform built specifically for ER:LC / PRC servers on Roblox. It bridges the gap between your game server, your Discord server, and your staff team.

{% hint style="info" %}
The official dashboard is located at: [**pow.ciankelly.xyz**](https://pow.ciankelly.xyz)
{% endhint %}

### Key Features

* **Real-time Logging:** Synchronize in-game logs directly to Discord and the POW Dashboard.
* **Staff Management:** Track shifts, enforce quotas, and manage Leave of Absence (LOA) requests.
* **Automation Engine:** Trigger Discord notifications and game commands based on server events.
* **Form Builder:** Create recruitment applications and surveys with automatic role granting.
* **Pro Features:** Protect your server with automated Raid Detection and AI-powered player risk assessments.
* **Rotector Integration:** Surface confirmed, human-reviewed safety flags from [Rotector](https://rotector.com), a third-party safety signal, directly on the player panel — advisory only, your staff always make the call.

Explore the sidebar to get started with setting up your community or learning more about specific features.


---

# 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://powdocs.atriasafety.org/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.
