> 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/monitoring-applications/monitoring-web-applications/ahead/affordability.md).

# Affordability

The **Affordability** tab compares how many of an application's purchased licenses your organization uses against the total configured.

**Affordability** is enabled by default for each application. If software metering is not yet configured, the tab shows an **Enable now** action: selecting it automatically configures software metering using an AI-suggested threshold for that application, without requiring you to visit the Software Metering module. You can review or adjust the suggested threshold from the **Manage software metering** page at any time.

## Explore license usage

The top section of the **Affordability** tab shows how many of the application's licenses employees actively use.

The system counts a license as used when employee application usage meets the software metering thresholds, then calculates the percentage of licenses in use. Refer to [Configuring AHEAD](/user-guide/applications/setting-up-and-managing-applications/configuring-applications/configuring-web-applications/configuring-ahead.md) for configuration details.

All metrics are calculated over the last 90 days.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fd40nIHIs1Y04TpRm5S1c%2F2026.8_AppEx_15_Ap9Ld4.png?alt=media&#x26;token=15574794-8070-49db-a285-a78c3baa6af1" alt=""><figcaption></figcaption></figure>

From the **Affordability** tab of the target application:

* Review the **licenses used** percentage to see how many of the configured licenses employees actively use.
  * Use the trend indicator to compare the current value against the previous period.
  * Hover over the **licenses used** percentage to open the **action menu** and drill down into the specific employees behind the aggregate.
* From the **Overview** gauge, review the breakdown of employees with an application license based on application usage:
  * **Using**: employees whose usage meets the configured software metering threshold.
  * **Underusing**: employees whose usage is below the configured software metering threshold.
* Inspect how license usage is distributed across your organization from the **Usage breakdown by department**.

{% hint style="info" %}
When licenses used exceeds 100%, the system displays 100%. If the total number of licenses is not configured in Manage Applications, the system shows only the count of licenses used, without a percentage.
{% endhint %}

## Investigate license usage by employee

Identify employees with little or no usage to reclaim or reassign their licenses to reduce cost.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Flqiloj6FAEsMF7FE0uVN%2F2026.8_AppEx_16_Yv3Rq8.png?alt=media&#x26;token=0a165d75-0a56-4ff2-8603-b76befe0bdcb" alt=""><figcaption></figcaption></figure>

From the **Affordability** tab of the target application:

* Review the employee table to see each employee application usage time and when they last used the application.
* Select a column header to sort employees by usage time.


---

# 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/monitoring-applications/monitoring-web-applications/ahead/affordability.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.