> 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/reporting/adding-table-of-contents-to-a-report.md).
# Adding table of contents to a report
Add a dynamic table of contents to your report by configuring bookmarks for fields like name or ID, displaying item links with page numbers for easy navigation in aqua.
To create a table of contents in your report, drag the corresponding control element into the report header band. If there is no report header yet, aqua will create it, as soon as you drop the table of contents element .
Table of contents element in the Layout view
Now select the field you want to bookmark, e.g. the name or ID of the items. Go to 'Expressions' and select 'BeforePrint'. Enter the value in 'Bookmark'.
Setting the Bookmark value
You can either type the value manually by entering the name in apostrophes, or select the available field.
Typing the Bookmark value
If you execute your report now, you will see all the items listed with their page number and the field you configured as a hyperlink.
Table of Contents view after running the report
---
# 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/reporting/adding-table-of-contents-to-a-report.md?ask=&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.
