# Configuring applications

Your Nexthink Lead can identify the scope of applications that require configuration for your organization. Nexthink Leads are best positioned to play a product ambassador role and get application owners appropriately engaged in the process, maximizing the value received from Applications.

## Choosing applications to configure in Nexthink

Decide which applications to set up first, by identifying:

* Frequently used applications for email, calendar, collaboration tools and information technology service management (ITSM)—such as Office 365, Zoom, ServiceNow, and others.
* High-priority applications used for business-critical operations, including VIP-facing applications.
* Applications with low adoption and high reported incident rates—including applications with numerous employee complaints.
* Deployed applications as part of a digital transformation project.

{% hint style="info" %}
To better understand the relevance of an application within the context of your organization:

* Use an application portfolio management system, such as ServiceNow or similar, to find more information about usage, traffic and business criticality.
* Rely on a single-sign-on (SSO) tool to verify which applications are part of your organization portfolio.
* Interview application owners and experts within your organization.
{% endhint %}

## Configuring applications for Nexthink monitoring  <a href="#managingapplications-configuringapplications" id="managingapplications-configuringapplications"></a>

1. Access the configuration page for new applications by following one of these options:
   * From the **Applications** module on the main navigational menu, click the **New** button in the top-right corner of the menu to open the application configuration page.&#x20;
   * From the **Applications** > **Manage applications** page:
     * Click on the **New application** button in the top-right corner of the page to open the application configuration page.&#x20;

{% hint style="warning" %}
To access and edit the configuration of existing applications, click on the [application hyperlink](../managing-applications#managingapplications-applicationstab) in the **Applications** table on the **Manage applications** page. Then, continue to follow the steps listed below.
{% endhint %}

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fxgq59UT8x46fkbnopl4f%2Fimage.png?alt=media&#x26;token=9c1ce5fd-931a-461e-a799-381ed39b7d5a" alt="Accessing the configuring page for new applications."><figcaption></figcaption></figure>

2. From the application configuration page, fill in the fields:
   * **Application name:** enter a unique name up to 256 characters long. Use the standard UTF-8 character set. Note that copying text from other sources might bring unsupported special characters.
   * **Category**: Standard, Connectivity or Collaboration.
     * **Standard:** this is the default setting for application Category.
     * **Connectivity:** use this category for applications that strongly impact the Internet connectivity of employees in your organization, such as VPN or ZTNA applications.&#x20;
       * Selecting this category causes the system to highlight the application in the [Device View Timeline](../device-view/timeline) under **Connectivity**, making it easier to check the correlation between employees' connectivity issues and the application.
     * **Collaboration:** use this category for applications that are essential for collaboration in your organization, such as Teams or Zoom. When you select this category the system highlights the application in the Device View Timeline under the **Collaboration** section to correlate the activities of these applications and their impact on collaboration sessions. Refer to the [Device View](../device-view) documentation for more information.
3. Select an **Application type**: **Web**, **Desktop** or **Network.**
   * If needed, configure the **Web** and **Desktop** versions of the same application by ticking both **Web** and **Desktop** checkboxe&#x73;**.**
   * Configure **Network** applications as a standalone application type. Define a unique **Application name** to easily distinguish it from other versions, e.g. _Zscaler (network)._

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-9273459a8b885607cb58458f9ee8382401bb726a%2Fhybrid_application.png?alt=media" alt="hybrid_application.png" width="760"><figcaption></figcaption></figure>

4. Depending on the **Application type**—**Web**, **Desktop** or **Network**—you need to fill in different configuration settings. Refer to the following documentation to configure each application according to its **type:**
   * [configuring-web-applications](configuring-applications/configuring-web-applications "mention"), including:
     * Key pages&#x20;
     * Transactions&#x20;
     * Licenses&#x20;
     * Thresholds&#x20;
   * [configuring-desktop-applications](configuring-applications/configuring-desktop-applications "mention")
   * [configuring-network-applications](configuring-applications/configuring-network-applications "mention")

***

RELATED TRAINING

* [How to configure the Applications module](https://learn.nexthink.com/courses/how-to-configure-applications-module)
