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

# Reports

The **Reports** section under **Analytics** stores and organizes document-based reports generated by AI agents during ticket work. You can browse all reports, filter by category, preview content inline, and add new reports from files attached to any ticket.

## Viewing Reports

Navigate to **Analytics** > **Reports** in the left sidebar.

![Reports list](/files/znQ90Re8cM4yK3sKjRIc)

The list shows every registered report. Use the **Compliance** and **Security** tabs at the top to filter by category. Each row shows the report name, its source, the entity (ticket) it came from, and the file path on disk.

![SOC 2 report row highlighted](/files/1PiDMo1eIa6TJibhgPRj)

Click any report name to open a full inline preview.

![SOC 2 report preview](/files/NbiGonTPCBLyqDTie4Y5)

## Adding a Report

Reports are sourced from files that an agent deposited into a ticket during its work. To register a file as a report:

### 1. Click Add

Click the **Add** button in the top-right corner of the Reports list.

![Add button](/files/6ZoKvii2ae6zlz0PyOW4)

The **Add Report Files** modal opens. The **Source** field defaults to **Ticket**.

![Add Report Files modal](/files/5kXm1KyHbfnv0RoR5aSC)

### 2. Select the ticket

Click the **Ticket** dropdown and type part of the ticket name to search. Select the ticket whose files you want to browse.

![Ticket search dropdown](/files/t4V8YPYD5CRNSEE5fFaC)

### 3. Browse files

Once a ticket is selected, the modal displays the agent's working directory. Expand folders to navigate to the file you want to add. The **Report** column shows a badge on any file that has already been registered as a report.

![File browser with canvas-documents expanded](/files/Si3m3PoUIx9Rftv4Lf4u)

### 4. Open the file menu

Click the **⋮** icon on the row of the file you want to add, then select **Add to Reports**.

![Kebab menu open on file row](/files/9pNv3VsCZoQJDZNFwgF9)

### 5. Enter report details

The **Add to Reports** dialog appears, pre-filled with the selected file name. Enter a **Name** for the report and, optionally, a **Category**. The category determines which tab the report appears under on the Reports list.

![Add to Reports dialog — empty](/files/8ofCCiSzVmoJDKt8Ythd)

![Add to Reports dialog — filled in](/files/5FhioqlY9px2RjWeW43o)

Click **Add** to save the report.

## Viewing the New Report

After saving, the report is immediately available in the Reports list. Click the tab that matches the category you entered to filter the view.

![Reports list — Security tab](/files/VTSG3NkwvZXwp4ldeXEE)

The new report appears in the list.

![New report highlighted](/files/7caRtvqPc1CJ2DBQAYrI)

Click the report name to open the inline preview.

![New report preview](/files/LFDX50iXXJgoLDLa7otM)


---

# 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.duplocloud.com/docs/armor/additional-components/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.