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

# Assets 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/assets/README.md).
{% endhint %}

The asset register, the assets in it and their tasks, and the barcodes, QR codes and NFC tags (Smart Tags) on assets.

An asset register is a group of type `asset`, and an asset is a task in it, so these screens reuse the group and task screens with asset wording: the register list is the [group list](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-list.md) in asset mode, the register settings are [Group settings](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-settings.md) with attributes in place of tag folders, and the asset page reuses the parts of [Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md). Linking assets to a task starts on the task ([Task detail](https://docs.snapfix.com/how-the-apps-work/screens/tasks/task-detail.md#assets)). The web talks to the [Assets API](https://docs.snapfix.com/engineering-reference/api/assets.md); the apps work on their device copy and sync it.

| Screen                                                                                                      | Platforms         | Where                                                                                                                   |
| ----------------------------------------------------------------------------------------------------------- | ----------------- | ----------------------------------------------------------------------------------------------------------------------- |
| [Asset registers](https://docs.snapfix.com/how-the-apps-work/screens/assets/registers.md)                   | web, ios, android | web `/assets`; iOS and Android: Plan > asset registers; side menu "Assets"                                              |
| [Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md)                       | web, ios, android | web `/asset-register/:id/assets`; iOS and Android: an asset register                                                    |
| [Asset detail](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-detail.md)                   | web, ios, android | web `/asset-register/:id/asset/:assetId`; iOS and Android: an asset, or a scanned code                                  |
| [Asset register settings](https://docs.snapfix.com/how-the-apps-work/screens/assets/register-settings.md)   | web, ios, android | web `/asset-register/:id/settings`; iOS and Android: a register row's settings button; Android also the asset list menu |
| [Create a new asset register](https://docs.snapfix.com/how-the-apps-work/screens/assets/create-register.md) | ios, android      | iOS and Android: asset registers, "+"                                                                                   |
| [Asset attributes](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-attributes.md)           | ios, android      | iOS and Android: creating an asset, or a task in an asset register                                                      |
| [Select asset register](https://docs.snapfix.com/how-the-apps-work/screens/assets/select-asset.md)          | ios, android      | iOS: a task's "+" menu, "Add Assets"; Android: the task's tagging sheet; tagging a new task or a planned task           |
| [Code scanner](https://docs.snapfix.com/how-the-apps-work/screens/assets/code-scanner.md)                   | ios, android      | iOS and Android: scan buttons and "+" menus ("Scan Asset QR or Barcode"); asset attributes                              |


---

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