About hiding Userlane content
In some cases you might want to decide by whom and where Userlane content should be seen, e.g. based on roles and rights, sensitive pages.
This article covers
as well as the three options to hide Userlane content on specific pages:
Why use it
You might want to
Hide the Userlane Assistant on dedicated pages (e.g. Login Pages)
Hide Assistant (Guides) on a specific user request or for dedicated users
Option A - Manager task: Use Segmentation
You can hide the whole Userlane Assistant on a specific page using context-based segmentation.
This only works if the respective page has a specific URL content that is not part of the domain and that is only visible in the URL when being in this section (e.g. /login).
Learn more info on context-based segmentation in this article.
You can hide the whole Userlane Assistant for specific user groups only you can use user-based segmentation.
Option B - Dev Task: Implement the hide command
Alternatively, you can hide Userlane programmatically on specific pages (e.g. the login page) using the hide command:
// hide Userlane Userlane('hide');
If you want to show Userlane again after hiding it, you can use the initialize command:
// initialize Command Userlane('init', your_property_ID);
💡Good to know
- If you want to open the Assistant with a specific button, you can use the openAssistant command.
- If you use links to share Guides, the hide command won’t work on the login page. The Guide will start on the login page if the login URL is added on the Application URLs page of your application's settings. If you want this case to work as well, your developers have to remove the Userlane snippet from the login page.
Option C - Userlane Task: Use the passive mode
Should you decide to have your own button which should trigger Userlane, please don’t use the hide command. Simply contact us, so we can advise you on how to best set it up.