The Playlist feature in Motivity allows you to assign specific targets or programs to specific roles—like caregivers—so that only intended users can view and collect data on those items. This is especially helpful when you want to ensure that some users (e.g., RBTs) don’t see or interact with targets that are not relevant to them (e.g., parent training goals).
What Is a Playlist?
A Playlist is a way to restrict visibility and data collection access for certain programs or targets to specific session types or roles.
- Think of it like a “custom view” of programs for different roles.
- Most commonly used for caregiver/parent roles or special assessments.
For example, you might create a caregiver playlist so that only caregivers can collect data on certain parent training goals—and those targets are hidden from RBTs.
Playlist Setup:
Step 1: Create the Playlist in the Program
For each program or target you want in a playlist:
- Go to the program or target’s Properties section.
- Add the following tags:
- #playlist → Marks it as part of a playlist
- #daily → Allows it to be visible all day (not session-bound)
- Make sure the tags are written exactly the same across both program properties and session types.
Capitalization and spacing matter—keep them consistent.
Example:
#caregiver #playlist #daily
Step 2: Create or Edit Session Types
To assign playlists to specific roles:
- Go to Roles & Permissions.
- Choose the role you want to update (e.g., caregiver, RBT).
- Under Session Types, add or remove playlist tags as needed.
Examples:
- For RBTs: Only include session (default), so they do not see playlist items.
- For Caregivers: Include #caregiver #playlist #daily so they only see those items.
Step 3: Collecting Data with Playlists
- Caregivers will log in and immediately see the targets assigned to them (outside of a formal session).
- RBTs will not see these targets unless explicitly given access.
- Data Collection View: Playlist targets will appear as a dropdown list and are not housed within a session.
You can also create multiple session types if needed (e.g., one for IOA data collection). See this article: