> 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/user-interface-overview.md).
# User Interface Overview
Get to know the Report and Run mobile app.
### Directory
When you open the Report and Run: Offline mobile app, you will see a directory listing the folders and reports within your work space. Tap a report or folder in the directory to open it. In the image below, *A* is an example of a folder and *B* is an example of a report*.*
### Spaces, Text Templates, and Settings
To create or access additional work spaces, text templates, and settings, tap the three horizontal lines in the upper-left corner (see *A* in the image below).\
A panel will pop out, showing your spaces and other options. If you have subscribed to the paid features of Report and Run: Offline, this panel will show *Subscribed*. If you are using the free version, it will say *Free Tier*. \
### Reports
When you open a report, you will see a list of items, such as images, paragraphs, and sections. Tap on an item to open it.\
### Report items
With a report item open, you can quickly add text and additional images. To access more details on images, such as the title and description, pull up the bar below the image.\
### PDF generation
You can generate a PDF by clicking Share at the bottom-right corner of any report.\
The generated PDF can be downloaded on your phone, printed, or shared with others via email, text, or other communication tool.
---
# 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/user-interface-overview.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.
