User & Permission Management – MyDataHelps™ Designer Help Center

MyDataHelps Designer employs a sophisticated team- and institution-based access control system. A single individual may be assigned to multiple teams, projects, or institutions within an organization, based on their specific responsibilities. For example, a coordinator in a multi-site study may be assigned to the study team at their specific site or institution, meaning they have access only to participant information at their location.

Table of Contents

Setting up Teams
Managing Users

Setting up Teams

User permissions within MyDataHelps Designer are controlled by a user’s assigned team. In order to get started with permissions, you’ll want to create teams and then assign permissions to those teams.

An “Everyone” team exists for all organizations, with some defaulted permissions that you should review and potentially adjust. For an organization with many users, it is recommended to remove all permissions from the “Everyone” team until users have been assigned to a more specific team.

Creating a Team

From Organization Settings, click on "Teams”.
To add a new team, click “Add Team”.
Provide a name for your new team, e.g. Study Coordinators.
Check off all of the appropriate permissions for this team. See below for an overview of permissions, including recommended teams & permissions.
Click “Save” once you are satisfied with the selected permissions.
If necessary, you can edit a team’s permissions by clicking the red trash can icon. If you need to delete a team, click the icon.

Demonstration: Creating a Team

Permissions

Now that you have a new team, you’ll want to assign permissions.

Organization Permissions: Apply to all notifications and settings within the organization.
All Project Permissions: Apply to all projects within the organization.
Project-specific Permissions: Apply only to specified projects. Your organization must have projects for this to be available. Select “Add Permissions for a Project” and “Add Project” to enable.
Segment-specific Permissions: Apply only to specific segments within a project. To apply these permissions you must:
- Have projects that have segments.
- Have “View/Manage Segment Participants” checked within the specified project.
Institution-specific Permissions: Apply to only specific institutions within a project. To apply these permissions you must:
- Have institutions in your project.
- Have "View/Manage All Institutions" unchecked within All Project Permissions.

Demonstration: Segment-Specific Permissions

Permissions Reference

The following tables summarize what each permission controls within the organization/project.

Organization Permissions

Permission	Description
Notification Author	Access the notifications screen, and manage all notifications for the organization.
Organization Settings	View and edit organization settings, users, and teams.
Survey Author	Access the surveys screen, and view and edit all surveys in this organization.

Project Permissions

Permission	Description
Data Export	View and update data export settings, and view the export history.
Delete Participants	Delete participants from a project.
Invite Participants	Invite participants to a project.
Project Builder	Create and edit projects, update project settings, create survey schedules, create segments, and select sensor data to collect.
Segment Actions	Invoke batch actions (send survey or notification, close survey, or set custom field) on participant segments.
Survey Publisher	Publish surveys.
View/Manage Participants in All Institutions	View, add, and edit participants in specified institution(s). Only available within project-specific permissions.
View/Manage Segment Participants	View, add, and edit participants in specified segment(s). Only available within project-specific permissions.

Suggested Teams/Roles

The following teams are recommended for any given organization.

Role	Responsibilities Description	Experience and Skills Recommendations
Organization Owner	Has access to all projects for a given organization. Will have access to PII/PHI across the projects within the organization. Full CRUD (Create, Read, Update, Delete) rights across projects such as ability to: authorize additional users; delete patient/participant data; delete projects; update project communications	Typically an individual with direct authority over projects or works directly for such an individual as their technology extension/designate. Ideally should have prior experience in working with enterprise technology platforms that require user account management (authorization/access control review), handling PHI/PII, and generally facile with new technology.
Survey Designer	Create and build surveys	Understands the goals of the project and what needs to be captured Understands how to code captured survey data appropriately for later analytics Has knowledge of best practices of user interface design
Survey Publisher	Create and build, review/publish, and schedule surveys in production	Similar to a survey designer, but designated as an individual with final approval on when a set of survey changes can be released to participants
Notification Author	Create and test notifications	A marketer or someone with experience with CRM tools and who is familiar with the mechanics of push notifications, SMS messages, and html emails
Project Administrator	Manage a specific project, including the ability to inspect participant data, schedule surveys, and change global project settings	Understands who on their team is responsible for what tasks, and can assign roles based on need and skill level If a multi-site study, this role may only have access to certain institutions
Invitation Manager	Add participants to one or more projects and send them an email invitation to join the project, or update participants in bulk	Understands organization recruitment needs and processes As needed, can manage multiple lists/segments of interested parties’ contact information As needed, a marketer with CRM tools If a multi-site study, this role may only have access to certain institutions
Participant Support	Access to view and manage participants / PHI, including: Ability to complete coordinator surveys Access to view submitted surveys, HealthKit / Google Fit data, connected accounts (like Fitbit), and history of notifications sent Ability to deliver surveys to individual participants Ability to process withdraw requests, removing participants from study.	Ability to clearly communicate over email or phone with participants of varying degrees of tech-savviness Understands the questions to ask to problem solve most issues without tech support (e.g. login issues) Possesses general knowledge of smartphone and devices If a multi-site study, this role may only have access to certain institutions
Data Export Manager	Ability to manage data export settings and download previously exported data	IT Experience with setting up data transfer and/ organization approval/training to handle large amounts of PHI

Managing Users

After setting up your teams, you’re ready to add users to those teams and edit institution permissions.

From Organization Settings, click “User Access”.
In the bottom right, enter the username or email address for the user and click “Add User to Organization”.
Check the end user being added is correct and click “Confirm”.
Select the appropriate team from the “Add to Team” dropdown.
If you are running a multi-site project, select the appropriate institution from the “Institution” drop-down.
If necessary, click the gray trash can item to delete a user. You can also click the “X” in their assigned team or institution to remove them from that team or institution.

Users can be added to multiple teams and institutions to ensure they have all necessary permissions. For example, if you are using our suggested teams, you would likely want to assign someone on the Project Administration team to the Study Coordination and Data Management teams as well so that they can oversee the project, interact with participants when needed, and export data. When a new organization is created, the "Everyone" team will have the "View/Manage Participants in All Institutions" permission selected, meaning users will default to having access to all institutions unless set-up otherwise.

Demonstration: Managing Users

In the event that an organization’s ownership needs to be transitioned to another user, you can click the “Transfer Ownership” button next to the appropriate user.

Articles in this section