# Creating guides

{% hint style="warning" %}
Refer to the [Deploying a guide: end-to-end](https://docs.nexthink.com/platform/user-guide/adopt/getting-started-with-adopt/deploying-a-guide-end-to-end-procedure) procedure for a summarized sequence of steps for publishing a guide.
{% endhint %}

Guides help you deliver **Walkthroughs**, **Tooltips**, or **Media** content to users. This page outlines the process of creating and managing Guides on the Nexthink platform.

## Creating guides

From Nexthink **Applications** > **Manage Applications:**

1. Select the application for which you want to create a guide.
2. On the **Application settings** tab, **Enable digital adoption**. This enables the **Adoption settings** and **Guides** tabs for the selected application.
   * **Save settings** after enabling digital adoption.

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

3. Go to the now enabled **Guides** tab—for the target application—and from the top right corner, create a **New guide**.
4. Define basic settings for your guide:
   * **Name:** Input a name for your guide.
   * **Open editor on URL:** Input the URL for your guide target page.
     * When launching Adopt Editor from the Nexthink browser extension for the created guide, the browser automatically loads the defined **Open editor on the URL** path.
   * **Description:** Input a short description for your guide.
   * **Type:** Select a type for your guide. The guide type cannot be changed after creation.
     * **Walkthrough:** step-by-step guidance of a task flow. The walkthrough provides in-line support throughout the process.
     * **Tooltip**: contextual information that organically unfolds to end-users while hovering or using specific elements on the application site. Unlike walkthroughs, tooltips are independent, user-discoverable, and quickly built.
     * **Media**: existing media or articles embedded within the application site. This way, end-users can access media content from the Context help pop-up—based on the Context help configuration and conditions.
5. **Save** the guide.

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

After creating a guide, you land on the guide **Edit** page. You should enable at least one of these two options:

6. **Activate autostart**, allowing you to [define autostart conditions](#defining-conditions-for-guide-autostart) that determine when the guide is shown to employees.
   * If you do not set any conditions, the guide starts automatically on every employee visit.
   * If your guide is a **Tooltip**, this is enabled by default and cannot be disabled.
7. **Include in context help**, allowing you to [define Context Help conditions](#defining-conditions-to-include-guides-in-context-help) that determine when the Context help pop-up displays the guide in question.
   * If your guide is **Media**, this option is enabled by default and cannot be disabled.

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

8. **Publish** your Guide or **Save it as a draft**. Guides can be edited as drafts in the in-app Adopt Editor and become visible to employees when published.

Alternatively, you can [import existing guides](https://docs.nexthink.com/platform/user-guide/adopt/managing-guides#importing-guides) previously exported—in JSON format—from the same or a different Nexthink instance, saved on your local device.

{% hint style="warning" %}
Before publishing a guide, configure the [Adoption settings](https://docs.nexthink.com/platform/user-guide/adopt/guide-creation-and-management-from-nexthink-applications/configuring-adoption-settings) applicable to all guides for the specific application.
{% endhint %}

### Defining conditions for guide autostart

Define a **New condition** to autostart guides based on completeness and interaction criteria.

For instance, the condition **Has viewed the related guide** automatically triggers the target guide after an employee views a predefined, related guid&#x65;**.**

Alternatively, you can set autostart conditions based on:

* **Frequency** (time)
* Employee's **Browser language**.
* Predefined [key pages](https://docs.nexthink.com/platform/user-guide/applications/configuring-applications/configuring-web-applications/key-pages) for the selected application.
* Predefined [custom fields](https://docs.nexthink.com/platform/user-guide/administration/content-management/custom-fields-management#customfieldsmanagement-creatinganewcustomfieldaddfield), such as **User attributes** or **Device attributes,** to create rule-based conditions.
  * For example, autostart the target guide when the **Adopt user** (employee) does not have a **Manager** role.

<details>

<summary>Using inbound connectors to define conditions from app-specific user attributes</summary>

For applications like Workday, Salesforce, or SAP SuccessFactors, you may set up inbound connectors in Nexthink to extract in-app user attributes. These custom fields help define precise guide-autostart conditions based on user roles or activities.

* [Connector for Workday](https://docs.nexthink.com/platform/integrations/inbound-connectors/connector-for-workday)
* [Connector for Salesforce](https://docs.nexthink.com/platform/integrations/inbound-connectors/connector-for-salesforce)
* [Connector for SAP SuccessFactors](https://docs.nexthink.com/platform/integrations/inbound-connectors/connector-for-sap-successfactors)

</details>

{% hint style="info" %}
If you do not set any conditions, the guide starts automatically on every user visit.
{% endhint %}

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

### Defining conditions to include guides in Context help

Define a **New condition** to include guides in the Context help pop-up based on completeness and interaction **Criteria.**

For example, after a user views a guide a certain amount of time&#x73;**,** the target guide becomes accessible from the Context help pop-up.

Alternatively, you can set autostart conditions based on:

* **Frequency** (time)
* Employee's **Browser language**.
* Predefined [key pages](https://docs.nexthink.com/platform/user-guide/applications/configuring-applications/configuring-web-applications/key-pages) for the selected application.
* Predefined [custom fields](https://docs.nexthink.com/platform/user-guide/administration/content-management/custom-fields-management#customfieldsmanagement-creatinganewcustomfieldaddfield), such as **User attributes** or **Device attributes,** to create rule-based conditions.
  * For example, the target guide becomes accessible from the Context help pop-up for employees with devices not based in **Andorra**.

<details>

<summary>Using inbound connectors to define conditions from app-specific user/device attributes</summary>

For applications like Workday, Salesforce, or SAP SuccessFactors, you may set up inbound connectors in Nexthink to extract in-app user attributes. These custom fields help define precise Context-help visibility conditions based on user roles or activities.

* [Connector for Workday](https://docs.nexthink.com/platform/integrations/inbound-connectors/connector-for-workday)
* [Connector for Salesforce](https://docs.nexthink.com/platform/integrations/inbound-connectors/connector-for-salesforce)
* [Connector for SAP SuccessFactors](https://docs.nexthink.com/platform/integrations/inbound-connectors/connector-for-sap-successfactors)

</details>

{% hint style="info" %}
If you do not set any conditions, the guide is always accessible from the Context help pop-up by default.
{% endhint %}

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

## Localizing content

Once you have [configured localization settings in a selected application](https://docs.nexthink.com/platform/user-guide/adopt/configuring-adoption-settings#configuring-the-localization-settings-for-the-selected-application) for a specific set of languages, you can translate guide content for those languages. To achieve this, use **AI localization** or provide manual translations.

### Creating automatic translations with AI

{% hint style="info" %}
The system displays the ✦ sparkles icon to indicate AI-generated content or insights. AI is evolving rapidly and delivering great insights, but it can still make mistakes. Nexthink recommends validating your results to ensure accuracy and support informed decision-making. Refer to the [Global AI Hub](https://docs.nexthink.com/legal/global-ai-hub) documentation for more information.
{% endhint %}

If you have selected any languages other than the system default (English), select **Update** to create an automatic translation.

When developing content for the target guide in[ Adopt Editor,](https://docs.nexthink.com/platform/user-guide/adopt/guide-content-development-from-in-app-adopt-editor) you can review and override any of the translated content for a specific guide step or overlay.

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

{% hint style="warning" %}
Note that users can select any previously configured language while viewing a guide in the Adopt Editor. However, until you generate translated content for languages other than the system default, the guide will appear blank in those languages.
{% endhint %}

### Creating manual translations from Adopt guide editor

Besides AI localization, you can create manual translations by selecting a different language from **Step properties** > **Content language** in the Adopt editor. This allows you to manually update step content in each previously selected language.

***

RELATED TOPICS

* [Deploying a Guide: end-to-end procedure](https://docs.nexthink.com/platform/user-guide/adopt/getting-started-with-adopt/deploying-a-guide-end-to-end-procedure)