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

# Dashboard

## What is a dashboard?

The dashboard is the first thing you see when you log in to eliona.

Dashboards are graphical interfaces on which you can see values, make settings, and recognize relationships.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/HlAdMw72D050aIfFCFy0/0E7BC01C-A571-4648-A056-A7670B45E64B.png" alt=""><figcaption><p>A dashboard with various widgets</p></figcaption></figure></div>

<table><thead><tr><th width="81.33333333333331"></th><th width="294"></th><th></th></tr></thead><tbody><tr><td><strong>[A]</strong></td><td>Menu item "Dashboards"</td><td>Click here to open the current dashboard</td></tr><tr><td><strong>[B]</strong></td><td>To the dashboard collection</td><td>Click to show all available dashboards</td></tr><tr><td><strong>[C]</strong></td><td>Button "Create new dashboard"</td><td>Create new dashboard</td></tr><tr><td><strong>[D]</strong></td><td>Options</td><td><p>Available selection:</p><ul><li>Copy</li><li>Edit name</li><li>Add to bookmarks</li><li>Remove</li></ul></td></tr><tr><td><strong>[E]</strong></td><td>Copy to user</td><td>Copy current dashboard to a user</td></tr><tr><td><strong>[F]</strong></td><td>Widgets</td><td>Available <a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets.md">-> Widgets</a> show</td></tr><tr><td><strong>[G]</strong></td><td>Masonry Switch</td><td><a href="https://docs.buildings.ability.abb/collection/english-v14/documentation/dashboard/layout-von-dashboards-anpassen.md#masonry">-> enable Masonry layout</a> activate</td></tr></tbody></table>

Dashboards consist of so-called [-> Widgets](https://docs.buildings.ability.abb/collection/english-v14/documentation/widgets.md). You can individually "assemble" a dashboard from different widgets.

You can return to the dashboard at any time by clicking the **menu item** **Dashboard \[A]** in the sidebar.

### Multiple dashboards

You can create as many dashboards as you like and switch between these dashboards.

You are not tied to a single dashboard.

{% hint style="info" %}
**Example**\
You create a dashboard on which the current states of all blinds in your building are displayed.

In another dashboard, you display room temperatures and the status of existing air conditioning systems.

In yet another dashboard, you monitor the energy flows in the infrastructure.
{% endhint %}

You can [-> copy dashboards to other users](https://docs.buildings.ability.abb/collection/english-v14/documentation/dashboard/dashboards-an-benutzer-kopieren.md). This means you do not have to create dashboards that have already been created separately for each user.


---

# 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/dashboard.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.
