> 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/show-asset-attribute-values-as-labels-asset-group-labels.md).

# Show asset attribute values as labels (Asset Group Labels)

Assets inside an asset group can carry attribute values — for example a sprinkler system's Sprinkler Type of Wet or Dry. Normally you'd open the asset group to see them. The Asset Group Labels setting surfaces the attributes you choose as labels, so their values are visible at a glance:

* On the property page, on each asset group's card in the Asset Groups section (for example "Sprinkler Type: Wet").
* When scheduling a visit, in the Additional Context panel's Asset Groups section — expand an equipment type and each group shows its labels under its name.

Asset group custom fields already appear as labels on the property page card; this setting adds asset attribute values alongside them.

> **Where to find it:** Settings > Asset Group Labels (under Asset Groups and Services)

## Choose which attributes show

1. Open **Settings > Asset Group Labels**. Each asset group type lists its asset types and their attributes.
2. Check every attribute you want shown as a label.
3. Click **Save**.

The choice applies business-wide. Saving requires the business profile setup permission (the same permission that manages custom fields); other settings users can view the page but not change it.

## How labels read

* A label shows the attribute name and value: "Sprinkler Type: Wet".
* When a group's assets have different values for the same attribute, the distinct values are combined into one label: "Sprinkler Type: Dry, Wet".
* For a multi-select attribute, each picked option counts as its own value. If one asset has "Wet" and another has "Wet, Dry", the label reads "Hazards: Dry, Wet". See [Pick several options on an asset (multi-select attributes)](/field-operations/assets/pick-several-options-on-an-asset-multi-select-attributes.md).
* Assets without a value are skipped; if no asset in a group has a value for any chosen attribute, the group simply shows no label.
* Yes/no attributes read "Yes" or "No", dates use your date format, and long text values are shortened.
* Photo attributes are not offered: a picture has no label text.

## Related guides

* [What an asset group page shows](/field-operations/assets/what-an-asset-group-page-shows.md)
* [See a property's equipment and asset groups](/customers-and-work/properties/see-a-propertys-equipment-and-asset-groups.md)
* [Create and manage custom fields](/administration/settings/create-and-manage-custom-fields.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/show-asset-attribute-values-as-labels-asset-group-labels.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.