> For the complete documentation index, see [llms.txt](https://docs.aqua-cloud.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aqua-cloud.io/documentation/desktop-client/reporting/creating-a-report.md).

# Creating a Report

Learn how to create custom reports in the Desktop Client. Step-by-step instructions help you generate insightful data summaries tailored to your needs.

The report is created based on the information within the currently selected project folder or subfolder. The list of available reports depends on the amount of templates stored within the current selected project. Report templates can be used in multiple projects, either by directly copying them to another project or by storing the report locally and then importing the report into a new project using the Import / Export function.

  

<figure><img src="http://aquawiki.andagon.com/pictures/drex_creating_a_report_custom.png" alt=""><figcaption></figcaption></figure>

Before the report is created, a dialogue is presented in which the basis of the report can be fine-tuned by using filters. In this dialogue, you can also choose whether to include pictures, for example. The settings applied in the dialogue box prior to creating the report are set when creating the report template, but may be changed later in the Edit Properties context.&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_creating_a_report_custom_2.png" alt=""><figcaption></figcaption></figure>


---

# 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.aqua-cloud.io/documentation/desktop-client/reporting/creating-a-report.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.