> 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/report-and-run-offline-team/showing-your-team-how-to-use-report-and-run-offline.md).

# Showing your team how to use Report and Run: Offline

Three good ways to learn how to use Report and Run: Offline.

1. If you want to see how to create your first report in under a minute, watch our [quick start video](https://youtube.com/shorts/QWzmUDSGMuQ?feature=share).
2. If you want to see all of the Report and Run: Offline videos, we have a [we have a full playlist on YouTube](https://www.youtube.com/watch?v=QWzmUDSGMuQ\&list=PL_ls6I3LliEQHgfWwB6_zJV_1WgBNCaK0).
3. We also have a Quick Start Guide that shows [how to create a report](https://docs.reportandrun.com/manual/report-and-run/quick-start-guide.md) (with text and screenshots).

{% hint style="info" %}
If you are running older versions of Report and Run: Offline (before v. 2.0), [please visit this article for legacy training guides](https://docs.reportandrun.com/manual/report-and-run-offline-team/showing-your-team-how-to-use-report-and-run-offline/showing-your-team-how-to-use-report-and-run-offline-android-12-and-below.md).&#x20;
{% 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.reportandrun.com/manual/report-and-run-offline-team/showing-your-team-how-to-use-report-and-run-offline.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.
