> 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/layout-von-dashboards-anpassen.md).

# Adjust dashboard layout

You can customize how widgets are displayed on dashboards to suit your preferences.

### Move widgets

You can rearrange widgets by drag and drop.

### Masonry

Enable "Masonry" to position all widgets as space-efficiently as possible.

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/0GEDre9tOyQKoI7Yp7w7/414B6616-4F41-44A6-BAB6-109C627C22EE.png" alt=""><figcaption><p>Left: Masonry "OFF", Right: Masonry "ON".<br>Click the image to enlarge it</p></figcaption></figure></div>

{% hint style="warning" %}
**Note**:\
If Masonry is enabled, widgets can no longer be moved manually.
{% endhint %}

### Change widget size

You can determine how much horizontal space widgets should take up. This setting is more useful for some widgets than for others. Compare the size of the "Air conditioner" asset in the following screenshots:

{% @supademo/embed url="<https://app.supademo.com/demo/Wy7zYDeYGeQ_TKGN0mqL0>" demoId="Wy7zYDeYGeQ\_TKGN0mqL0" fullWidth="true" %}

1. Make sure you are in the "Dashboards" menu
2. In a widget: Click "More options"\
   ▷ The "More options" menu opens
3. Click "Change size"\
   ▷ The available sizes are displayed
4. Click the desired size\
   ▷ The widget is displayed in the desired size


---

# 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/layout-von-dashboards-anpassen.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.