> 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/table-of-contents.md).

# Table of Contents

In aqua reports, you can create a table of content. To do so, create a new report:

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

&#x20;

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

&#x20;&#x20;

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

Now, insert a Table of Content into your report...

&#x20;&#x20;

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

...and you will receive the following result: &#x20;

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

Now, add requirements into your report in order to define a table of content by requirements. You will achieve the following result: &#x20;

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

Next, define that the requirement name will be visible in report table of content. To do so, click on the field Name and switch into the properties on the right-hand side. &#x20;

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

There, define the Binding in Data Binding -> Bookmark. Then, define it using Data->ReportData->RequirementReport->Requirements->Name. &#x20;

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

You will receive the following result: &#x20;

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

Then, save your report and you are ready to create a report. In this case, there are a couple of copied requirements:&#x20;

&#x20;

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

After generating the report, we get the following result:&#x20;

<figure><img src="http://aquawiki.andagon.com/pictures/drex_table_of_contents_3_custom_11.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 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.aqua-cloud.io/documentation/desktop-client/reporting/table-of-contents.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.