> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/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/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools.md).
# Setting up and managing AI Tools
Configure AI Tools and its content to ensure AI Tools users can fully benefit from it without interruptions.
To start configuring AI Tools:
* Review the AI Tools technical prerequisites outlined in the [#before-you-begin](#before-you-begin "mention") section on this page.
* Refer to [Configuring AI tools](/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools/configuring-ai-tools.md).
* Refer to [Configuring Microsoft Copilot using API credentials](/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools/configuring-ai-tools/configuring-microsoft-copilot-using-api-credentials.md).
* Refer to [Modifying campaign setups for AI tools](/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools/modifying-campaign-setups-for-ai-tools.md) to set up campaing target exclusion or change sender information.
{% hint style="info" %}
After configuration is complete in your Nexthink instance, [manage AI tools content](/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools/managing-ai-tools.md).
{% endhint %}
## Before you begin
Complete the following prerequisites to ensure the correct configuration and monitoring of AI tools, and facilitate a smooth onboarding:
{% stepper %}
{% step %}
#### Deploy the Nexthink browser extension for data collection
Install and deploy Nexthink [browser extension](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-the-nexthink-browser-extension.md)—`25.8.1` or newer—across all employee devices to allow Nexthink to collect data for AI tool web usage.
Nexthink browser extension cannot track the web usage of AI tools on Mozilla Firefox
{% endstep %}
{% step %}
#### Validate Collector version for the deployment of built-in campaigns
Ensure all employee devices have Collector version `25.5.1` or newer. This guarantees the correct deployment of built-in Nexthink campaigns, which you should enable from the specific [AI tool configuration](/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools/configuring-ai-tools.md#configuring-ai-tools-for-nexthink-monitoring), to collect employee feedback on AI usage, necessary for monitoring employees' perceptions of AI tools.
Run the following query in the Investigations module to list devices with an unsupported Collector version:
```
devices
| where collector.version < v25.5.1
```
{% endstep %}
{% step %}
#### Enable the `focus_time` field for monitoring desktop AI tools
Make sure to opt in and activate the `focus_time` field for `execution.events` , by using the *Set Collector Configuration* remote action from the [library pack](https://nexthink.com/library/collector-configuration#set-collector-configuration) from Nexthink Library.
The system estimates **AI usage** on **Desktop**-type applications using the `focus_time` field. Without `focus_time`, Nexthink cannot monitor AI-tool interactions on desktop applications.
{% endstep %}
{% step %}
#### Set up connector credentials and Entra ID connector for Microsoft Copilot
The system uses API-based configuration for Microsoft Copilot, which requires the configuration of **connector credentials** and **Entra ID connector** in Nexthink.
Configure connector credentials
{% hint style="info" %}
This section references external sources. Nexthink does not control the accuracy of third-party documentation or any external updates or changes that might create inconsistencies with the information presented on this page. Please report any errors or inconsistencies to [Nexthink Support](https://support.nexthink.com/).
{% endhint %}
**Step 1 - Configure the Azure application**
Configure the application from the [Azure](https://azure.microsoft.com/es-es/free/search/?ef_id=_k_EAIaIQobChMIodqLx8ichgMVu5xQBh2GnA_UEAAYASAAEgJxevD_BwE_k_\&OCID=AIDcmm68ejnsa0_SEM__k_EAIaIQobChMIodqLx8ichgMVu5xQBh2GnA_UEAAYASAAEgJxevD_BwE_k_\&gad_source=1\&gclid=EAIaIQobChMIodqLx8ichgMVu5xQBh2GnA_UEAAYASAAEgJxevD_BwE) page to retrieve AI-employee interaction data:
1. Sign in using your Azure credentials.
2. Register a new application.
* During the registration process, select the **Single tenant** option.
3. For the **Redirect URL**, select **Web**.
* If the application already exists in the Azure portal, you can reuse the application to assign the permissions to retrieve AI-employee interaction data.
4. **Register** the application.
5. Access the **API Permissions** option from the left-side menu.
6. Add permission for **Microsoft Graph**.
* Select **`AiEnterpriseInteraction.Read.All`** and add the API permission. See the images below.
 
The **Status** column on the permissions list indicates if the Azure account you are using lacks proper privileges. Refer to the [Register an application with the Microsoft identity platform](https://learn.microsoft.com/en-us/graph/auth-register-app-v2) documentation from Microsoft for more information on the steps listed above.
7. Access the **Overview** section of the configured application to copy and save Azure AD credentials for the Nexthink connector configuration.
* **Application (client) ID**
* **Directory (tenant) ID**
* Generate and copy the client secret Value in the Azure portal using the **Certificates** and **secret** option for the Nexthink tool configuration.
* Select **New client secret**.
* Fill in the **Description** and **Expiration values**.
* Select **Add** and copy the **Value**.
After the expiration date, you need to update the client secret in the Azure portal and for the Nexthink connector credentials.
**Step 2 - Configure the Microsoft Copilot connector credentials in Nexthink**
From the [connector credential](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/outbound-connectors/connector-credentials.md#connectorcredentials-connectorcredentialsforhttpshttpsprotocol) configuration page, fill out the fields using the information from the connection you created in Azure.
1. Choose the **HTTPS** option from the **Protocol** drop-down.
2. Paste the Microsoft API `https://graph.microsoft.com` into the **URL address** field.
3. Choose the `OAuth 2.0 - Client Credentials` option from the **Authorization** drop-down.
4. Copy the **Directory (tenant) ID** from the Copilot connection and paste it into the **Access token URL** field—include the whole URL string:
* `https://login.microsoftonline.com/<<`**`Tenant ID`**`>>/oauth2/v2.0/token`
* Example: `https://login.microsoftonline.com/2efa03d5-62e6-XXXX-XXXX-XXXXXXXXXXXX/oauth2/v2.0/token`
5. Enter the **Client ID** and **Client secret** you obtained from configuring the Azure application.
6. Add `https://graph.microsoft.com/.default` in the **Scope** field.
7. Select **Header** under **Authorization information**. Nexthink advises against selecting **Body** based on Request for Comments (RFC) standards.
8. **Save** the credential.
Set up the Entra ID connector
The system uses the **Entra ID connector**—that you must configure—to collect user-license data and tag interaction events based on whether the employee uses a free or licensed version of Microsoft Copilot.
Refer to [Microsoft Entra ID (Azure AD) connector](/platform/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 configuration steps.
{% hint style="warning" %}
Nexthink AI Tools collects user-license data for Microsoft Copilot by default, even if you do not configure Microsoft Copilot in AI Tools. Refer to [Configuring Microsoft Copilot using API credentials](/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools/configuring-ai-tools/configuring-microsoft-copilot-using-api-credentials.md#configuring-the-tool-in-the-nexthink-web-interface) for more details.
{% endhint %}
{% endstep %}
{% step %}
#### Configure user organization fields for usage breakdowns tailored to your organization
Nexthink **User organization fields** enable custom dashboard filters that align with your organization structure and employee groups.
Depending on the data field enrichment method, you may use the **Entra ID connector** configured in step 4.
Refer to [Device and user classification](/platform/user-guide/administration/system-configuration/data-management/environment/product-configuration.md#configuring-user-organization) to create and enrich user organization fields.
{% endstep %}
{% step %}
#### Enable domain names for tool detection for AI governance
Enable domain names at Collector level to ensure the system can detect all AI tools in use within your environment—this is essential for the correct functioning of **AI tool governance** features.
To enable domain names, download and run the *Set application connectivity configuration* remote action from Nexthink Library.
Running a remote action from Nexthink Library to enable domain names
From Nexthink Infinity web interface:
1. Download the *Set application connectivity configuration* remote action from **Nexthink Library**.
2. From the main navigation panel, go to **Remote Actions > Manage remote actions** to open the **Remote Actions Administration** page.
3. From the **Remote Actions Administration** page, use the table search bar to find the *Set application connectivity configuration* remote action. Open the action menu to **Configure** the remote action settings.
4. From the remote action configuration, under the **General** tab:
* Select your preferred **Trigger.** Execute the remote action **manually** or **schedule** it to run periodically.
* Ensure you target all **Devices** and **VDI sessions** if applicable.
5. From the remote action configuration, under the **Script** tab:
* Set the **Value** of **allow\_domain\_names\_reporting** to `True`.
* Set the **Value** of **set\_data\_privacy\_filter** to `ALLOW\*` all domains. Refer to [Configuring Collector-level anonymization](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-collector/configuring-collector-level-anonymization.md#configuringcollectorlevelanonymization-domainnamewithwildcard) for more information.
Nexthink Collector reports network connections by default. However, if you have disabled network connection reporting in the past, make sure you set the **Value** of **allow\_connection\_data\_reporting** to `True`.
6. After saving the *Set application connectivity configuration* remote action configuration, you should execute it manually. Refer to [Managing Remote Actions](/platform/user-guide/remote-actions/setting-up-and-managing-remote-actions/managing-remote-actions.md#executing-remote-actions-from-the-manage-remote-actions-page)
{% hint style="info" %}
Nexthink detects all **AI tools in use** based on `connection.events` data. The system maps the observed AI tool `domains` to be displayed under the **AI tools governance** tab.
`domain` reporting is not scoped to specific users or tools—it's an instance-wide Collector setting.
{% endhint %}
{% endstep %}
{% step %}
#### Grant permissions for AI Tools
Enable permissions for the **AI Tools** module as an administrator.
1. Select **Administration >** [Roles](https://docs.nexthink.com/platform/user-guide/administration/account-management/roles) from the main navigation panel.
2. Create a **New Role** or edit an existing role by hovering over it.
3. Under the **Permissions** section, scroll down to the **AI Tools** section to:
Enable permissions for AIadoption monitoring and management
Enable permissions for **AI** **adoption** monitoring and management:
* **Manage all AI tools** to create and manage AI tools configured by your organization for **AI adoption** monitoring.
* **View all AI tool dashboards** to monitor **AI adoption** dashboards and insights.
Enable permissions for AI tools governance
If needed, you may grant permissions specifically for **AI tools governance**, separate from the adoption monitoring permissions listed above.
* **Manage AI tools governance** to manage governance policies for all AI tools, and add new AI tools to assign them governance policies, if required.
* **View AI tools governance** to see **AI tools governance** dashboard data.
{% hint style="warning" %}
User roles with only **AI tools governance** permissions cannot access any **AI adoption-related** data, configurations, or dashboards from anywhere in the product.
{% endhint %}
4. Ensure you grant **Data Model Visibility** into **AI Tools** to the specific user role. Refer to [Roles](/platform/user-guide/administration/account-management/roles.md#data-model-visibility) for more information.
{% endstep %}
{% endstepper %}
## Key AI Tools configuration concepts
### AI-tool application types: Desktop and Web
Nexthink supports the following types of application configurations for AI tools:
* **Desktop** AI applications require their respective **Binaries** running the AI tool interaction.
* **Web** AI applications relies on the URL for the **Conversation endpoint** path used to detect interactions with the AI tool.
Refer to [Configuring AI tools](/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools/configuring-ai-tools.md#configuring-ai-tools-for-nexthink-monitoring).
{% hint style="warning" %}
The **API**-based setup is only available for Microsoft **Copilot.** Refer to [Configuring Microsoft Copilot using API credentials](/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools/configuring-ai-tools/configuring-microsoft-copilot-using-api-credentials.md).
{% endhint %}
***
### User-target exclusions for built-in campaigns
Built-in campaigns for AI Tools have uneditable content, deployed under specific conditions. However, if needed, you can modify AI-tool campaign settings to exclude specific users from campaigns and change campaing sender information details.
Refer to [Modifying campaign setups for AI tools](/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools/modifying-campaign-setups-for-ai-tools.md).
{% hint style="info" %}
To learn about the AI Tools campaign content, deployment conditions and interpretation, refer to [Monitoring AI Tools](/platform/user-guide/ai-tools/working-with-ai-tools.md#built-in-campaign-content-for-sentiment-tracking).
{% endhint %}
---
# 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.nexthink.com/platform/user-guide/ai-tools/setting-up-and-managing-ai-tools.md?ask=&goal=
```
`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.
