> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pbi-guides/parallels-browser-isolation-administrators-guide/parallels-browser-isolation-interface/dashboard.md).

# Dashboard

The **Dashboard** category allows you to perform quick actions and see general usage statistics.

<figure><img src="/files/oE6L8UAvK2IsRRAe26hL" alt=""><figcaption></figcaption></figure>

## **Past 24 hour insights**

This section lets you view what changes have taken place across metrics like total user session, total applications, policy violations and Current active users and a small arrow points the delta, whether it has a upward or downward trend.

## **Key trends**

This section lists the top domains that were visited either over a day or over a month, same has been extend to view the top violated policies and top risky users. You can also view the regions on a map showing the user sessions origin.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/pbi-guides/parallels-browser-isolation-administrators-guide/parallels-browser-isolation-interface/dashboard.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.