> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/how-the-apps-work/screens/reports.md).

# Reports screens

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/reports/README.md).
{% endhint %}

Dashboards, task reports and exports. On the web, "Dashboard & Reports" holds the Dashboard, the Ops Dashboard (a separate analytics app in a frame) and the task and asset report pages, and Site reports has its own page. The report pages queue files on the server and list the user's reports; the apps have a smaller analytics screen built from the tasks on the device. Task reports for one task are made from [Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#share-task), and the housekeeping reports are in [Housekeeping](https://docs.snapfix.com/how-the-apps-work/screens/housekeeping.md). The endpoints are in the [Reports API](https://docs.snapfix.com/engineering-reference/api/reports.md).

| Screen                                                                                             | Platforms    | Where                                                                    |
| -------------------------------------------------------------------------------------------------- | ------------ | ------------------------------------------------------------------------ |
| [Dashboard](https://docs.snapfix.com/how-the-apps-work/screens/reports/dashboard.md)               | web          | web `/dashboard-reports/dashboard`; side menu "Dashboard & Reports"      |
| [Ops dashboard](https://docs.snapfix.com/how-the-apps-work/screens/reports/ops-dashboard.md)       | web          | web `/dashboard-reports/ops-dashboard` (frame)                           |
| [Task reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/task-reports.md)         | web          | web `/dashboard-reports/task-reports`                                    |
| [Asset reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/asset-reports.md)       | web          | web `/dashboard-reports/asset-reports`                                   |
| [Site reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/site-reports.md)         | web          | web `/admin-reports`; side menu "Site Reports" or "Multi-Site Reports"   |
| [Analytics](https://docs.snapfix.com/how-the-apps-work/screens/reports/analytics.md)               | ios, android | iOS and Android: a group's tasks or an asset list, "Analytics"           |
| [Legacy dashboard](https://docs.snapfix.com/how-the-apps-work/screens/reports/legacy-dashboard.md) | ios          | iOS: group task list, "Dashboard" in a bottom bar that appears on scroll |


---

# 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.snapfix.com/how-the-apps-work/screens/reports.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.
