Adopt conditions
Define conditions to autostart a guide, display it in context help, or show a Journey in context help.
This page outlines each condition and examples of use cases. Refer to Configuring Adoption settings to learn how to configure Context help settings and conditions.
Autostart is available for Walkthrough and Tooltip guides.
Context help is available for Walkthrough and Media guides.
When multiple conditions are defined for autostart or Context help, all conditions within their own set must be met for the guide or journey to appear. For example, if you define multiple conditions for a guide to appear in Context help, all must be satisfied. If you want the same guide to start automatically, you must define separate autostart conditions.
The table below displays the condition applicability in relation to autostart, Context help and journeys.
Number of views
✅
✅
❌
Number of completions
✅
✅
❌
Number of times closed or completed
✅
✅
❌
Has not completed the current guide/journey
✅
✅
✅
Has not viewed the current guide/journey
✅
✅
✅
Has completed the related guide
✅
✅
❌
Has closed or completed the related guide
✅
✅
❌
Has viewed the related guide
✅
✅
❌
Has not completed the related journey
❌
❌
✅
Has not viewed the related guide/journey
✅
✅
✅
Browser languages
✅
✅
✅
Frequency to show guide/journey
✅
✅
✅
User attribute
✅
✅
✅
Device attribute
✅
✅
✅
Key pages
❌
✅
✅
Number of views
Starts a guide based on the number of times it has been viewed. Define rules with is, is not, exactly, more than, or less than.
Example: Autostarting a guide once and then showing it in Context help:
Autostart condition:
is exactly 0orless than 1Context help condition:
more than 0
Number of completions
Controls how often a guide appears after completion. Prevents guides from showing again after users have completed them.
Number of times closed or completed
Similar to Number of completions but also counts when users close a guide without finishing it. Helps prevent showing the same guide too often or when completion is optional.
Has not completed the current guide/journey
Prevents the guide or journey from starting again once it has been fully completed.
Has not viewed the current guide/journey
Prevents the guide or journey from starting again after it has been viewed at least once.
Has completed the related guide
Starts a guide only after one or more related guides are completed.
Has closed or completed the related guide
Starts a guide after a related guide has been closed or completed.
Has viewed the related guide
Starts a guide once another related guide has been viewed.
Has not completed the related journey
Starts a journey only until a related one is completed, such as when a detailed journey replaces a broader one.
Has not viewed the related guide/journey
Starts a guide or journey only if a related one has not been viewed.
Browser languages
Limits visibility based on the user’s browser language. Select one or more languages from the list.
Frequency to start guide/journey
Controls how often a guide or journey starts. Helpful for reminders or process refreshers, such as starting a guide at the start of each Jira sprint.
Define frequency with exactly, more than, less than, at least, within combined with 1 week or 1 month.
Exactly 1 week means the guide is available only if the user visits the page exactly 7 days after the last time it was shown.
If the user misses that specific day, the guide will no longer appear unless it is started in another way (for example, from context help).
For exactly conditions, note that the timing is specific to the hour and minute. It is advised to use at least 1 week instead.
At least 1 week means the guide becomes available again 7 or more days after the user last saw it.
This option is more flexible and ensures the guide reappears after a minimum of seven days, even if the user misses a specific date.
In either case, the guide will never start twice within the same week period (Monday through Sunday).
Example: If a guide’s Autostart condition is set to at least 1 week and it is also listed in context help:
The guide's Autostart triggers on Monday of week 1.
The next Autostart trigger will occur on Monday of week 2 or later.
If the user manually starts the guide from context help on Wednesday of week 1, the next Autostart will instead trigger on Wednesday of week 2 or later.
In short, the frequency timer always begins from the last time the guide was started, regardless of the trigger method.
User attribute
Targets specific users based on values set in custom fields. This allows you to control which users can see or start a guide or journey.
All conditions defined within a guide are evaluated with AND logic, meaning every condition must be true.
Multiple values within a single custom field are evaluated with OR logic, meaning only one of the values needs to match.
Between different custom fields
AND
All conditions must be true
Within a single custom field
OR
At least one value must match
Example 1: Single Custom Field A user has a custom field called Job Title with values such as Manager, Director, and President.
Condition: Job Title is “Manager”, “Director”: The guide is available to users whose Job Title is either Manager or Director.
Condition: Job Title is NOT “Manager”, “Director”: The guide is available to everyone except users with Job Title set to Manager or Director.
Example 2: Multiple Custom Fields When two or more custom fields are used, all conditions must be true for the guide to appear or start.
For example, there are two custom fields:
Job Title: Manager, Director, President
Department: Sales, Engineering
A guide includes two conditions:
Job Title is “Manager”, “Director”
Department is “Sales”
The guide will only Autostart for users who have:
Job Title = Manager or Director and
Department = Sales
Device attribute
Targets users by device entity or country. Define conditions with is one of or is not.
Key pages
Defines where a guide should appear in Context help. Helpful for displaying only the most relevant guides for each page or section.
RELATED TOPICS
Last updated
Was this helpful?