# Overview

The **Overview** dashboard helps service managers, application owners, and end-user computing (EUC) teams monitor employee experience and application adoption.

The dashboard highlights feature usage and user experience to support application roadmaps and lifecycle management.

## Interpreting the Overview dashboard

The **Overview** dashboard contains the following widgets grouped into the sections:

* [#experience-metrics](#experience-metrics "mention")
* [#usage-metrics](#usage-metrics "mention")

The top of the dashboard displays the **Employees** KPI and **Employees** chart widgets:

* The **Employees** KPI shows the total number of unique employees who had the application in focus by opening a browser tab at least once. Page loads that occur in background tabs without focus are not included in this KPI.
* The **Employees** chart displays, for each time bucket, the number of unique employees with usage time greater than zero, which cumulatively equals or exceeds the total number of unique employees.
* Optionally, [set up the number of licenses](https://docs.nexthink.com/platform/user-guide/applications/configuring-applications/configuring-web-applications/application-licenses) for the selected web application and identify cost optimization opportunities using a **License usage ratio** KPI.

{% hint style="info" %}
Use the **Investigate more** right-side panel, which offers predefined drill-down options. These links direct you to investigation results that are relevant to the current dashboard context.
{% endhint %}

<figure><img src="/files/TlT4ug241wo7yZuOGRvk" alt="Overview dashboard"><figcaption></figcaption></figure>

## Experience <a href="#experience-metrics" id="experience-metrics"></a>

This section reflects user-application **Experience** by tracking the total **Time lost** for the selected timeframe and web application, considering delays due to:

* [Page loads](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/page-loads.md) – Time taken for web pages to be ready for user interaction.
* [Transactions](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/transactions.md)– Time to complete a tracked user action.
* [Reliability](/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/performance/reliability.md) – Implied lost productivity from failed interactions.

{% hint style="info" %}
**Time lost** analytics use cases:

* For IT teams: Pinpoint where users lose the most time to prioritize performance fixes.
* For business stakeholders: Correlate delays and errors with lost productivity across the workforce.
  {% endhint %}

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

## Usage <a href="#usage-metrics" id="usage-metrics"></a>

The **Usage** section tracks the deployment of new applications, expansion of existing software into new countries or the introduction of specific new features via upgrades.

### Usage time per employee <a href="#usage-time-per-employee" id="usage-time-per-employee"></a>

This metric represents the average usage time or focus time per employee within the selected timeframe. **Usage time** includes:

* Time spent on page loads.
* Time the tab remains in focus, even without user interaction.

The system calculates **Usage time per employee** as the total focused usage time across all employees in a given timeframe, divided by the number of distinct employees.

On the line chart, each plotted point represents the average usage time per employee, computed across all unique active users within a specified time bucket—15 minutes, 1 hour or 1 day, depending on the chosen timeframe.

{% hint style="warning" %}
The system does not count the time a device is locked as **Usage time**.
{% endhint %}

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

### **Key pages**

[Configure key pages](/platform/user-guide/applications/configuring-applications/configuring-web-applications/key-pages.md) for each application individually. Key pages break an application down into functionally relevant parts based on the application URL patterns. For each page, see the number of unique **employees**, **usage time per employee** and **page views per employee**.

**Page views per employee** represents the average number of navigations per employee within a selected timeframe, considering both hard and soft navigations.

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

### **Transactions**

Transactions complement the monitoring of page loads by tracking important changes of state within a web application that do not necessarily require a complete page reload.

View the number of **employees**, **completed transactions**, and **completed transactions per employee**.

{% hint style="info" %}
Refer to the [Configuring Transactions](/platform/user-guide/applications/configuring-applications/configuring-web-applications/transactions.md) documentation for setting up transactions.
{% endhint %}

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

### Organization

The **Organization** table displays metrics by your organization's classification. Select the organization level from the dropdown list.

Refer to the [Product configuration](https://docs.nexthink.com/platform/latest/product-configuration) documentation for more information on how to define entities and custom classification for your organization.

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


---

# Agent Instructions: 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:

```
GET https://docs.nexthink.com/platform/user-guide/applications/monitoring-applications/monitoring-web-applications/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.