Once an App has been deployed to a Project Team, Team Owners can configure various levels of access and permissions for end users as needed for your use case.
Checkbox supports both role based and app based permissions for end users.
What is the difference between "Default Role Permissions" and "Member Specific Permissions"?
By default, every user in a Team will belong to a given role, typically a team 'Member'. For each App in your team, you can configure the default level of access for all users who are Members.
You can override the default role permissions by setting Member specific permissions. In the screenshot above, John Smith as a Member, should only be able to 'Create and Edit own Assessments' for this App based on the default Member permissions granted.
However, because the Team Owner has set a member specific permission for John Smith, he can additionally view all assessments as well.
Permission levels and actions allowed
Permission | View data | Create assessment | Edit assessment | Delete Assessment | View Transcript & Documents | Change Assignee | Send Reminders |
Edit own assessments | Own | No | Own | Own | Own | No | No |
Create & edit own assessments | Own | Yes | Own | Own | Own | No | No |
Create, Edit own & view all assessments | All | Yes | Own | Own | All | No | No |
Team Owner | All | Yes | Own | All | All | Yes | Yes |