> 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/product/features/reports/asset-reports.md).

# Asset 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)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/product/features/asset-reports.md).
{% endhint %}

**Asset reports** are spreadsheets of the assets in the **asset registers** people pick. On the web, the "Asset Reports" tab of **Dashboard & Reports** makes one type, the "Multi-Asset Report (export)", and lists the user's asset reports of the last 30 days. The page works like [Task reports](https://docs.snapfix.com/product/features/reports/task-reports.md). On Android, an asset register's "+" menu also has "Asset Details Report (XLSX)", which is not a server report: it shares a CSV of the register's tasks from the phone.

## Rules

* Any signed-in user can open the tab. Creating a report needs `perJobReportGenerate` in every selected asset register. Only the browser checks it, as on [Task reports](https://docs.snapfix.com/product/features/reports/task-reports.md) ([Asset reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/asset-reports.md#actions)).
* The permission alert says "The group …" and "Groups filter", though the item is an asset register ([Asset reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/asset-reports.md#dialogs-and-sheets)).
* The filters are the task report filters with asset registers in place of groups, and no group or tag filter. The default is every register of the site; an empty selection means every register again ([Asset reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/asset-reports.md#inputs)).
* The "Attribute" filter is never sent, so it does not change the report.
* The list holds the user's multi-asset and single-asset reports of the last 30 days. No code writes a single-asset report today (php-apis @ 238ca4414e, `report.functions.php:8431`; no writer in any repo).
* The list, polling, download, delete and public file rules are those of [Task reports](https://docs.snapfix.com/product/features/reports/task-reports.md#the-list).
* The Android item shows to group admins of the register and to users with `perJobReportGenerate` there; no plan switch is read for it (android @ 86068bfeea, `AssetPlusMenuBottomSheet.kt:136`).
* The Android item makes no request and writes no report row. Its file is a CSV of the register's tasks that the phone has loaded, with the assets' attributes, named after the register and the date, although the label says XLSX ([Asset reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/asset-reports.md#platform-differences)).

## Flow

```mermaid
flowchart TD
    regs["Pick asset registers in the filters"] --> pick["Pick Multi-Asset Report (export)"]
    pick --> create["Create"]
    create --> perm{"Report permission in every selected register?"}
    perm -- no --> alert["Alert names the register"]
    perm -- yes --> queued["Report row added, spreadsheet built after the answer"]
    queued --> done["100%: Download"]
    plus["Android: register's + menu, Asset Details Report (XLSX)"] --> csv["Share a CSV of the loaded tasks"]
    csv --> none["No request and no report row"]
```

## Platforms

| Capability                                           | Web | iOS                                                                                                          | Android                                                                                                      |
| ---------------------------------------------------- | --- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| "Multi-Asset Report (export)" with its list          | Yes | No                                                                                                           | No                                                                                                           |
| "Asset Details Report (XLSX)", a device CSV of tasks | No  | No                                                                                                           | Yes                                                                                                          |
| Task reports of a register's tasks                   | No  | Yes, from the asset list ([Task reports](https://docs.snapfix.com/product/features/reports/task-reports.md)) | Yes, from the asset list ([Task reports](https://docs.snapfix.com/product/features/reports/task-reports.md)) |

## Screens

* [Asset reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/asset-reports.md): web.
* [Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md): the apps' asset lists and their menus.

## API and data

* [`multi_asset_report_excel`](https://docs.snapfix.com/engineering-reference/api/reports.md#post-actionmulti_asset_report_excel) makes the spreadsheet, with the [report filter fields](https://docs.snapfix.com/engineering-reference/api/reports.md#report-filter-fields); `business_uuids` holds asset registers.
* [`user_asset_reports`](https://docs.snapfix.com/engineering-reference/api/reports.md#post-actionuser_asset_reports) lists the reports, and [`delete_user_report`](https://docs.snapfix.com/engineering-reference/api/reports.md#post-actiondelete_user_report) deletes one.
* The registers for the filter: [`GET /v1/app/asset-regs`](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appasset-regs).
* The Android item makes no request.
* Tables: [`report_userreports`](https://docs.snapfix.com/engineering-reference/db/tables/report_userreports.md) (one row per report) and [`assetReg`](https://docs.snapfix.com/engineering-reference/db/tables/assetreg.md) (the registers).

## Depends on

* [Asset registers](https://docs.snapfix.com/product/features/assets/asset-registers.md): the registers in the filter and the assets in the file.
* [Asset tasks](https://docs.snapfix.com/product/features/assets/asset-tasks.md): the tasks that the Android export lists.
* [Task reports](https://docs.snapfix.com/product/features/reports/task-reports.md): the same page layout, list, download and delete rules.
* [Group members](https://docs.snapfix.com/product/features/groups/group-members.md): the `perJobReportGenerate` permission in each register.

## Edge cases

* **No report in the last 30 days:** the list says "No data available", with "0 of 0" ([Asset reports](https://docs.snapfix.com/how-the-apps-work/screens/reports/asset-reports.md#states)).
* **A register without the permission:** the report stops, and the alert names it.
* **A failed report:** its "Download" does nothing.
* **Android export:** it covers only the tasks the phone has loaded, and needs no connection to build; sharing it may.


---

# 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/product/features/reports/asset-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.
