> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c142/c143/q392.md).

# Do you have a user manual?

We offer a [comprehensive user manual](https://docs.reportandrun.com/manual) for all of our products, including a quick start guide to help you create your first report fast. 

For a visual overview of Report and Run, you can also check out our [video training content](/manual/videos.md) and walkthroughs on YouTube. 

If you need more detailed instructions or have specific questions, [feel free to reach out](/manual/faq/c169/q575.md). 

## Related

* [Article: Report and Run: Cloud Quick Start Guide](/manual/readme/quick-start-guide.md)
* [Article: Report and Run: Integrate Quick Start Guide](/manual/report-and-run-integrate/quick-start-guide.md)
* [Article: Report and Run: Offline Quick Start Guide](/manual/report-and-run/quick-start-guide.md)
* [Video: Report and Run (iOS + Android): Integrate + Cloud - Walkthrough](/manual/videos/cloud-videos/zi-gjdz4yw0.md)
* [Video: Report and Run (Mac + PC): Cloud + Web Portal Desktop Walkthrough](/manual/videos/cloud-videos/tdve4rbmlnw.md)
* [Video: Report and Run Offline: How to create and share a PDF from your phone](/manual/videos/offline-videos/qwzmudsgmuq.md)


---

# 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.reportandrun.com/manual/faq/c142/c143/q392.md?ask=<question>&goal=<user_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.