> For the complete documentation index, see [llms.txt](https://docs.powermonitor.com.br/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.powermonitor.com.br/en/power-monitor/governanca/relatorios/dashboards.md).

# Dashboards

Inventory of the Power BI dashboards published in the monitored workspaces, with number of tiles, tags, access and a link to Power BI.

The **Dashboards** screen lists the dashboards (one-page canvases built with *tiles* pinned from reports) published in the monitored Power BI workspaces.

**How to access:** menu *Governance › Reports › Dashboards*. Available to all profiles.

<figure><picture><source srcset="/files/Zx4NvhGfdiDlouelxm0f" media="(prefers-color-scheme: dark)"><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-a65648b168eb3921c9e2936e0132e1b410e6a9c4%2Fpm-governanca-dashboards-en.png?alt=media" alt="Dashboards screen with the dashboards table, number of tiles and tags"></picture><figcaption><p>Dashboards inventory</p></figcaption></figure>

## What it is for

* Find out how many dashboards exist and in which workspaces: many environments accumulate old dashboards that nobody maintains anymore.
* Identify empty or nearly empty dashboards by the number of **Tiles**, candidates for removal.
* Check who has access to a dashboard before changing or deleting it.

The screen follows the [common structure of the Governance lists](/en/power-monitor/governanca/relatorios.md#common-structure-of-the-lists).

## Features

All the features below start from the menu *Governance › Reports › Dashboards* and are available to all profiles.

### Dashboards counter

**What it is:** the **Dashboards** badge, next to the section title, with the total number of dashboards in the list.

**What it is for:** gauge how many classic dashboards still exist in the environment, and how many remain after filtering by a workspace.

**How to use:** read the number on the badge; when you apply filters, it shows the total of the filtered subset.

**How it works:** it counts only dashboards from monitored workspaces that still exist in the tenant.

### Column filters and sorting

**What it is:** text boxes in the header of the **ID**, **Name** and **Workspace** columns, and sorting by the title of any column.

**What it is for:** find a dashboard and, by sorting by **Tiles**, bring empty or nearly empty dashboards to the top.

**How to use:**

1. Type the term in the filter box below the title of the **ID** (*Item ID*), **Name** (*Item name*) or **Workspace** (*Workspace name or ID*) column. The table is filtered automatically.
2. Click the column title (for example, **Tiles**). The first click sorts in descending order (dashboards with the most tiles first); click again to reverse it: this way empty or nearly empty dashboards appear at the top.

**How it works:** all columns are sortable. 10 items per page. This screen has no date filter.

### Dashboards table

**What it is:** the list of dashboards with identification, location, number of tiles and tags.

**What it is for:** assess the content of each dashboard without opening it.

**How to use:** read the columns; click the row to open the details.

**How it works:**

| Column        | Description                                     |
| ------------- | ----------------------------------------------- |
| **ID**        | Identifier (GUID) of the dashboard in Power BI. |
| **Name**      | Name of the dashboard.                          |
| **Workspace** | Workspace where the dashboard is located.       |
| **Tiles**     | Number of tiles in the dashboard.               |
| **Tags**      | Tags assigned to the dashboard in Power BI.     |
| **⋮**         | Row actions menu.                               |

This screen has no authorship or creation/modification date columns: the focus is on content (tiles and tags) and access.

### Actions menu

**What it is:** the menu opened by the **⋮** button at the end of each row (or by right-clicking anywhere on the row).

**What it is for:** reach the details tabs or open the dashboard in Power BI.

<figure><picture><source srcset="/files/sxRxWTE6OTkwpc2aC8oY" media="(prefers-color-scheme: dark)"><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-72441adce3526edca75213ddbd4e06851366b47d%2Fpm-governanca-dashboards-menu-acoes-en.png?alt=media" alt="Actions menu of a dashboard with the Open details submenu open"></picture><figcaption><p>Actions menu of a dashboard</p></figcaption></figure>

**How to use:**

1. Click the row's **⋮** button, or right-click the row.
2. Click **Open details** (or hover over it and choose **Overview** or **Users & Permissions**) or **Open in Power BI**.

**How it works:**

| Action               | What it does                                                            |
| -------------------- | ----------------------------------------------------------------------- |
| **Open details**     | Opens the details modal. Submenu: *Overview* and *Users & Permissions*. |
| **Open in Power BI** | Opens the dashboard in Power BI, in a new browser tab.                  |

### Details: Overview

**What it is:** the first tab of the details modal, with the properties of the dashboard.

**What it is for:** check the dashboard's identifier, workspace and tags, and copy the ID.

<figure><picture><source srcset="/files/CqRcMt3eNDz9tHTnPSIl" media="(prefers-color-scheme: dark)"><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-79d087bda5abb3c4371138f5af4e832403143377%2Fpm-governanca-dashboards-modal-visao-geral-en.png?alt=media" alt="Details modal of a dashboard on the Overview tab"></picture><figcaption><p>Dashboard details: Overview</p></figcaption></figure>

**How to use:**

1. Click the dashboard row, or the **⋮** button › **Open details**. The modal opens on the **Overview** tab.
2. Click **Copy** next to the ID to copy the identifier.

**How it works:** the tab shows ID, Name, Type, Workspace and Tags. See [The details modal](/en/power-monitor/governanca/relatorios.md#the-details-modal).

### Details: Users & Permissions

**What it is:** the tab that lists who has access to the dashboard.

**What it is for:** check who still uses a dashboard before changing or deleting it.

<figure><picture><source srcset="/files/RIDRTRBOf6Euy1vEiZ1I" media="(prefers-color-scheme: dark)"><img src="https://3938213054-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH2bFRBmIfyK3kwVKbldl%2Fuploads%2Fgit-blob-5042d07b5f747de5d55599126694674be6fad645%2Fpm-governanca-dashboards-modal-usuarios-en.png?alt=media" alt="Users &#x26; Permissions tab of a dashboard&#x27;s modal"></picture><figcaption><p>Dashboard details: Users &#x26; Permissions</p></figcaption></figure>

**How to use:**

1. In the dashboard's **⋮** menu, hover over **Open details** and choose **Users & Permissions**.
2. Use the search to find a user, group or application by name, email or identifier.

**How it works:** the table shows the **Principal Type**, the **Category** (Member or Guest/External) and the **Access Level** of each one. Dashboards do not have the *Dependencies* tab: they are not part of the dependency graph declared by Fabric.

### Open in Power BI

**What it is:** the **Open in Power BI** action in the **⋮** menu.

**What it is for:** go from the inventory straight to the dashboard in the portal.

**How to use:**

1. Click the **⋮** button at the end of the row, or right-click the row.
2. Click **Open in Power BI**. The dashboard opens in a new browser tab.

**How it works:** you need access to the dashboard in Power BI to view it.

## Rules and behavior

* This screen has no authorship or creation/modification date columns, and no date filter: the focus is on content (tiles and tags) and access.
* The [common list rules](/en/power-monitor/governanca/relatorios.md#rules-that-apply-to-all-lists) apply: only monitored workspaces, deleted artifacts are excluded, the user's workspace scope is respected and updates come from the inventory scans.

## Frequently asked questions

<details>

<summary>What is the difference between this screen and KQL Dashboards?</summary>

This screen lists the classic Power BI dashboards (tiles pinned from reports). **KQL Dashboards** are the Fabric real-time dashboards, which query KQL databases: they have their own screen in [KQL Dashboards](/en/power-monitor/governanca/relatorios/kql-dashboards.md).

</details>

## Related pages

* [Reports](/en/power-monitor/governanca/relatorios.md)
* [KQL Dashboards](/en/power-monitor/governanca/relatorios/kql-dashboards.md)
* [Apps](/en/power-monitor/governanca/relatorios/apps.md)


---

# 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.powermonitor.com.br/en/power-monitor/governanca/relatorios/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.