> For the complete documentation index, see [llms.txt](https://docs.agilecase.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.agilecase.com/administrator-documentation/reports/organizing-reports.md).
# Organizing Reports
This lesson will show you how to organize your reports in AgileCase using labels.
### Add a label to your report
To organize your reports, add a label to them.
These labels create categories that your reports will be split between on the "Reports" page. As you will likely produce a high volume of reports when using AgileCase, labels become a vital tool when organizing or searching through them.
At the bottom of the page when creating a report, you will see the option to add a label. Use this dropdown to select a system label to apply to your report.
Once you have finished, make sure to save your report to confirm the changes.
### Creating labels for reports
Unlike in other areas of the system, the labels you use on your reports must be created using the "Reports" page on the settings menu. You can learn how to do this in [this](/administrator-documentation/system-settings/creating-labels.md) lesson.
### Reports sorted by label
Once you are in the habit of applying labels to your reports, the reports page will become much easier to navigate.
Each label creates its own category under which reports bearing that label will be listed.
---
# 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.agilecase.com/administrator-documentation/reports/organizing-reports.md?ask=&goal=
```
`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.