Limiting Task Visibility

During study setup, there may be instances where Admins wish to surface distinct Tasks to specific participants to create designated pathways or tailored follow-ups. This can be done by customizing a Task’s visibility settings. 

These Visibility settings allow you to restrict a Task’s visibility to a specific group of participants based on defined criteria, including segment, previous task response, task completion, and activity completion. 

Restricting Visibility at Activity vs. Task Level

Recollective allows you to restrict the visibility of an entire Activity (and all Tasks within it) using Segments. This method is ideal when all Tasks within an Activity are relevant to everyone within the chosen segments.  

However, there may be cases where the content of one or more Tasks does not apply to all users with access to the Activity. In such a case, you can leverage Visibility Logic to restrict the visibility of a Task to a specific group of participants. This is ideal when:

• You want all participants to access an Activity, but have specific questions that apply only to a subset of participants 
• You want to restrict the whole Activity to specific Segments of people AND also have specific questions that apply to a further subset of those participants
• You want to create branching pathways to control content visibility based on previous responses

How To Limit Task-Level Completion

Each Task contains visibility settings that allow you to restrict its visibility to a specific group of participants based on defined criteria. These settings can limit visibility by segment, previous task response, task completion, and activity completion.

To limit Task Visibility, follow these steps:

1. Scroll to the Visibility section and click the Add Criteria button
2. Select from the following options in the drop-down menu:
   1. Task Response: Limit visibility based on how participants responded to a previous Task.
   2. Assigned Segments: Limit visibility based on participant segment assignments.
      • Note: The selected segments must have access at the Activity level to view the Task. 
   3. Task Completion: Limit visibility based on whether a participant has completed a specific Task.
   4. Activity Completion: Limit visibility based on whether a participant has completed a specific Activity. 
3. Define the conditions of the selected criteria
4. Optional: Click the Add Criteria button to further refine your visibility
5. Choose whether participants will need to Match All or Match Any of the criteria
   1. Match Any: The Task will be visible to participants who belong to any of the selected Criteria.
   2. Match All: The Task will only be visible to participants who belong to all the defined Criteria. 
6. Click Set Visibility
7. Give your Task a name. It will now only be visible to the participants who match the defined Criteria.

When a task is limited to criteria and activity responses are socialized, participants will only be able to see the responses to the Tasks they had visibility of. Participants outside of the defined criteria cannot view the responses, even if they have access to the activity in which the task is housed.

Editing Tasks With Visibility Limitations

After saving your visibility criteria, the Visibility section will display a summary for easy reference. You can return and edit these criteria at any time by clicking Edit.

You can also review and edit a Task’s visibility criteria from the Activity page. Tasks with Visibility Logic will display a hoverable icon. To quickly edit a Task’s visibility, simply click on the dropdown on the Task card and select Task Visibility.

Editing Tasks With Dependencies

If you have configured Visibility Criteria that rely on Task Responses, then the Task where those responses were collected will have a section in the Task Setup page labelled Dependencies. This indicates that the configuration of this Task impacts the visibility of future Tasks.

When making changes to a task that has dependencies, we recommend reviewing the tasks listed in the Task Dependencies section to ensure your edits will not disrupt your desired task flow.