> 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/english-v14/documentation/widgets/widgets-bedienen.md).

# Operate widgets

## Widget options

You can access additional options for each widget.

Click the button on any widget **\[A]**, to show more options.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/LxDltYAvAnnNNsLHyARg/1F25F736-D196-4AAB-8429-E9C914F8B8E6.png" alt=""><figcaption><p>The "Show widget options" button. Works with all available widgets.<br>Shown here by way of example on a widget for Analog Trends.</p></figcaption></figure></div>

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/qvdcv8m29sGixFJMkRZ1/0E205E95-B722-4347-A19F-15EA91266DAD.png" alt=""><figcaption><p>The widget options</p></figcaption></figure></div>

<table><thead><tr><th width="84.33333333333331"></th><th></th><th></th></tr></thead><tbody><tr><td><strong>[B]</strong></td><td>Go to...</td><td>Opens available points related to the widget. More details see <a href="#ueber-widgets-navigieren">-> Navigate through widgets</a></td></tr><tr><td><strong>[C]</strong></td><td>Edit</td><td>This item allows you to make changes to the widget contents.</td></tr><tr><td><strong>[D]</strong></td><td>Create analytic</td><td>Creates an analytic for the selected widget</td></tr><tr><td><strong>[E]</strong></td><td>Resize</td><td>Changes the size of the widget</td></tr><tr><td><strong>[F]</strong></td><td>Remove</td><td>Removes the widget from the dashboard.<br>⚠ This action cannot be undone!</td></tr></tbody></table>

## Arrange widgets

See [↗ Organize dashboards](/collection/english-v14/documentation/dashboard/dashboards-organisieren.md).

## Navigate through widgets

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/zT4ofrcdMnRxePe4mzNe/Docs_Widgets%20-%20U%CC%88ber%20Widgets%20navigieren.png" alt=""><figcaption></figcaption></figure>

With the "Go to..." option, you can navigate directly from the widget to relevant settings.

<table><thead><tr><th width="82.33333333333331">Icon</th><th>Description</th><th>Details</th></tr></thead><tbody><tr><td><strong>A</strong></td><td>Alarm</td><td><a href="/collection/english-v14/documentation/alarme-regeln-und-eskalationen/alarme.md">-> Alarms</a> call up the primary asset</td></tr><tr><td><strong>B</strong></td><td>Ticket</td><td><a href="/collection/english-v14/documentation/tickets.md">-> Tickets</a> call up the primary asset</td></tr><tr><td><strong>C</strong></td><td>Rules</td><td><a href="/collection/english-v14/documentation/alarme-regeln-und-eskalationen/regeln.md">-> Rules</a> call up the primary asset</td></tr><tr><td><strong>D</strong></td><td>asset</td><td><a href="/collection/english-v14/documentation/assets/asset-details.md">-> asset details</a>call up the asset data of the primary asset</td></tr><tr><td><strong>E</strong></td><td>Data</td><td>-> call up the data of the primary asset</td></tr><tr><td><strong>F</strong></td><td>Analytics and reports</td><td><a href="/collection/english-v14/documentation/analytics-and-reports.md">-> Analytics and reports</a> call up the primary asset</td></tr><tr><td><strong>G</strong></td><td>Map</td><td><a href="/collection/english-v14/documentation/widgets/vordefinierte-widgets/karte.md">-> Map</a> call up the primary asset</td></tr><tr><td><strong>H</strong></td><td>BIM</td><td><a href="/collection/english-v14/documentation/bim.md">-> BIM</a> call up the primary asset</td></tr><tr><td><strong>I</strong></td><td>Digital Twin</td><td>The <a href="/collection/english-v14/documentation/digitaler-zwilling.md">-> Digital Twin</a> call up the primary asset</td></tr></tbody></table>

{% hint style="info" %}
Navigation always goes to the primary asset that has been defined for the respective widget.
{% endhint %}

## Add subtitle and description

For each widget, an additional **subtitle** and a **Description** can now be defined.\
These fields make it possible to provide the widget with additional information or context – visible directly in the widget itself.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/2YtsfqRne7fnfOdfspRU/Widget%20Untertitel%20Beschreibung.png" alt=""><figcaption></figcaption></figure>

* **subtitle**: Short, highlighted text below the widget title. Ideal for additional information such as location, device type, or status.
* **Description**: Free-text field for a more detailed explanation of the widget content, e.g. purpose, measurement range, or special notes.


---

# 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/english-v14/documentation/widgets/widgets-bedienen.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.
