> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/dashboards/insights/reports.md).

# Reports

The Reports tab displays all environments detected by AppControl in all of your hosting platforms. For each environment, if the deployed revision has been analyzed, a series of reports is available. Select the report type you want to generate from the 'Report type' selector.

If AppControl does not have sufficient access to the app, or the deployed revision has not yet been analyzed, the message 'no deployed app' will be displayed.

You can download a PDF version of the app report by clicking on the 'download PDF' link. Note: This feature must be configured first by your platform administrator from the feature settings tab in the [System Configuration](https://docs.bluestorm.io/administration/system/system-configuration.md) page.

The following report types are available:

* [Governance.](https://docs.bluestorm.io/dashboards/insights/reports/governance.md) Reports on the current governance status of the selected app / environment, and lists all details of issues and violations related to your controls.
* [Security.](https://docs.bluestorm.io/dashboards/insights/reports/security.md) Reports on the current security status of the selected app / environment, and lists all details of security issues and violations.


---

# 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.bluestorm.io/dashboards/insights/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.
