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

# Floor

The **Storey** widget displays a building's floor plans with the points, polygons, and readings configured for each floor. You can switch floors and categories within one widget.

Before you begin, [create the floors](https://docs.buildings.ability.abb/collection/platform/map-and-floor/floor/create-a-floor.md) under a building and [configure their points, polygons, and categories](https://docs.buildings.ability.abb/collection/platform/map-and-floor/floor/placing-assets-on-a-floor.md). The building must contain at least one configured floor.

## Configure Widget

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-504a3595fae4e19b77c46540368abd9c3606cd89%2Fstorey-widget-configuration.png?alt=media" alt="Storey widget configuration with a building selected and two automatically discovered floors, each with order and removal controls."><figcaption></figcaption></figure>

1. Open the dashboard where you want to [add the widget](https://docs.buildings.ability.abb/collection/platform/live-cockpit/add-widgets-to-the-dashboard.md).
2. Click **Widget**.
3. Select **Storey**.
4. Optional: Select a **Primary asset (for title and alarms)** **\[A]**.
5. Select the **Width** **\[B]**.
6. Optional: Enter a **Subtitle** or **Description** **\[C]**.\
   ◈ Each text field has its own switch to show or hide it.
7. Select a building under **Storeys assets to show in the widget** **\[D]**.\
   ▷ The building's configured floors are added to the list automatically.
8. Optional: Drag the floor handles **\[E]** to change their order.
9. Optional: Remove unwanted floors with their delete buttons **\[F]**.
10. Click **Add Widget** **\[G]**.\
    ▷ The widget displays the selected floors and their category-specific asset connections.

{% hint style="info" %}
To display alarm indications, enable **Show alarms** in the point's or polygon's configuration for the relevant category. See [Placing Assets on a Floor](https://docs.buildings.ability.abb/collection/platform/map-and-floor/floor/placing-assets-on-a-floor.md).
{% endhint %}

***

## Operate Widget

<div data-full-width="true"><figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-40139f617fe37aa842621aa44be872fee350db1a%2Fstorey-widget-navigation.png?alt=media" alt="Storey widget showing floor and category tabs, an Office A polygon with its reading, a point, and the Reset view button below the zoom controls."><figcaption></figcaption></figure></div>

Select a floor **\[H]**, then a category **\[I]** to see its connected assets. Colors follow the category's configuration, for example a value mapping for temperature.

<table data-full-width="true"><thead><tr><th width="80">Element</th><th width="180">Title</th><th>Details</th></tr></thead><tbody><tr><td><strong>[H]</strong></td><td>Floor tabs</td><td>Switch between the floors included in the widget. Their order follows the widget configuration.</td></tr><tr><td><strong>[I]</strong></td><td>Category tabs</td><td>Choose the selected floor's category. Only its connected geometry is displayed. These tabs appear when the floor has multiple categories.</td></tr><tr><td><strong>[J]</strong></td><td>Polygon and value</td><td>Display a configured area with its category-specific color, label, and value. Value visibility follows the polygon's Show value setting.</td></tr><tr><td><strong>[K]</strong></td><td>Point</td><td>Display a connected asset at its configured position, using the category's color and alarm settings.</td></tr><tr><td><strong>[L]</strong></td><td>Zoom controls</td><td>Use + and − or the mouse wheel to zoom. You can drag the plan to pan. Zooming out stops at the default zoom level.</td></tr><tr><td><strong>[M]</strong></td><td>More options</td><td>Open additional widget actions.</td></tr><tr><td><strong>[N]</strong></td><td>Reset view</td><td>Click <strong>Reset view</strong> below + and − to restore the floor plan's original zoom and position after zooming or dragging.</td></tr></tbody></table>

## Placement of Assets

Configure the shared geometry and the asset, attribute, colors, labels, and alarms for each category in **Map & storey**.

Learn more in [Placing Assets on a Floor](https://docs.buildings.ability.abb/collection/platform/map-and-floor/floor/placing-assets-on-a-floor.md).

## Customize the Floor Image

The widget displays each floor with the image stored in the corresponding floor asset.

You can find out how to assign an image to a floor or change an existing image under [-> Create a floor](https://docs.buildings.ability.abb/collection/platform/map-and-floor/floor/create-a-floor.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://docs.buildings.ability.abb/collection/platform/live-cockpit/widgets/predefined-widgets/floor.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.
