> For the complete documentation index, see [llms.txt](https://manual.harpe.io/start/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual.harpe.io/start/manual/capa/viewing-a-capa.md).
# Viewing a CAPA
Clicking on a CAPA will take you to a more detailed view of it. From here you can also add comments, upload files, and view the activity on that CAPA. The CAPA report page can be accessed by clicking on the `CAPA Report` button.
{% tabs %}
{% tab title="General" %}
This is the default view when a CAPA is opened. It shows all the general details you have assigned to the CAPA.
By clicking the `Edit` button at the bottom of the right-hand sidebar, you can alter any CAPA field.
Clicking on the `CAPA Report` button in the description panel will take you to a separate view where you can fill in the investigative report associated with this CAPA.
CAPA view page
{% endtab %}
{% tab title="Report" %}
Clicking on the `CAPA Report` button from the main CAPA view page will bring you to the report page for the associated CAPA. You can edit each individual field by clicking the `Edit` button in each section.
CAPA report page
{% endtab %}
{% endtabs %}
---
# 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://manual.harpe.io/start/manual/capa/viewing-a-capa.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.
