> 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/auditoria/visualizacoes-de-relatorios.md).

# Report Views

Event-by-event trail of who viewed which reports and dashboards, when, through which path (portal, app or Power Embedded) and from where (country, state and city).

The **Report Views** screen shows, event by event, **who viewed which reports and dashboards, when and from where**. It is a subset of the [Events Overview](/en/power-monitor/auditoria/geral-de-eventos.md) that considers **only view events** (`ViewReport` and `ViewDashboard`) and adds the **location** of each access (country, state, city and internet provider) and the **path** used (portal, app or Power Embedded).

**How to access:** *Audit › Report Views*. Available to all profiles (read-only).

<figure><picture><source srcset="/files/plLPsnuzCW1OfGBHdhTL" 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-5b13df632c16867852d6e326625a04fde63f61cc%2Fpm-auditoria-visualizacoes-de-relatorios-en.png?alt=media" alt="Report Views screen with KPIs, filters and the list of views with country"></picture><figcaption><p>List of views with type, workspace and country</p></figcaption></figure>

## What it is for

* **Proving access**: "did the director open the closing report before the meeting?".
* **Report adoption**: who is actually using a new report and through which path (directly in the workspace, through an app or embedded via Power Embedded).
* **Security**: detecting access from unexpected countries or cities.
* **Basis for cleanup decisions**: confirming that a report has not been viewed for weeks before removing it.

{% hint style="info" %}
This screen is the **event-by-event** view. For rankings and aggregates (most accessed, most active users, access by month, by capacity, by country), use the [Report Access Dashboard](/en/power-monitor/dashboards/dashboard-de-visualizacoes.md): the **View insights** button takes you there (who can open it depends on the page access of the profile).
{% endhint %}

## Features

### View KPIs

**What it is:** three cards at the top: **Total Views**, **Active Users** and **Audited Workspaces**.

**What it is for:** measuring the reach of a report (or a set of reports) in the filtered period.

<figure><picture><source srcset="/files/S0zWRCX8KL9tOjQkeEDW" 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-db7ca9430587954f16f7646d550f80c730a5c024%2Fpm-auditoria-visualizacoes-de-relatorios-kpis-en.png?alt=media" alt="Total Views, Active Users and Audited Workspaces cards"></picture><figcaption><p>KPIs for the filtered period</p></figcaption></figure>

| KPI                    | Meaning                                |
| ---------------------- | -------------------------------------- |
| **Total Views**        | Number of views that match the filters |
| **Active Users**       | Distinct users who viewed              |
| **Audited Workspaces** | Distinct workspaces with views         |

**How it works:** the KPIs follow the filters, **except Country and City**, which restrict only the list. The cards are not clickable.

### Period (Start Date and End Date)

**What it is:** the **Start Date** and **End Date** fields in the filter bar.

**What it is for:** limiting the query to the range of interest (by default, the last 7 days).

<figure><picture><source srcset="/files/uGTuoVAL3QHAA89PIPJ1" 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-bcc0b83f46ea4a2a293d1b3ccd613c75922dcc94%2Fpm-auditoria-visualizacoes-de-relatorios-barra-filtros-en.png?alt=media" alt="Bar with Start Date, End Date, City, View insights, Export and Clear filters"></picture><figcaption><p>Filter bar and buttons</p></figcaption></figure>

**How to use:**

