Creating guides
Last updated
Was this helpful?
Last updated
Was this helpful?
Refer to the Deploying a guide: end-to-end procedure for a summarized sequence of steps for publishing a guide.
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.
From Nexthink Applications > Manage Applications:
Select the application for which you want to create a guide.
On the Application settings tab, Enable digital adoption. This enables the Adoption settings and Guides tabs for the selected application.
Save the web application after enabling digital adoption.
Go to the now enabled Guides tab—for the target application—and from the top right corner, create a New guide.
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 till completion.
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: embedded existing media or articles 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.
Save the guide.
After creating a guide, you land on the guide Edit page. You should enable at least one of these two options:
Activate autostart, allowing you to define autostart conditions 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.
Include in context help, allowing you to define Context Help conditions 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.
Publish your Guide or Save it as a draft. Guides can be edited as drafts in the in-app Adopt Editor and will be visible to employees when published.
Before publishing a guide, configure the Adoption settings applicable to all guides for a specific application.
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 guide.
Alternatively, you can set autostart conditions based on:
Frequency (time)
Employee's Browser language.
Predefined key pages for the selected application.
Predefined custom fields, 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.
If you do not set any conditions, the guide starts automatically on every user visit.
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 times, 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 for the selected application.
Predefined custom fields, 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.
If you do not set any conditions, the guide is always accessible from the Context help pop-up by default.
Once you have configured localization settings in a selected application for a specific set of languages, you can use Nexthink AI localization to translate guide content for those languages.
If you have selected any languages other than the system default (English), select Update to create a translation.
When developing content for the target guide in Adopt Editor, you can review and override any of the translated content for a specific guide step or overlay.
Note that users can select any language you have configured while viewing a guide. However, until you generate translated content for languages other than the system default, the guide will appear blank in those languages.
RELATED TOPICS
