> 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/exploracoes.md).
# Explorations
Inventory of Power BI Explorations, with status, authorship, access and dependencies.
The **Explorations** screen lists the Power BI *Explorations* (ad hoc analyses saved from a semantic model (the "Explore this data" experience)) that exist in the workspaces inventoried by Power Monitor.
**How to access:** menu *Governance › Reports › Explorations*. Available to all profiles.
Explorations inventory
## What it is for
* **Reconcile inventory and billing:** explorations are inventory items and, in monitored workspaces, count toward the Power Monitor item count. This screen lets you see exactly which ones they are.
* Discover ad hoc analyses created by users on top of corporate models: a good indicator of demand for new reports.
* See, in the *Dependencies* tab, which semantic model each exploration reads from.
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 › Explorations* and are available to all profiles.
### Date filters
**What it is:** the **Created on** and **Modified on** range filters, above the table.
**What it is for:** find explorations created in a period (for example, after the launch of a new model) or abandoned a long time ago.
**How to use:**
1. In the **Created on** or **Modified on** filters, above the table, fill in the start date, the end date, or both.
2. The table is filtered automatically and returns to the first page. Clear the dates to return to the full list.
**How it works:** the filter is applied to the list already loaded, without a new query to the server.
### Column filters and sorting
**What it is:** text boxes and a status list in the table header, and sorting by the column titles.
**What it is for:** find explorations from a workspace, from an author or in a specific status.
**How to use:**
1. Type the term in the filter box below the title of the **Name** (*Search by name*), **Workspace** (*Search by workspace*), **Created by** (*Search by creator*) or **Modified by** (*Search by modifier*) column. The table is filtered automatically.
2. In the **Status** column, choose **Active**, **Inactive** or **Unknown** from the list (*All statuses* removes the filter).
3. Click the title of the **Modified at** column (or any other). The first click sorts from most recent to oldest (descending); click again to reverse it.
**How it works:** default sort by **Modified at**, from most recent to oldest. 10 items per page.
### Explorations table
**What it is:** the list of explorations with location, status, authorship and dates.
**What it is for:** find out who creates ad hoc analyses and on which workspaces.
**How to use:** read the columns; click the row to open the details.
**How it works:**
| Column | Description |
| --------------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Name** | Name of the exploration. |
| **Workspace** | Workspace of the exploration. When the workspace name is not available, the column shows the workspace identifier (GUID). |
| **Status** | **Active**, **Inactive** or **Unknown**. |
| **Created by** | Account that created the exploration. |
| **Modified by** | Account of the last change. |
| **Created at** | Creation date. |
| **Modified at** | Date of the last change. |
| **⋮** | Row actions menu. |
Above the table there is a note stating that, when the workspace name is not returned, the column shows its identifier. That is why the **Workspace** filter is a text filter: you can type part of the name or of the identifier.
### 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), with the **Open details** item.
**What it is for:** go straight to a specific tab of the details.
Actions menu of an exploration
**How to use:**
1. Click the row's **⋮** button, or right-click the row.
2. Click **Open details** to open the **Overview** tab, or hover over it and choose **Overview**, **Users & Permissions** or **Dependencies**.
**How it works:** there is no "Open in Power BI" link on this screen.
### Details: Overview
**What it is:** the first tab of the details modal, with the properties of the exploration.
**What it is for:** check the identifier, workspace, dates, authors, tags and description, and copy the ID.
Exploration details: Overview
**How to use:**
1. Click the exploration 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:** it shows ID, Name, Type, State, Workspace, dates, authors, tags and description, when available. 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 exploration.
**What it is for:** check whether an ad hoc analysis on sensitive data is accessible to more people than it should be.
**How to use:**
1. In the exploration'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.
### Details: Dependencies
**What it is:** the tab with the **Depends on** and **Used by** lists, as declared by Fabric.
**What it is for:** discover which semantic model the exploration reads from: and, with that, which corporate models are being explored by users.
Exploration details: Dependencies
**How to use:**
1. In the exploration's **⋮** menu, hover over **Open details** and choose **Dependencies**.
2. **Depends on** shows the semantic model (or other artifact) that the exploration reads; **Used by** shows the artifacts that depend on it, if any.
**How it works:** dependencies that point to something outside the monitored scope appear as "Unidentified artifact". See [The details modal](/en/power-monitor/governanca/relatorios.md#the-details-modal).
## Rules and behavior
* There is no "Open in Power BI" link on this screen.
* **Scope:** this list **does not apply the monitored-workspaces restriction** and shows the explorations of all inventoried workspaces. Explorations deleted in the tenant are excluded, and users with restricted visibility see only those from the workspaces granted to them.
* If the list cannot be loaded, the screen shows "Could not load the explorations." with the **Retry** button.
* The other [common list rules](/en/power-monitor/governanca/relatorios.md#rules-that-apply-to-all-lists) also apply (updates through inventory scans, page lock).
## Related pages
* [Reports](/en/power-monitor/governanca/relatorios.md)
* [Metric Sets](/en/power-monitor/governanca/relatorios/conjuntos-de-metricas.md)
* [Semantic Models](/en/power-monitor/governanca/modelos-semanticos.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/exploracoes.md?ask=&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.
