> For the complete documentation index, see [llms.txt](https://docs.cw.crisisworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cw.crisisworks.com/modules/reports/system-administration-reports.md).

# System Administration Reports

<table><thead><tr><th width="355">Report Name</th><th>Description/Usage</th></tr></thead><tbody><tr><td>Audit Report</td><td>Provides audit action details recorded by the system for a specified time period.</td></tr><tr><td>Monthly Statistics of Emails &#x26; SMS's sent</td><td>Lists the monthly totals of Emails &#x26; SMSs sent for a nominated period</td></tr><tr><td>Security: Users having positions</td><td>Lists each user and their competent positions</td></tr><tr><td>Security: Positions having policies</td><td>Lists each position and all of its policies</td></tr><tr><td>Security: Users having policies based on current duty</td><td>Lists each user their effective policies based on their current duties. Note that this changes based on users going on and off duty.</td></tr><tr><td>File attachments</td><td>Lists file attachments along with their links to register items.</td></tr><tr><td>Events positions are involved in</td><td>Lists all events positions are involved in</td></tr></tbody></table>

For instructions on running reports, refer to: [Running Reports](https://docs.cw.crisisworks.com/system-administration/reporting/running-reports.md).


---

# 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://docs.cw.crisisworks.com/modules/reports/system-administration-reports.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.
