User Roles and Permissions
User roles define the abilities of a Zappi user. The role you are assigned will change what you can see and do on-platform.
Jump to:
Admin
- Fully configure their organization's settings, including:
- Set product-specific configuration defaults
- Build tag taxonomies
- Decide which tools other users can access within the same organisation
- Add Auto-Join domains
- Invite and manage users
- Manage and transfer all shared credit
- Create, edit, launch and share any projects
- View a log of all projects configured and launched on Zappi
- Analyze any report
- Download all surveys and stimuli
Power User
- Invite users
- Share credit
- Create, edit, launch and share personal projects
- Edit, launch and duplicate public and shared projects
- Can see/analyze all reports across the entire organisation
- Download all surveys and stimuli
User
- Create, edit, launch and share personal projects
- Edit, launch and duplicate public and shared projects
- Analyze personal and public reports, plus download their surveys and stimuli
Viewer
- View shared projects
- Analyze shared reports, and download their surveys
- View public projects
- Analyze public reports, and download their surveys
Adjusting and Troubleshooting Roles
Admins have the ability to invite and deactivate users, as well as adjust a user's Role.
Adjusting Roles
Admins can go to the avatar menu and click on "Users & Groups" to see who currently has access to the domain, and to invite users, or edit their permissions.
Troubleshooting Roles & Permissions
When approached by a user with questions about specific permissions, admins should first inspect the user's role.
If the user is set to a role that is more limited than they need, the admin will need to consider changing it. This ensures there is governance in place and that research is only shared as broadly as you see fit.
For example, a user has reached out saying that they are unable to change the configuration of a question and then launch a project. An admin should first inspect this user's role; in this case, they find the user is a Viewer, and while they can view the project that's been shared with them, they are not able to edit or launch it. The admin can simply adjust the role to something less restrictive (like "User" or in this specific example, "Power user", as shared configuration can only be edited by Power users or Admins), or reroute the request to ensure only someone who already has the proper access makes the edit and launches.