> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/reports/report-builder/report-items.md).
# Report Items
Report items are parts of your report, each report item provides a unique set of functionalities to analyze your results.
## ➕ Adding a new report item
To add a new report item to your survey you may use any of the available report items as shown below.
## 🚀 Report item actions
Each report item supports following actions
* **`Filters`** narrow down your results based on [report filters](/form-management/reports/filters.md), on specific date ranges or on respondents languages.
* **`Reporting alias`**will use answer or question [reporting aliases](broken://pages/-MBKsbRkjgLF8KK4FENU) for its display set otherwise if none is available it will use the question and answer labels.
## ✂️ Filters
Enabling the filters will let you filter out the respondents and responses that you need in your report.
{% hint style="info" %}
Report item's data will be updated in real-time on each change of the filter properties.
{% endhint %}
---
# 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.ngsurvey.com/form-management/reports/report-builder/report-items.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.
