> For the complete documentation index, see [llms.txt](https://docs.buildings.ability.abb/collection/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buildings.ability.abb/collection/platform/live-cockpit/widgets/predefined-widgets/asset-properties.md).

# Asset properties

Use the predefined **Asset properties** widget to display selected characteristics of one asset as a name/value list. For example, show a building's total area, floor count, occupancy capacity, and usage alongside its operational widgets.

## Prerequisites

* You can edit the target dashboard.
* You can access an asset with property attributes assigned to categories. Populate the properties you want to display on that asset.

The available categories and properties depend on the selected asset's template. If the expected choices are missing, check the asset's [template configuration](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/asset-core.md).

## Select the Asset and Properties

1. Open the [dashboard](https://docs.buildings.ability.abb/collection/platform/live-cockpit/add-widgets-to-the-dashboard.md) where you want to display the properties in **Live Cockpit** **\[A]**.
2. Select **+ Widget**.
3. Select **Asset properties** from **Builtin**.\
   ▷ The widget configuration opens.

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-3d954dd8c0c8c6600e75167bc3e0b1d9e8c5d335%2Fproperty-element-configuration.png?alt=media" alt="Predefined Asset properties widget configuration for Building 1 with four selected building properties and the asset selectors, category, attribute, row controls, and Add Widget button marked"><figcaption><p>Select the property rows for this dashboard widget.</p></figcaption></figure>

| Reference | Control                                  | Purpose                                                                                                             |
| --------- | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| **\[B]**  | **Primary asset (for title and alarms)** | Optional asset for the widget header and alarms. Set **Data source** separately to choose whose properties appear.  |
| **\[C]**  | **Data source**                          | The asset whose property values the widget displays. Each Asset properties widget uses one data-source asset.       |
| **\[D]**  | **Category**                             | Narrows the attribute choices to a property category from the selected asset's template.                            |
| **\[E]**  | **Attribute**                            | The property to display in this row. The figure marks **Usage** in the final row.                                   |
| **\[F]**  | **Add category and attribute**           | Adds another property row after you select a data source.                                                           |
| **\[G]**  | Remove row                               | Removes that property from the widget configuration, not from the asset. Available when there is more than one row. |
| **\[H]**  | **Add Widget**                           | Saves the configuration and adds the widget to the dashboard.                                                       |

4. Select the asset in **Data source** **\[C]**.
5. Select **Add category and attribute** **\[F]**.
6. Select a **Category** **\[D]**.
7. Select an **Attribute** **\[E]** from that category.
8. Repeat steps 5–7 for each additional property.\
   ◈ Rows appear in the order you configure them. Use the trash button **\[G]** to omit a property.
9. Set the optional **Primary asset** **\[B]**, **Width**, **Subtitle**, and **Description** as needed.
10. Select **Add Widget** **\[H]**.\
    ▷ The dashboard displays the selected properties.

Changing a row's category clears its attribute selection if that attribute does not belong to the new category. Select the property again before saving.

## Read the Result

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-9e57e3b7dc959e88f925bd90ec1b2c01889ffbf1%2Fproperty-element-result.png?alt=media" alt="Dashboard showing Building 1 properties: total area 4&#x27;956 square metres, floor count 5, occupancy capacity 83, and usage Mixed use"><figcaption><p>A populated Asset properties widget on a dashboard.</p></figcaption></figure>

The table **\[I]** lists the selected property names under **Category** and their current formatted values under **Property-Attribute**. Values include their configured units.

In this example, **Total Area** is `4'956 m²`, **Floor Count** is `5 count`, **Occupancy Capacity** is `83`, and **Usage** is `Mixed use`. Occupancy capacity describes the building's configured capacity; it is not a live occupancy count.

The widget displays `—` when a selected property has no value. If no asset is selected, it displays **Select an asset to display its properties**. If no property rows are configured, it displays **No properties configured**.


---

# 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.buildings.ability.abb/collection/platform/live-cockpit/widgets/predefined-widgets/asset-properties.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.
