# Deploying a guide: end-to-end procedure
{% hint style="info" %}
To drive greater impact, go beyond guide deployment by [Executing a digital adoption strategy](/platform/solutions/executing-a-digital-adoption-strategy.md)—combining Adopt tools and powerful Nexthink Infinity DEX analytics.
For an introduction to Adopt basics and features, refer to the [Getting started with Adopt](/platform/user-guide/adopt/getting-started-with-adopt.md) documentation.
{% endhint %}
This page summarizes the steps to launch an Adopt in-app guide. This procedure involves switching between the Nexthink web interface and Adopt Editor.
***
{% stepper %}
{% step %}
**Configure an application in the Nexthink Applications module**
From **Applications** > **Manage applications**:
1. In the **Settings** tab, enable [web usage time](/platform/user-guide/applications/managing-applications.md#managingapplications-collectusagetimeforwebapplications) collection for all applications, to ensure Adopt-related dashboards work properly.
2. In the **Applications** tab, [configure a new or existing web application](/platform/user-guide/applications/configuring-applications/configuring-web-applications.md)—including [key pages](/platform/user-guide/applications/configuring-applications/configuring-web-applications/key-pages.md) setup.
* Alternatively, [import built-in web application configurations](/platform/user-guide/applications/configuring-applications/configuring-web-applications.md#configuringwebapplications-understandingurlpatterns-1) which include predefined key pages and CSS selectors. This feature is different from applications installed from Nexthink Library.
3. From the application configuration page:
* Enable the **Digital adoption** toggle button from the **Application** **settings** tab > **General** subtab on the web application configuration page. See the image below.
* **Save settings** after enabling **Digital adoption**.
{% endstep %}
{% step %}
**Create and set up a guide in Nexthink**
In **Applications** > **Manage applications** > application **Edit** page:
1. In the **Adoption settings** tab, define default behaviors for all guides created for this application.
* In the [Settings subtab](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/configuring-adoption-settings.md#configuring-adoption-settings-for-the-selected-application), configure the guide default behaviors and determine how Adopt Editor captures page elements directly from the target web application based on a predefined set of instructions for **Element selectors**.
* In the [Localization subtab](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/configuring-adoption-settings.md#configuring-the-localization-settings-for-the-selected-application), select a set of languages to activate AI-generated translations for specific guides which Adopt displays based on the employee's browser settings.
* In the [Theme subtab](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/configuring-adoption-settings.md#customizing-the-adopt-theme-for-the-selected-application), define the default color scheme for guide components.
* In the [Context help subtab](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/configuring-adoption-settings.md#configuring-context-help-settings-for-the-selected-application), configure how the **Context help** pop-up appears and behaves on the web application site by default.
**Save** the web application after configuring the [Adoption settings](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/configuring-adoption-settings.md).
2. In the **Adoption content** tab > **Guides** subtab, [create a new guide](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/creating-guides.md):
* Paste the guide's target URL in the **Open editor on URL** field. When launching Adopt Editor from the Nexthink browser extension for the created guide, the browser automatically loads the defined URL path.
* Define the guide **Type**: **Walkthrough, Tooltip** or **Media**. The guide type is not editable after creation.
3. After saving the guide's name, URL and type, on the guide's **Edit** page:
* Define how the guide is accessed by enabling at least one of the following options:
* **Activate autostart**: The guide starts automatically when the application page loads.
* **Include in context help**: The guide is accessible via the **Context help** pop-up.
* Define conditions, separately for **Autostart** and **Context help**, to restrict guide visibility based on previous user interactions, user or device attributes or browser language settings.
* Optionally, set up [inbound connectors](/platform/configuring_nexthink/bringing-data-into-your-nexthink-instance/integrating-nexthink-with-third-party-tools/inbound-connectors.md) to extract custom user attributes from the target web application for precise targeting conditions.
4. **Save** the guide as a draft.
{% hint style="info" %}
Alternatively, [import existing guides](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/managing-guides.md#importing-guides) previously exported in JSON format instead of creating a new guide.
{% endhint %}
{% endstep %}
{% step %}
**Develop content for your guide in Adopt Editor**
From your Nexthink browser extension:
1. To access guides created in the Nexthink web interface, you must first authenticate.
* Right-click on the Nexthink extension icon, or open the extension options, and select **Sign in as an administrator.**
* Alternatively, go to the **Tenants Configuration** page and select **Authenticate** from the action menu, to authenticate for a specific Nexthink environment**.**
2. Once authenticated, click on the Nexthink icon from the browser toolbar or select **Inspect pop-up window** from the extension options.
* Select the Nexthink **Tenant** where you have created the guide.
* Select the target web **Application**.
3. Click the guide of interest to open Adopt Editor on the corresponding web application page and begin [developing and customizing the guide content](/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor.md).
{% endstep %}
{% step %}
**Publish your guide in Nexthink**
Return to Nexthink **Applications** > **Manage applications:**
1. Select the web application for which you have both created a guide and developed the guide content, and open the **Adoption content** tab > [Guides subtab](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/managing-guides.md).
2. Hover over a guide to reveal the action menu on the right side of the table-item row and select **Publish**.
* Once published, employees will be able to access the guide according to the conditions for guide autostart and visibility in the Context help pop-up.
* You cannot edit published guides in the Nexthink web interface or in Adopt Editor. If changes are required, [unpublish the guide](/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/managing-guides.md).
{% hint style="info" %}
Refer to [Guide insights and analytics](/platform/user-guide/adopt/guide-insights-and-analytics.md) for more information about employee-guidance interaction monitoring.
{% endhint %}
{% endstep %}
{% endstepper %}
---
# Agent Instructions: 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:
```
GET https://docs.nexthink.com/platform/user-guide/adopt/getting-started-with-adopt/deploying-a-guide-end-to-end-procedure.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.