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

# Asset registers

{% 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-registers.md).
{% endhint %}

An **asset register** is a list of a site's **assets** of one kind, such as the boilers in a plant room, kept like a **group**. Each register has its own **attributes** (the fields every asset in it can have, such as a serial number or a QR code), its own status names, its own members and its own settings. Each asset has a photo or a large text, attribute values, a note, users, a checklist, documents, a message thread, and its tasks and planned tasks. Members create registers and assets, change an asset's status, lock, archive, copy, move or delete it, and manage a register's settings and members as they would a group's. In the data a register is a group of type `asset` and an asset is a task ([Assets API](https://docs.snapfix.com/engineering-reference/api/assets.md)), so the rules in [Tasks](https://docs.snapfix.com/product/features/tasks/tasks.md) apply to assets unless this page says otherwise. Linking assets to tasks is in [Asset tasks](https://docs.snapfix.com/product/features/assets/asset-tasks.md), and codes are in [Asset codes](https://docs.snapfix.com/product/features/assets/asset-codes.md).

## Rules

### Registers and who sees them

* A register belongs to one site. Its name is unique among the site's registers that are not deleted ([`POST /v1/app/asset-regs`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appasset-regs)).
* A user sees the registers they belong to on the site. In a multi-site view the web lists, for each site, every register except those the user was removed from, so registers of more than one site show \[[ASK-100](https://github.com/snapfix/docs/blob/main/ASK.md#ask-100-should-a-multi-site-member-see-every-asset-register-and-asset-of-the-multi-sites-sites)] ([Asset registers](https://docs.snapfix.com/how-the-apps-work/screens/assets/registers.md), [`GET /v1/app/asset-regs`](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appasset-regs)).
* Opening a register needs a live membership. The server also lets in a member of any multi-site, for any register ([`GET /v1/app/asset-regs/{uuid}`](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appasset-regsuuid)).
* The apps list the registers the user belongs to on the selected site, from the copy on the device.
* An archived register leaves the active list and shows only with the archived filter. It does not open on the web or on iOS, while its settings still open on the web; Android opens it ([Asset registers](https://docs.snapfix.com/how-the-apps-work/screens/assets/registers.md#platform-differences)).
* A member can mute a register's notifications, for themselves only ([Asset registers](https://docs.snapfix.com/how-the-apps-work/screens/assets/registers.md#actions)).

### Creating a register

* Creating a register needs the create flag of the user's site membership (`fCreateNewBusiness`). Without it the server refuses with `403`, and the web hides the "+" ([`POST /v1/app/asset-regs`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appasset-regs)).
* The apps decide who gets "+" in their own way: iOS shows it to admins of an asset register or a task group and to account admins \[[ASK-104](https://github.com/snapfix/docs/blob/main/ASK.md#ask-104-who-may-create-an-asset-register)], and its "+" menu item follows the right to create groups; Android shows the create item by the device's copy of the create flag, or to account admins ([Create a new asset register](https://docs.snapfix.com/how-the-apps-work/screens/assets/create-register.md)).
* The creator becomes the register's admin.
* The web creates the register on the server at once. The name stops at 100 characters, and a name that matches a register already loaded on the page, in any letter case, is refused before anything is sent; the server refuses a taken name too ([Asset registers](https://docs.snapfix.com/how-the-apps-work/screens/assets/registers.md#create-a-new-asset-register-web)).
* The apps create the register on the device, also offline, and the sync sends it later. iOS lets a name of only spaces through and saves it empty ([Create a new asset register](https://docs.snapfix.com/how-the-apps-work/screens/assets/create-register.md)).
* A new register copies its settings, statuses and sub-statuses from a template, without tag folders. It gets the description "New Asset", the status names "New assets", "Assets in progress" and "Completed assets" \[[ASK-103](https://github.com/snapfix/docs/blob/main/ASK.md#ask-103-should-a-new-asset-start-green)], and ten attributes, none mandatory: "Asset ID", "Description", "Type", "Manufacturer", "Model", "Location" and "Notes" (text), and "NFC", "QR" and "Barcode" in the category "Tracking". The server adds them for registers made on the web; the apps add them on the device ([`POST /v1/app/asset-regs`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appasset-regs), [Create a new asset register](https://docs.snapfix.com/how-the-apps-work/screens/assets/create-register.md#actions)).

### Settings and members

* The settings page is for users with the settings permission (`perBusSettingsScreenAccess`). Others get a read-only details dialog on the web, or the register's purpose page in the apps. On Android the row's button opens settings for admins only ([Asset register settings](https://docs.snapfix.com/how-the-apps-work/screens/assets/register-settings.md)).
* A register's settings are its details, status names, attributes, members, photo, manual NFC checks, camera-only photos, archive and delete. Registers have no tag folders and no group QR code, and the web's settings drawer leaves out the tag, checklist, task, report and room options of groups. The drawer is titled "Group Settings" ([Settings drawer](https://docs.snapfix.com/how-the-apps-work/screens/assets/register-settings.md#settings-drawer-web)).
* The server is looser than the page: any member who is not read-only can change or delete a register through the API. Who should be allowed to delete is open \[[ASK-97](https://github.com/snapfix/docs/blob/main/ASK.md#ask-97-who-may-change-and-delete-an-asset-register)] ([`PUT /v1/app/asset-regs/{uuid}`](https://docs.snapfix.com/engineering-reference/api/assets.md#put-v1appasset-regsuuid)).
* Deleting a register marks it deleted. Its assets, attributes and memberships stay as they are, although the web's info text says its tasks go too \[[ASK-99](https://github.com/snapfix/docs/blob/main/ASK.md#ask-99-what-should-deleting-an-asset-register-do-to-its-assets)] ([`DELETE /v1/app/asset-regs/{uuid}`](https://docs.snapfix.com/engineering-reference/api/assets.md#delete-v1appasset-regsuuid)).
* On the web, "Save" goes back to the previous page after 1.5 seconds, and a delete opens Fix.
* The members list shows each member's name, email and role, and the answer carries every member's phone number and address. Deleted profiles can appear in it ([`GET /v1/app/asset-regs/{uuid}/users`](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appasset-regsuuidusers)).

### Attributes

* An attribute has a name, a type ("Text", "Number", "Date", "Barcode", "QR" or "NFC") that cannot change once saved, a "Mandatory" switch and a category: "Attributes", or another such as "Tracking" ([Asset register settings](https://docs.snapfix.com/how-the-apps-work/screens/assets/register-settings.md#inputs)).
* An attribute name is unique in its register. The web checks it in any letter case against the attributes it has loaded; the server does not check it. An empty or taken name shows a message under the field once it has been left.
* Attributes are reordered by drag; the web saves the new order at once.
* Changing or deleting an attribute that assets have values for needs a second confirmation, which gives the number of assets. The count can include deleted assets. A change does not change the stored values ([`PUT /v1/app/asset-regs/{uuid}/attribute-rule`](https://docs.snapfix.com/engineering-reference/api/assets.md#put-v1appasset-regsuuidattribute-rule)).
* Deleting an attribute marks only the attribute deleted. The values stay in the database, and the assets stop showing them. The web's text says the attribute is removed from the assets that use it \[[ASK-102](https://github.com/snapfix/docs/blob/main/ASK.md#ask-102-should-deleting-an-attribute-rule-remove-its-values-from-the-assets)] ([`DELETE /v1/app/asset-regs/{uuid}/attribute-rule`](https://docs.snapfix.com/engineering-reference/api/assets.md#delete-v1appasset-regsuuidattribute-rule)).
* The delete dialogs can show stray markup ([Delete Attribute](https://docs.snapfix.com/how-the-apps-work/screens/assets/register-settings.md#delete-attribute-web)).
* Any signed-in user can add, change or delete any register's attributes through the API.
* Each asset holds one value per attribute. A mandatory attribute must have a value: the web and the apps check this before they save, and the server does not \[[ASK-98](https://github.com/snapfix/docs/blob/main/ASK.md#ask-98-should-the-server-refuse-an-asset-save-that-leaves-a-mandatory-attribute-empty)] ([Asset detail](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-detail.md#inputs), [Asset attributes](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-attributes.md#inputs)).
* Any signed-in user can change any asset's attribute values through the API ([`POST /v1/app/assets/save-attributes`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassetssave-attributes)).

### Assets

* Creating an asset needs "Create New Task" in the register, or the admin role, and a member who is not read-only ([`POST /v1/app/assets`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassets)). The web's "+" opens "Add an Asset"; iOS starts from the camera button and checks the site's task limit first; Android uses "Create a new Asset" in its "+" menu; the apps also create an asset from a scan ([Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md#actions), [Asset codes](https://docs.snapfix.com/product/features/assets/asset-codes.md)).
* A new asset has a title and a photo or a large text. It starts green with the sub-status "New" and gets an eight-digit reference number \[[ASK-103](https://github.com/snapfix/docs/blob/main/ASK.md#ask-103-should-a-new-asset-start-green)].
* When the register has a mandatory attribute, the web asks for it before saving, then saves the values in a second request after the asset ([Add an Asset](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md#add-an-asset-web)).
* A member sees an asset when they are an admin of the register, have "View All Tasks", created it, or are assigned to it or follow it. Lists hold only those assets. A multi-site user of the register's site sees every asset \[[ASK-100](https://github.com/snapfix/docs/blob/main/ASK.md#ask-100-should-a-multi-site-member-see-every-asset-register-and-asset-of-the-multi-sites-sites)] ([`GET /v1/app/assets/{uuid}`](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appassetsuuid)).
* Changes follow the register's task permissions ([`PUT /v1/app/assets/{uuid}`](https://docs.snapfix.com/engineering-reference/api/assets.md#put-v1appassetsuuid)):
  * a colour needs the "move to" permission for that colour, and green is refused for an asset with an unfinished checklist when the register blocks that;
  * lock needs an admin of the register or the asset's creator;
  * archive needs "Delete or Archive Tasks" or the admin role, and so does delete;
  * every change needs a member who can see the asset and is not read-only. A locked asset refuses changes except unlocking, and an archived one is read-only.
* "Duplicate Asset (all messages)" and "Duplicate Asset (no messages)" copy the asset into its own register, with " Copy" added to the title ([Asset detail](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-detail.md#actions)).
* "Copy Asset to Register" and "Move Asset to Register" go to another register of the same site. The server needs an admin of the asset's register who is a member of the target. The dialog says the user must be an admin of both, while the web checks admin here and "Create New Task" in the target \[[ASK-21](https://github.com/snapfix/docs/blob/main/ASK.md#ask-21-who-may-copy-or-move-a-task-and-what-should-the-tag-options-do)] ([Copy or move](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-detail.md#copy-or-move-web)).
* Within its own register a copy or a move checks nothing on the server, so any signed-in user who knows the asset's ID can copy it, and a move deletes the original.
* A copy takes the checklist, the attribute values (matched by name in another register), the asset's task links, schedules, time and cost, and the users who are members of the target. A move makes a new asset, with a new ID and reference number, and deletes the original ([`POST /v1/app/assets/copy`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassetscopy), [`POST /v1/app/assets/move`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassetsmove)).
* "Share" offers "Asset Report" and "Asset URL", as for tasks. The URL keeps working after the asset is deleted or moved, until it expires ([Task sharing](https://docs.snapfix.com/product/features/tasks/task-sharing.md)).
* A new photo is checked for size only, not for file type.
* The asset's messages use the task chat. Any signed-in user who knows the asset's ID can read them, and read-only members can post \[[ASK-44](https://github.com/snapfix/docs/blob/main/ASK.md#ask-44-should-read-only-members-post-react-and-delete-chat-messages)] ([Task chat](https://docs.snapfix.com/product/features/chat/task-chat.md)).
* Deleting an asset marks it deleted. Its links stay in the database, but tasks stop listing it, and the scheduler stops linking new planned tasks to it (api\_php\_live\_v2 @ ef3c4319f6, `app/Models/JobModel.php:419-428` with the soft-delete scope of `app/Models/BaseModel.php:15`; py\_scheduler @ c8b1344036, `models/feature_job_from_scheduler.py:663-697`). The dialog says the asset "will be removed from all tasks and schedules it is associated with" ([`DELETE /v1/app/assets/{uuid}`](https://docs.snapfix.com/engineering-reference/api/assets.md#delete-v1appassetsuuid)).

### Bulk actions

* The web changes the status or priority of many assets at once, adds a checklist, or archives, locks or deletes them, for the selected assets or for every asset that matches the filters ([Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md#actions), [Multi-select](https://docs.snapfix.com/product/features/tasks/multi-select.md)).
* The bulk routes take asset IDs from any register. The bulk priority change checks no permission, and setting a priority skips assets that already have one. The bulk lock reaches only the assets whose register the caller is an admin of, or that they created.
* The apps have their own bulk sets; which set is intended is open \[[ASK-105](https://github.com/snapfix/docs/blob/main/ASK.md#ask-105-which-bulk-actions-should-assets-have-on-each-platform)] ([Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md#platform-differences)).
* The asset list API has no maximum page size.

### Plans and devices

* When the site's plan has no asset feature (`asset_enabled`), the apps show a "Learn more" card instead of the register list. iOS also refuses the asset picker ("Not included in this business account"), and its NFC scan on an asset needs `nfc_enabled`. The web checks neither \[[ASK-23](https://github.com/snapfix/docs/blob/main/ASK.md#ask-23-should-plan-limits-be-enforced-on-the-web-and-the-server)] ([Asset registers](https://docs.snapfix.com/how-the-apps-work/screens/assets/registers.md#states)).
* The apps keep registers, assets, attributes and values on the device and sync them later.
* For app versions above 6.10.5, the sync also sends every live asset register of the user's sites, with the membership rows and the user rows of all their members, not only the registers the user belongs to (php-apis @ 238ca4414e, `htmlphp/api/snapfix/class/class.functions.php:30099-30110`).
* The apps always show 0 new activity for registers.
* The old asset tables ([`assetReg`](https://docs.snapfix.com/engineering-reference/db/tables/assetreg.md) and its siblings) belong to an old iOS picker that no button opens ([Select asset register](https://docs.snapfix.com/how-the-apps-work/screens/assets/select-asset.md#old-ios-picker)).

## Flow

```mermaid
flowchart LR
    list["Asset registers"] --> create["Create a register (create flag)"]
    create --> defaults["Template statuses and ten default attributes"]
    list --> settings["Settings: details, attributes, members, archive, delete"]
    list --> open["Open a register: asset list"]
    open --> newasset["Create an asset"]
    newasset --> mandatory{"Mandatory attributes?"}
    mandatory -- yes --> values["Fill them in"]
    mandatory -- no --> asset["Asset"]
    values --> asset
    open --> asset
    asset --> change["Status, lock, archive, delete"]
    asset --> copy["Duplicate, copy or move within the site"]
    asset --> work["Tasks, codes, documents, messages"]
```

## Platforms

| Capability                     | Web                                                                                                                                                | iOS                                                                                                                                                   | Android                                     |
| ------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------- |
| Register list                  | From the server, paged, list or grid                                                                                                               | From the device copy                                                                                                                                  | From the device copy                        |
| Create a register              | Dialog, saved on the server at once                                                                                                                | Screen, saved on the device and synced                                                                                                                | Screen, saved on the device and synced      |
| Who gets "+"                   | The server's create flag                                                                                                                           | Register or task group admins, account admins \[[ASK-104](https://github.com/snapfix/docs/blob/main/ASK.md#ask-104-who-may-create-an-asset-register)] | The device's create flag, or account admins |
| Archived register              | Does not open                                                                                                                                      | Does not open                                                                                                                                         | Opens                                       |
| Settings from the list         | Settings permission                                                                                                                                | Admin or settings permission                                                                                                                          | Admins only                                 |
| Attributes                     | Saved on the server at once                                                                                                                        | Saved on the device, then synced                                                                                                                      | Saved on the device, then synced            |
| Create an asset                | "+" opens "Add an Asset"                                                                                                                           | Camera button, or a scan                                                                                                                              | "Create a new Asset", or a scan             |
| Copy, move, duplicate          | "Actions" menu                                                                                                                                     | Header menu                                                                                                                                           | Header menu                                 |
| Bulk actions                   | Status, priority, checklist, archive, lock, delete                                                                                                 | Also users, tags, reminders, adding assets, copy and move                                                                                             | Mark all as read, archive and delete        |
| Without the asset plan feature | Registers still show \[[ASK-23](https://github.com/snapfix/docs/blob/main/ASK.md#ask-23-should-plan-limits-be-enforced-on-the-web-and-the-server)] | "Learn more"                                                                                                                                          | "Learn more"                                |
| Offline                        | No                                                                                                                                                 | Yes, synced later                                                                                                                                     | Yes, synced later                           |

## Screens

* [Asset registers](https://docs.snapfix.com/how-the-apps-work/screens/assets/registers.md)
* [Create a new asset register](https://docs.snapfix.com/how-the-apps-work/screens/assets/create-register.md)
* [Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md)
* [Asset detail](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-detail.md)
* [Asset register settings](https://docs.snapfix.com/how-the-apps-work/screens/assets/register-settings.md)
* [Asset attributes](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-attributes.md)

## API and data

* [Assets API](https://docs.snapfix.com/engineering-reference/api/assets.md), registers: [`GET`](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appasset-regs) and [`POST /v1/app/asset-regs`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appasset-regs); [`GET`](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appasset-regsuuid), [`PUT`](https://docs.snapfix.com/engineering-reference/api/assets.md#put-v1appasset-regsuuid) and [`DELETE /v1/app/asset-regs/{uuid}`](https://docs.snapfix.com/engineering-reference/api/assets.md#delete-v1appasset-regsuuid); [members](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appasset-regsuuidusers).
* Attributes: [list](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appasset-regsuuidattribute-rules), [add](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appasset-regsuuidattribute-rule), [change or reorder](https://docs.snapfix.com/engineering-reference/api/assets.md#put-v1appasset-regsuuidattribute-rule) and [delete](https://docs.snapfix.com/engineering-reference/api/assets.md#delete-v1appasset-regsuuidattribute-rule); an asset's values with [`POST /v1/app/assets/save-attributes`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassetssave-attributes).
* Assets: [list](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassetslist), [create](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassets), [get](https://docs.snapfix.com/engineering-reference/api/assets.md#get-v1appassetsuuid), [change](https://docs.snapfix.com/engineering-reference/api/assets.md#put-v1appassetsuuid), [delete](https://docs.snapfix.com/engineering-reference/api/assets.md#delete-v1appassetsuuid), [copy](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassetscopy), [move](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassetsmove), and the bulk routes `multi/*` and `all/*`, from [`POST /v1/app/assets/multi/archive`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-v1appassetsmultiarchive) on.
* Mute and unmute: `PUT /v1/app/notification/{businessUuid}/mute` and `unmute` ([Notifications API](https://docs.snapfix.com/engineering-reference/api/notifications.md)).
* Apps: registers, assets, attributes and values sync through the `save_pri_*` actions, including [`?action=save_pri_businessjobattributerule`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-actionsave_pri_businessjobattributerule) and [`?action=save_pri_jobattribute`](https://docs.snapfix.com/engineering-reference/api/assets.md#post-actionsave_pri_jobattribute), and download through [`?action=read_parent_business_data_v2`](https://docs.snapfix.com/engineering-reference/api/groups.md#post-actionread_parent_business_data_v2).
* Snapfix AI reads registers and assets ([Assets API](https://docs.snapfix.com/engineering-reference/api/assets.md)).
* Tables: [`tPri_Business`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_business.md) (the register, type `asset`), [`tPri_SettingsBusiness`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_settingsbusiness.md), [`tPri_Status`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_status.md), [`tPri_UserBusiness`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userbusiness.md) (members), [`tPri_BusinessJobAttributeRule`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_businessjobattributerule.md) (attributes), [`tPri_Job`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_job.md) (assets) and [`tPri_JobAttribute`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_jobattribute.md) (values).

## Depends on

* [Tasks](https://docs.snapfix.com/product/features/tasks/tasks.md): an asset is a task, so its fields, permissions, checklist, approval, time and cost follow the task rules.
* [Groups](https://docs.snapfix.com/product/features/groups/groups.md) and [Group members](https://docs.snapfix.com/product/features/groups/group-members.md): registers are kept like groups, with the same settings pattern, roles and permissions.
* [Task chat](https://docs.snapfix.com/product/features/chat/task-chat.md): the asset's messages and documents.
* [Checklists](https://docs.snapfix.com/product/features/checklists/checklists.md): an asset's checklist, and the register setting that blocks green until it is done.
* [Multi-select](https://docs.snapfix.com/product/features/tasks/multi-select.md): bulk changes to many assets.
* [Task sharing](https://docs.snapfix.com/product/features/tasks/task-sharing.md): "Share Asset".
* [Asset tasks](https://docs.snapfix.com/product/features/assets/asset-tasks.md) and [Asset codes](https://docs.snapfix.com/product/features/assets/asset-codes.md): an asset's tasks, planned tasks and codes.
* [Asset reports](https://docs.snapfix.com/product/features/reports/asset-reports.md): the spreadsheet of a register's assets.
* [Push notifications](https://docs.snapfix.com/product/features/notifications/push-notifications.md): asset changes push as task changes do.
* [Site switching](https://docs.snapfix.com/product/features/groups/site-switching.md) and [Multi-site console](https://docs.snapfix.com/product/features/console/multi-site-console.md): registers in a multi-site view.
* [Snapfix AI](https://docs.snapfix.com/product/features/ai/snapfix-ai.md): reads registers and assets.
* [Subscriptions](https://docs.snapfix.com/product/features/billing/subscriptions.md): the plan features `asset_enabled` and `nfc_enabled` \[[ASK-23](https://github.com/snapfix/docs/blob/main/ASK.md#ask-23-should-plan-limits-be-enforced-on-the-web-and-the-server)].

## Edge cases

* **Offline (apps):** registers, assets, attributes and values are created and changed on the phone and synced later. The web needs a connection, and a failed register list shows no message ([Asset registers](https://docs.snapfix.com/how-the-apps-work/screens/assets/registers.md#states)).
* **Missing permission:** the "+" and the settings are hidden from users who may not use them. The server's own checks are looser for register changes and deletes, attributes, attribute values and copies within a register.
* **Archived or locked asset:** it refuses changes; archived assets leave the list until the archived filter is on ([Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md#inputs)).
* **Deleted register:** a register that cannot be read sends the user back to the register list ([Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md#actions)).
* **Empty register:** the web shows "Manage your Assets in a Snap!", and the "+" in its sentence does nothing. A search or filter with no match shows the same text ([Asset list](https://docs.snapfix.com/how-the-apps-work/screens/assets/asset-list.md#states)).
* **Android Plan tab:** tapping Plan while Assets is open can switch to another Plan page.
* **Several sites:** registers belong to one site, names are unique within it, and copies and moves stay within it.
* **Time zones:** date attributes are stored as epoch milliseconds; the shared task page can show an asset date in the wrong year.
* **Limits:** the register and asset lists have no maximum page size.


---

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