Getting started with Adopt
Organizations still using the standalone version of Adopt should refer to the Adopt (classic) documentation—until they transition to the Infinity-integrated version described on this page.
Nexthink Adopt guides allow employees to contextually receive real-time support while successfully conducting on-the-job tasks, directly from the applications available in your organization.
Nexthink Adopt offers different types of guidance overlays, depending on employee needs and the nature of the software application.
Prerequisites
Before creating, managing and publishing Adopt guides for web applications:
Install and deploy Nexthink browser extension across your organization.
Deploying the Nexthink browser extension across all employee devices, allows them to access published guides associated with the web application in use.
Employees cannot edit guides nor access the Adopt Editor.
Confirm the Nexthink Infinity tenant for the Nexthink browser extension.
Adopt guides are specific to the Nexthink environments where you create and configure them. Therefore, depending on your architecture, you can deploy different guides for the same web application across multiple tenants.
Grant Nexthink Application permissions to Nexthink user roles creating and configuring Adopt guides.
Configure in Nexthink Applications a web application of interest—associated with a specific Nexthink Infinity tenant—and enable it for Adopt guides deployment.
How to deploy in-application guides with Nexthink Adopt?
Refer to the Deploying a guide: end-to-end procedure for a summarized sequence of steps for publishing an Adopt guide.
After meeting the prerequisites listed above, the following diagram depicts the overall workflow for deploying Adopt in-app guides. The Adopt Agent, part of Nexthink browser extension, renders created guides to any employee who visits the target web application.
What type of guides can I deploy in web applications?
Guides provide in-app guidance throughout tasks in real time by directly interacting with elements from the application web interface.
These are the available guide types:
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.
What are the different visual components and overlays available for guides?
When defining components for a guide, Adopt Editor offers different overlay options—that is, the graphical user interface elements of interaction:
Bubble: pop-up attached to an element. Bubble pop-ups appear when following guide steps, when a page loads, or when employees interact with a specific element.
Smart page: pop-up not attached to an element. Splash pop-ups appear to the user in the center of the screen on page load or as part of a guide.
Notice: pop-up at the bottom-right of the screen to provide guidance. Notices can operate both independently or as part of a guide.
Sidebar: screen side panel not attached to an element—usually on the left side.
The image below displays a bubble pop-up example with a Walkthrough step.
How can employees search for published guides within the web application?
Context Help is a question mark icon easily accessible to all employees by default. By clicking the Context Help icon, employees open a pop-up with a search bar and contextualized support guides or documents for self-help.
Links in the Context Help pop-up may take employees to external content in a new browser tab. The following image shows an open Context Help pop-up from an application.
When do guides or the Context Help pop-up become visible to employees within the web application?
When configuring a guide created in Nexthink Applications, or while developing guide content from the in-app Adopt Editor, you should define Element selectors and Conditions to determine when and where the employee triggers a guide and/or the Context help icon within the web application.
You should also determine how different employee actions trigger a sequence of visual guide components.
How can I monitor and measure employee-guide engagement?
Monitor predefined dashboards with Adopt-related fields to identify how employees interact with your in-app guides. Leverage this data to refine guidance support and maximize application adoption within your organization.
How can I execute a digital adoption strategy within my organization?
To drive digital transformation, you should go beyond just deploying quality in-app guides to users—you should impact employee experience and, as a result, drive organizational productivity and efficiency.
Follow the Executing a digital adoption strategy documentation to successfully combine powerful digital adoption capabilities from Adopt with the comprehensive analytics of Digital Employee Experience (DEX)—Nexthink Infinity.
Granting permissions for Adopt
To enable proper permissions for Adopt as an administrator:
Select Administration > Roles from the main navigation panel.
Create a New Role or edit an existing role by hovering over it.
In the Permissions section, scroll down to the Applications section to enable appropriate permissions for the role:
Manage all applications: to create and manage guides in the Applications module of the Nexthink web interface.
View all dashboards: to monitor employee-guide engagement and interactions.
View domain impact on Applications permissions
The table below shows what users with full and limited View domain access can do, assuming the necessary permissions are enabled.
Manage all applications
View all application dashboards
Last updated
Was this helpful?