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

# Global dashboards

## Also called Public or Project dashboards

## About Global Dashboards

With “Global Dashboards,” you can create a single dashboard and then share that dashboard with as many users as you like. Changes to this dashboard can only be made by you.

## Create a global dashboard

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/YmP5GjnpjRRP1C3xQgbR/Docs_Dashboards%20Globale%20Dashboards%201.png" alt=""><figcaption></figcaption></figure>

### Create a global dashboard

1. Make sure that you are in the “Dashboards” menu
2. Click on **\[A1]**\
   ▷ The “Add dashboard **\[A2]**” window opens
3. Click on **\[A4]**
4. Give the dashboard in **\[A5]** a name
5. Click on **\[A6]**\
   ▷ The Global Dashboard is created

## Manage Global Dashboards

Global Dashboards are stored in a separate folder in the [↗ dashboard collection](/collection/english-v14/documentation/dashboard/dashboards-organisieren.md) stored.

<figure><img src="https://content.gitbook.com/content/Nyvwhz1kEMXcHf4HLuZ8/blobs/RlgNaF17kxh8TLjger7H/Docs_Dashboards%20Globale%20Dashboards%202.png" alt=""><figcaption></figcaption></figure>

Global Dashboards are marked with a blue dot.

**\[B]**: Global Dashboards

**\[C]**: Normal Dashboards


---

# 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/globale-dashboards.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.