> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/configuring-ahead.md).

# Configuring AHEAD

Configure the required settings to populate the **Adoption**, **Health**, **Efficiency**, **Affordability**, and **Delight** tabs of the AHEAD dashboard.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2FpubQfBnZTTj1HyCyO5Xn%2F2026.9_AppEx_setup_17_Oh5Nv8Sp4l.png?alt=media&amp;token=51aae573-9890-4fb0-a5cb-b4e8f38efd00" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
AHEAD applies to web and hybrid (web and desktop) applications only.
{% endhint %}

## Configure user organization fields

Configure user organization fields to classify employees by department or business unit and enable organizational breakdowns in the dashboards.

* Define up to six levels of organizational hierarchy (for example, **Business Unit**, **Department**, **Region**) to enable breakdowns in the dashboards. Refer to [Configuring user organization](/user-guide/administration/system-configuration/data-management/environment/product-configuration.md) for more information.
* If user organization data is missing, configure the **Entra ID** connector to map dashboard data to your organization structure. Refer to [Connector for Microsoft Entra ID (Azure AD)](/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/connector-for-microsoft-entra-id-azure-ad.md) for more information.

## Configure Adoption settings

Enable web-usage time collection for the target application to capture usage duration data and populate the **Adoption** tab.

Select [Managing applications](/user-guide/applications/setting-up-and-managing-applications/managing-applications.md) to go to **Manage Applications > Settings**, and verify that **Web usage time** monitoring is enabled.

## Configure Health settings

The **Health** tab compares application performance against the global Nexthink benchmark by default.

Select [Setting application thresholds](/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/thresholds.md) to go to the web application's **Application settings > Web configuration > Thresholds** tab, and set application thresholds as a fallback to categorize performance when benchmark data is unavailable for this application.

{% hint style="info" %}
The **Health** heatmap can break down data by application feature, based on the **Key pages** configured for the application. Refer to [Configuring Key pages](/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/key-pages.md) to set them up.
{% endhint %}

## Configure Efficiency settings

Select [ServiceNow Tickets connector](/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors/servicenow-tickets-connector.md) to go to **Administration > Inbound connectors > New connector**, and configure the **ServiceNow Tickets** connector to bring ticket data into Nexthink and enable the **Efficiency** tab.

{% hint style="info" %}
The **ServiceNow Tickets** connector can collect both incidents and service requests. The **Efficiency** tab counts only service requests.
{% endhint %}

The **Efficiency** tab requires the **Tickets** data model to be visible for the user's role. Refer to [Data model visibility](/user-guide/administration/account-management/roles.md) for more information.

## Configure Affordability settings

Configure software metering thresholds for active license usage and total license counts to calculate the percentage of licenses in use in the **Affordability** tab.

* Select [Managing Software Metering](/user-guide/software-metering/managing-software-metering.md) to go to **Software Metering > Manage software metering**, and configure software metering thresholds to set the minimum usage that counts as an active license.
* Select [Setting application licenses](/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/application-licenses.md) to go to the web application's **Application settings > Web configuration > Licenses** tab, and enter the total number of licenses available for the application to calculate the license utilization rate shown in the **Affordability** tab.

{% hint style="info" %}
When multiple applications share the same software metering entry (for example, Salesforce Lightning and Salesforce Classic under Salesforce), the same threshold applies to each one.
{% endhint %}

Nexthink enables **Affordability** by default. If an application has no software metering configured, select **Enable now** on the tab to configure it automatically, using an AI-suggested usage threshold. Review or adjust the threshold from the **Manage software metering** page.

## Configure Delight settings

Enable the **Collect feedback** toggle on the web application's settings to collect employee satisfaction ratings and populate the **Delight** tab.

{% hint style="info" %}
The **Delight** score also uses **frustrating page loads** as a data source, which requires no additional configuration. If the survey is not configured for an application, the Delight score is calculated using frustrating page loads alone.
{% endhint %}

Nexthink limits how often the system surveys the same employee:

* 30 days between surveys for different applications, regardless of whether the employee responded
* 90 days between surveys for the same application if the employee declined or answered partially
* 90 days between surveys for the same application if the employee answered fully

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fi8JO9qwL5ixhvQME3dkw%2F2026.8_AppEx_SetUp_45_Kv2Th6.png?alt=media&#x26;token=e571085e-5988-45ba-82be-a05088f01277" alt=""><figcaption></figcaption></figure>

***

RELATED TASKS

* [Configuring Transactions](/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/transactions.md)
* [Setting application licenses](/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/application-licenses.md)
* [Setting application thresholds](/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/thresholds.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.nexthink.com/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/configuring-ahead.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.
