> 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/platform/live-cockpit/global-dashboards.md).

# Global Dashboards

## Also known as Public or Tenant Dashboards

## About Global Dashboards

With "Global Dashboards," you can create a single dashboard and share it with users in the same tenant. Unlike [↗ copying dashboards to users](https://docs.buildings.ability.abb/collection/platform/live-cockpit/copy-dashboards-to-users.md), this shares the dashboard itself, not disconnected copies.

Users with **Read** permission for dashboards can view public dashboards. To create a public dashboard or manage its widgets and date settings, your role needs **Manage** permission for dashboards. Users with this permission can manage the content of public dashboards they can access, even if someone else created them. See [↗ Roles](https://docs.buildings.ability.abb/collection/mandatory-base/platform-core/workspace-and-identity/roles.md).

You can restrict a public dashboard's visibility by assigning an asset. Users without access to that asset do not see the dashboard. Leave **Asset** empty when you do not need this additional restriction.

Access to a dashboard does not grant access to the assets used in its widgets. Widget titles and descriptions can remain visible while asset data is hidden from users without permission for those assets.

## Create a Global Dashboard

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-31af0984b4ef513b1cb3a4a4d92e1228b71f1078%2Fglobal-dashboards-collection.png?alt=media" alt="Live Cockpit dashboard collection showing private dashboards and a public dashboard assigned to an asset"><figcaption><p>Dashboard collection and public dashboard visibility</p></figcaption></figure>

<figure><img src="https://2013058394-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FOqGnkz52o2zVUsEGEZGk%2Fuploads%2Fgit-blob-d0de3f019f58e57afd382187bfd9bdba9ea41cf2%2Fglobal-dashboards-create.png?alt=media" alt="Add dashboard dialog with Public selected, a dashboard name, and an optional assigned asset"><figcaption><p>Create a public dashboard with asset-based access</p></figcaption></figure>

#### Create a global dashboard

1. Open **Live Cockpit** **\[A]**.
2. Click **+ Dashboard** **\[B]**.\
   ▷ The **Add dashboard** dialog opens.
3. Select **Public** in **Type** **\[F]**.
4. Enter a dashboard name in **Name** **\[G]**.
5. Optionally select an asset in **Asset** **\[H]** to restrict who can see the dashboard.
6. Click **Confirm** **\[I]**.\
   ▷ The public dashboard is created.

To fill the dashboard with content, [↗ add widgets to the dashboard](https://docs.buildings.ability.abb/collection/platform/live-cockpit/add-widgets-to-the-dashboard.md).

## Manage Global Dashboards

Global dashboards are saved in the **Public dashboards** folder **\[C]** in the [↗ Dashboard collection](https://docs.buildings.ability.abb/collection/platform/live-cockpit/organize-dashboards.md), shown above. Expand the folder and select a dashboard to open it.

* **Asset** **\[D]** shows the asset assigned to the dashboard. Its access rights determine which users can see the dashboard.
* **Type** **\[E]** distinguishes **Public** and **Private** dashboards. Public dashboards also have a blue dot next to their icon.

Users without **Manage** permission view public dashboards without changing their widgets or date settings. Users with **Manage** permission can add, edit, and delete widgets on public dashboards they can access, including widgets created by another 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/platform/live-cockpit/global-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.
