> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/field-operations/assets/files-on-an-asset-group.md).

# Files on an asset group

Asset groups have a **Files** tab where you can keep documents tied to that equipment — photos, manuals, inspection certificates, warranties, and the like. It works the same way as files on a property, including who is allowed to see each file.

> **Where to find it:** An asset group's page, the **Files** tab (next to Assets)

## Add a file

1. Open the asset group and switch to the **Files** tab.
2. Choose **Add**.
3. Pick the file, give it a name, and set its visibility (see below).
4. Save. The file is attached to the asset group and appears for anyone whose access includes that visibility level.

## View files as a list or a gallery

The Files tab can show your files as a **list** or as a **gallery** of preview tiles. Use the toggle to switch between them — Essential remembers your choice for next time. You can also:

* **Search** by file name to filter the list.
* A download icon (tooltip "Download all files") downloads every file in the group at once. It only appears once the group has more than one file.
* Click a file to preview it.

## Who can see a file (visibility)

Each file has a visibility level that controls who can see it — the same three levels used for property files:

* **Back Office Only** — office staff with back-office file access.
* **Back Office + Technicians** — also visible to field technicians in the mobile app.
* **Back Office + Technicians + Customers** — also shared to the customer through the customer portal.

The levels you can choose from depend on your own permissions, and you can only widen visibility, not narrow it below what you can see yourself. The customer level only appears when your business has the customer portal enabled, and a specific customer must have portal access turned on to actually view a file shared with them. Small icons on each file show its current visibility at a glance. See [Property files and who can see them](/customers-and-work/properties/property-files-and-who-can-see-them.md) for the full explanation of the levels.

## On mobile

Field technicians see an asset group's files on the visit in the Essential mobile app, limited to the files their access allows, and can attach new files from there.

## Related guides

* [What an asset group page shows](/field-operations/assets/what-an-asset-group-page-shows.md)
* [Add or bulk-add assets to an asset group](/field-operations/assets/add-or-bulk-add-assets-to-an-asset-group.md)
* [Property files and who can see them](/customers-and-work/properties/property-files-and-who-can-see-them.md)


---

# 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://learn.withessential.com/field-operations/assets/files-on-an-asset-group.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.