> 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/applications/setting-up-and-managing-applications.md).

# Setting up and managing Applications

Configure Applications and its content to ensure Applications users can fully benefit from it without interruptions.

* Review the Applications technical prerequisites outlined in [Before you begin](#before-you-begin).
* See [Configuring applications](/platform/user-guide/applications/setting-up-and-managing-applications/configuring-applications.md) for guides on how to configure applications.
* See [Managing applications](/platform/user-guide/applications/setting-up-and-managing-applications/managing-applications.md) for how to manage applications configured in your Nexthink instance.

### Before you begin

Nexthink Administrators must complete the following technical prerequisites to ensure all required system components and settings are correctly in place.

1. **Install the Nexthink browser extension**

   Install and deploy the [Nexthink browser extension](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/deploying-nexthink-in-non-vdi-environment/installing-the-nexthink-browser-extension.md) across your organization. This is required to monitor web applications.

   <div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>Nexthink does not support Mozilla Firefox for these purposes.</p></div>
2. **Validate Collector version and settings**

   Ensure all employee devices have the Collector version required for the application types you plan to monitor. For Desktop applications, opt in and activate the `focus_time` field for `execution.events` using the **Set Collector Configuration** remote action from Nexthink Library — Desktop application monitoring depends on this field.
3. **Set up inbound connectors**

   For applications like Workday, Salesforce, or SAP SuccessFactors, set up inbound connectors to extract in-app user attributes. These custom fields help define precise guide visibility conditions based on user roles or activities. Refer to [Guides conditions](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/configuring-adoption-settings/adopt-conditions.md) for more information on using these attributes as conditions.
4. **Set permissions**

   Nexthink Administrators should enable permissions to ensure the correct configuration and monitoring of Applications.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>Refer to the <a href="/pages/y1DAAad4AcWIE7y0un6T">Roles</a> documentation for a detailed description of Permissions, View domain options and <a href="/pages/y1DAAad4AcWIE7y0un6T#roles-dataprivacy">Data privacy</a> granularity settings.</p></div>


---

# 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/applications/setting-up-and-managing-applications.md?ask=<question>&goal=<endgoal>
```

`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.
