> 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.md).

# Reports

This page outlines the Reports module and report folders.

## Overview

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

The Reports module provides reports categorised into folders based on their purpose and to apply security.

### Access

Access to reports is based on:

1. The Event you're signed in to and the registers enabled in it
2. The position you're on duty with and the security policies your administrator has applied to it

Reporting is generally a System Administration function. Ask your administrator if you need access to a specific report or folder.

For information on how to run reports, refer to: [Reporting](/system-administration/reporting.md)

### Setup and Configuration <a href="#requests-usingrequests" id="requests-usingrequests"></a>

Your System Administrator configures report access using security policies.

#### **Security Policies**

Refer to: [Positions: Security Policies](/system-administration/configuring-the-system/positions.md#security-policies)​

<details>

<summary><strong>Security Policy explanations</strong></summary>

The following security policies apply to Reports:

| Security Policy                         | Use                                                                            |
| --------------------------------------- | ------------------------------------------------------------------------------ |
| Access to base analytics data           | Can access basic reports                                                       |
| Access to EMV Recovery Portal Reporting | Access to [EMV Recovery Portal](broken://pages/a1lkrj9L29gsprDjb1Ld) folder    |
| Access to library analytics             | Access to the [Library Reports](broken://pages/2znzscpbaO2lafV8pP9V) folder    |
| Access to operations analytics          | Access to the [Operations Reports](broken://pages/rDzS0x7dG5bGlIkFeGEK) folder |
| Access to recovery analytics            | Access to the [Recovery Reports](broken://pages/4BZWTfGBU6PxeNo6ehdK) folder   |
| Access to resource analytics            | Access to the Operations: Resource Report                                      |
| Access to system analytics              | Can access protected reports such as audit and system reports.                 |

</details>


---

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