1. Click **Start Date** and choose the first day. The calendar only accepts dates within the period already collected.
2. Click **End Date** and choose the last day (considered up to 23:59:59, in your browser's time zone).
3. The KPIs and the list are updated automatically.

**How it works:**

* **Default period:** the screen opens with the last 7 days up to today and keeps that period even when the collection has not yet brought views from the last few hours.
* **Automatic adjustment:** only a date that **you chose** is adjusted to the available period.
* **Sorting:** changing the dates **does not change the sorting**. The list keeps the current order (by default, **Date/Time** from newest to oldest); to see the oldest first, click the **Date/Time** column title.

### Text and Status filters

**What it is:** the text boxes in the **User** (*Search by e-mail...*), **Artifact** (*Search artifact...*) and **Workspace** (*Search workspace...*) headers, and the **Status** list (All, Success, Failed).

**What it is for:** proving whether a person opened a report or seeing all accesses to an item or workspace.

**How to use:**

1. In the column header, type the text (or part of it). The list is updated as you type.
2. In **Status**, choose **All**, **Success** or **Failed**.

### Type filter (content and access path)

**What it is:** the **Type** multi-select (*All types*) in the **Type** column header.

**What it is for:** separating paginated reports from Power BI reports and dashboards, or seeing only accesses made through an app or through Power Embedded.

<figure><picture><source srcset="/files/2LFJqx17RGvdp6SSXavU" 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-1233ab88724a83263334c27aa26b31c63d194f7b%2Fpm-auditoria-visualizacoes-de-relatorios-filtro-tipo-en.png?alt=media" alt="Type filter open with Power BI Report, Paginated Report, Dashboard, Viewed via App and Viewed via Power Embedded"></picture><figcaption><p>Type filter options</p></figcaption></figure>

**How to use:**

1. In the **Type** header, click **All types**.
2. Select one or more options: **Power BI Report**, **Paginated Report**, **Dashboard**, **Viewed via App** or **Viewed via Power Embedded**.
3. The list is updated automatically.

**How it works:** the path options (*via App*, *via Power Embedded*) can be combined with the type options: the same access can be, for example, a Power BI report opened through an app. *Viewed via Power Embedded* identifies accesses by the embed Service Principal that were associated with a real user through the Power Embedded integration.

### Country and City filters

**What it is:** the **Country** multi-select (*All countries*), in the **Country** column header, and the **City** multi-select (*All cities*), in the filter bar.

**What it is for:** detecting access from unexpected countries or cities.

<figure><picture><source srcset="/files/x02RkejqZ9JOnSBtj7Lj" 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-c4e2e90b9a014f1fa1c4a628de42221dd4a7ef7e%2Fpm-auditoria-visualizacoes-de-relatorios-filtro-pais-en.png?alt=media" alt="Country filter open with the countries identified in the accesses"></picture><figcaption><p>Country filter</p></figcaption></figure>

**How to use:**

1. For country: in the **Country** header, click **All countries** and select the countries you want (the list shows the countries already identified in the accesses).
2. For city: in the filter bar, click **City**, search and select the cities.
3. Open the details of an access to see **State**, **City**, **ISP** and the **Client IP**.

{% hint style="warning" %}
The Country and City filters apply only to the list: the KPIs and the export still consider all countries and cities. Accesses from a private IP or not yet geolocated do not appear when these filters are active.
{% endhint %}

### Clear filters

**What it is:** the **Clear filters** button, with the number of active filters.

**What it is for:** returning to the full list for the period with one click.

**How to use:** click **Clear filters**. User, artifact, type, workspace, status, country and city are removed; the period is kept. The button is disabled when no filters are active.

### Views list

**What it is:** the table with one view per row, 20 per page by default, with the **Items per page** selector (10, 25, 50 or 100).

**What it is for:** seeing each opening of a report or dashboard, with date/time, user, path and country.

| Column        | Content                                                                                                                             |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Date/Time** | Date and time of the view, in your time zone                                                                                        |
| **User**      | Who viewed it. For accesses via Power Embedded, the real user resolved by the integration, with the indication *via Power Embedded* |
| **Artifact**  | Report or dashboard viewed; when the access was through an app, *via App: {app}* is shown                                           |
| **Type**      | Power BI Report, Paginated Report or Dashboard                                                                                      |
| **Workspace** | Item's workspace                                                                                                                    |
| **Status**    | Success or Failed                                                                                                                   |
| **Country**   | Country of origin of the access, based on IP geolocation                                                                            |

**How to use sorting:** click the column header (**Date/Time**, **User**, **Artifact**, **Type**, **Workspace** or **Status**; **Country** is not sortable). The first click sorts in descending order and the second reverses it; the arrow next to the header indicates the direction. The default is **Date/Time**, from newest to oldest.

**Empty state:** with no results, *No Report or Semantic Model events found* is displayed. Remember that the most recent events arrive in the next collection (01:23, 08:23 or 18:23, Brasília time, UTC-3).

### Event details

**What it is:** the **Event Details** modal, opened by clicking anywhere on the row.

**What it is for:** seeing where the access came from (IP, country, state, city, provider) and the technical identifiers of the event.

<figure><picture><source srcset="/files/LDKnpsyRebSGFZYFOCTV" 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-1adee3359213cbd7cd395407e63389b26925c650%2Fpm-auditoria-visualizacoes-de-relatorios-detalhe-en.png?alt=media" alt="Details of a view with country, state, city and provider"></picture><figcaption><p>Event details with the access geolocation</p></figcaption></figure>

**How to use:**

1. Click the view's row.
2. In **General Information**, hover over the **Operation** (`ViewReport` or `ViewDashboard`) to see the translation and what generates the event; also check the date/time, user, workspace and status.
3. In **Technical Metadata**, check **Client IP**, **Country**, **State**, **City**, **ISP**, **User Agent**, **Request ID** and **Activity ID**.
4. Close it with the **X** or by clicking outside the modal.

### View insights

**What it is:** the **View insights** button, in the filter bar, which takes you to the [Report Access Dashboard](/en/power-monitor/dashboards/dashboard-de-visualizacoes.md).

**What it is for:** moving from the event-by-event view to rankings and aggregates (most accessed reports, most active users, access by month, by capacity and by country).

**How to use:** click **View insights**. Prerequisite: your profile must have access to the dashboard page (Administrators always do; the Audit profile comes enabled; Member is blocked by default); without access, the screen is denied.

### Hide data

**What it is:** the **Hide data** button, next to **Export**. Once on, it shows **Show data**.

**What it is for:** sharing the screen, recording demos or taking screenshots without exposing people.

**How to use:** click **Hide data**: the identity of users (the **User** column and the detail panel) are masked on screen and in exported files. To see the values again, click **Show data**. If the file cannot be masked, the download is stopped and the screen warns *Could not mask the exported file. Show the data again or try once more.* The choice is saved in the browser and applies to the other screens that have the button. It is a presentation convenience, not an access control.

### Export

**What it is:** the **Export** button, in the filter bar, with the **CSV** and **JSON** options.

**What it is for:** keeping evidence of access or analyzing adoption outside the tool.

**How to use:**

1. Apply the filters you want.
2. Click **Export** and choose **CSV** or **JSON**.
3. The download starts automatically (up to 50,000 rows). If something goes wrong, *Failed to export data.* is displayed.

**How it works:** the export does not consider the Country and City filters.

## Rules and behavior

* **Same source as the Events Overview.** The events come from the Power BI/Fabric Activity Events collection (01:23, 08:23 and 18:23, Brasília time, UTC-3). See the collection rules in [Events Overview](/en/power-monitor/auditoria/geral-de-eventos.md#rules-and-behavior).
* **Geolocation.** Country, state, city and provider are obtained from the source IP by an external geolocation service, resolved every hour and cached for 90 days. Accesses from a private IP or not yet resolved have no country/city and **do not appear** when the Country or City filters are active.
* **The Country and City filters apply only to the list**: the KPIs and the export consider the other filters.
* **Via App and via Power Embedded.** The *Viewed via App* type identifies accesses made through a Power BI app; *Viewed via Power Embedded* identifies accesses by the embed Service Principal that were associated with a real user through the Power Embedded integration (configured in *Settings › Audit*).
* **Workspace scope.** You only see views of items in the workspaces you can view.

## Step by step: common scenarios

All steps start from *Audit › Report Views* and are available to any profile, always within the workspaces in your scope. If an administrator has blocked this page for your user in [Users](/en/power-monitor/usuarios.md), it disappears from the menu and direct access through the address leads to the **Not allowed** screen. If the screen itself displays **Access Denied**, the server refused the query for your user: contact an administrator.

### How to check whether a person opened a report

Use this to prove access, for example, "did the director open the closing report before the meeting?".

{% stepper %}
{% step %}

### Adjust the period

Set **Start Date** and **End Date** to cover the range of interest.
{% endstep %}

{% step %}

### Filter the user

In the **User** header, type the e-mail (or part of it) in *Search by e-mail...*.
{% endstep %}

{% step %}

### Filter the report

In the **Artifact** header, type the name (or part of it) in *Search artifact...*.
{% endstep %}

{% step %}

### Check the result

Each row is an opening of the report, with date/time and country. If the list is empty (*No Report or Semantic Model events found*), no view was recorded in the period: remember that the most recent events arrive in the next collection (01:23, 08:23 or 18:23).
{% endstep %}
{% endstepper %}

### How to identify accesses via app or via Power Embedded

* **Via app:** in the **Artifact** column, below the name, *via App: {app}* is shown.
* **Via Power Embedded:** in the **User** column, below the e-mail, *via Power Embedded* is shown. The e-mail displayed is the end user's, resolved by the Power Embedded integration (prerequisite: integration configured by an administrator in *Settings › Audit*).

To list only these accesses, use the **Type** filter (see **Type filter**, under Features).

## Frequently asked questions

<details>

<summary>The country appears as "-" in some accesses.</summary>

The IP has not been resolved yet (resolution happens every hour) or it is a private/corporate IP that has no public location.

</details>

<details>

<summary>I clicked "View insights" and got "unauthorized".</summary>

The Report Access Dashboard exposes the usage profile of each person in the organization, so the Member profile has the page blocked by default. Ask an administrator to enable the page in [Users](/en/power-monitor/usuarios.md).

</details>

<details>

<summary>A user opened the report through an app. How do I identify it?</summary>

The Artifact column shows *via App: {app}*. You can also filter Type by *Viewed via App*.

</details>

## Related pages

* [Events Overview](/en/power-monitor/auditoria/geral-de-eventos.md)
* [Report Access Dashboard](/en/power-monitor/dashboards/dashboard-de-visualizacoes.md)
* [Efficiency Dashboard](/en/power-monitor/dashboards/dashboard-de-eficiencia.md): reports with no access


---

# 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/auditoria/visualizacoes-de-relatorios.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.