> 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/creating-reports/adding-case-links-to-reports.md).
# Adding Case Links to Reports
This lesson will show you how to add hyperlinks to reports in order to quickly navigate to the cases they have highlighted.
### Add the Case Link entity as a column
Case links provide a hyperlink to any cases that the report pulls up when it is run. To add case links to a report, you must add the "Case Link" entity as a column within the report.
### An example of a report with case links
When you run a report that includes a case links, the Case Links column will be populated with hyperlinks that will take you directly to the case that the row they inhabit refers to when clicked.
---
# 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/creating-reports/adding-case-links-to-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.