> 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/site-reports.md).

# Site reports

{% 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)). Platforms: web. [Source on GitHub](https://github.com/snapfix/docs/blob/main/spec/screens/reports/site-reports.md).
{% endhint %}

Create the "Performance report" spreadsheet for the groups in the filters, and download it from the list of the user's performance reports. With a multi-site selected the page is titled "Multi-Site Reports".

![Site reports](https://3653879137-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsVVGa79QbcEkJ7n8srxe%2Fuploads%2Fgit-blob-c11f7fd359050a97cf16960c486720b0700a9f1a%2Fsite-reports.png?alt=media)

* **Where:** web `/admin-reports`. Side menu "Site Reports" when no multi-site is selected, or "Multi-Site Reports" in its place while a multi-site is selected.
* **Who:** the side menu shows "Site Reports" to role "Admin" when no multi-site is selected. It shows "Multi-Site Reports" to every user while a multi-site is selected \[[ASK-119](https://github.com/snapfix/docs/blob/main/ASK.md#ask-119-who-should-see-site-reports-and-multi-site-reports)]. The route admits role "Admin" and group admins of the selected site, so a group admin can open the page by URL; it sends everyone else to `/fix`. The page has no text for a refused user, though the language file has "Site Reports can only be accessed by Site admins." and "Multi-site Reports can only be accessed by Multi-site admins." \[[ASK-119](https://github.com/snapfix/docs/blob/main/ASK.md#ask-119-who-should-see-site-reports-and-multi-site-reports)].
* **Feature:** [Site reports](https://docs.snapfix.com/product/features/reports/site-reports.md)

## Layout

The page has the header with the title "Site Reports" or "Multi-Site Reports", a title row with the same name and the filter button, then the filter banner and the two columns of [Task reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/task-reports.md#layout): the create panel on the left and "Your reports" on the right. The page has no tabs. The create panel has "Select a report to create", "Please set your filters to see the required information", "Create" and one card, "Performance report", with "Spreadsheet report at the site level. Ideal for monthly or quarterly site performance comparisons.". The banner shows "Created date: - " and " group(s)", with "Clear all".

With a multi-site selected, the header also has a site selector. On the first visit in multi-site mode the console's welcome dialog showed ("Welcome to your Multi-Site Console!", "Ok"). Choosing a site in the site menu after the multi-site brings back that site's selector, side menu and page.InputsThe page offers only these two filters, and the banner treats both as permanent. The drawer's "Apply" is off while nothing has changed. The request does not send the selected site as `parent_uuids`.ActionsStates

* **Loading:** the list shows the loading animation until the answer arrives.**Empty:** "No data available", with "0 of 0" in the pager. The API answers "no reports found!" as an error, and the page shows the empty text.**Error:** the list request skips the app's error dialog. A failed create shows the server's message.**Pending:** while a report made in the last 24 hours is below 100%, the list is asked for again after 3, 6, 9 and 12 seconds, then every 10 seconds. A new report starts again at 3 seconds.
* **Failed:** as on [Task reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/task-reports.md#states).
* **No permission:** as under **Who**.
* **Offline (mobile):** not applicable, web only.

## Dialogs and sheets

* **Delete report:** as on [Task reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/task-reports.md#dialogs-and-sheets).
* **Filters:** the shared filter drawer ([Filters](https://docs.snapfix.com/how-the-apps-work/screens/tasks/group-tasks.md#filters)), with only the panels "Groups" (collapsed at first, with its count) and "Dates".

## Platform differences

Web only. The apps have no site-level report.


---

# 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/site-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.
