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

# Dashboard templates import/export

Some [↗ Apps](/collection/english-v14/documentation/einstellungen/apps.md) provide so-called *Dashboard Templates* are available.

*Dashboard Templates* are preconfigured dashboards that are specifically tailored to the use of the corresponding app.

{% hint style="info" %}
Apps can provide one or more *Dashboard Templates* provide.
{% endhint %}

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/icdbC7IKxthcJ18dzuIw/Docs%20-%20App%20Dashboards.png" alt=""><figcaption></figcaption></figure></div>

Proceed as follows to create a dashboard template:

1. Make sure you are in the menu **Dashboards \[A]** are
2. Click on **Copy to users \[B]**
3. Click on **Apps \[D]**
4. Select in **\[D]** the app whose dashboard template you want to use.
5. Select in **\[E]** the dashboard template you want to use
6. Select in **\[F]** one or more users to whom you want to copy this dashboard.
7. Click on **Copy dashboards \[G]**\
   ▷ The *Dashboard Template* appears in the [↗ dashboard list](/collection/english-v14/documentation/dashboard/dashboards-organisieren.md) of the selected users.

## Export dashboard as JSON

<div data-full-width="true"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/frscudhDdklPffCsdciL/Dashboard%20export.png" alt=""><figcaption></figcaption></figure></div>

You can export a dashboard in JSON format to reuse it later or import it into another project.

Here's how:

1. Open the desired dashboard.
2. Click the menu *More options* \[A].
3. Select **Export to JSON** \[B].\
   ▷ A `.json`-file is automatically downloaded. This file contains the complete configuration of the dashboard.

With this file, the dashboard can later be imported again or transferred between systems.

## Import dashboard from JSON

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/RwP4fYVJgJWsB9F45pTu/Dashboard%20import.png" alt=""><figcaption></figcaption></figure>

<div align="left"><figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/Mebovnyl7KXKJfNHk9aW/Dashboard%20import%20(1).png" alt="" width="375"><figcaption></figcaption></figure></div>

You can import an externally created or exported dashboard as a `.json`-file.

Here's how:

1. Open the menu *Dashboards*.
2. Click on **Import** \[C].
3. Select the desired `.json`-file from your system.
4. Click again on **Import**.

▷ The dashboard now appears in your list and can be edited as usual.


---

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