User permissions are important to help control access, maintain security, and ensure efficient workflow management. There are several different permissions configured on either an Organisation or a Team level.
Organisation Permissions
There are two permissions at the Organisation level either Organisation Administrator or Organisation User. Each Dapple user must be one of these two options.
Organisation Administrator
The Organisation Administrator is highest permission in the system. This access enables the user to all parts of the system. They have access to the Organisation Settings and to all Teams without restriction. Through the Organisation Settings they have access to billing info, can add other users including other Org Admin users, change user roles, add users to teams have access to all settings. When a user creates an Organisation, they will automatically be designated with this highest permission and it's worth noting that Organisation Administrators cannot be removed by any user.
Organisation User
The Organisation User essentially means you are not an admin. Organisation Users can be part of multiple teams and there are several team based roles that an Organisation User may have (see below) however it's worth noting that only Organisation Administrators have access to the Organisation Settings. If you are added to the system as a User but not assigned to any teams then you will have access to the system but will not be able to see any data.
Team Permissions
There are two permissions at the Team level either Team Manager or Team Member. Each Dapple user must be one of these two options.
Team Manager
The Team Manager permission enables a user to have manager access to specific teams within an organisation and will only have access to those teams they are members/managers of. Team Managers will have access to the Team Settings for their designated teams and will therefore be able to manage the settings for all the projects within that Team. They will also be able to upgrade any Team Users to Team Manager status. They will not have access to any of the Organisation settings and therefore not have access to billing info, won't be able to add other users to the system or add any Organisation users to their team.
Team Member
The Team Member access is for any users who are added as a user and then assigned to a specific team. Team Members will only be able to see the teams they have been added to. They will not have access to any Org or Team Settings and so will not be able to change any project settings or add other users and change user roles. Importantly, Team Members will be able to see and manage submissions for projects created in their teams and will be able to change the stage and status of submissions. They will also be able to send messages to creators.
Permissions Table
Those with Organisation Administrator permission will be able to see the permissions each user has.
How to view the Permissions Table
Go to Organisation Settings and select Users.
Find the correct user you'd like to see the permissions for and select View Permissions.
The top section of the table will display whether the user is an Organisation Administrator or a Organisation User. If they are an admin, you should see all of the boxes ticked green as this permission by default has access to everything within the system.
The lower part of the table will display all of the Teams created within the organisation and whether the user is a Team Manager or a Team Member of those different teams.
There are two different usage options within the system Read or Write.
Read means the user only has access to view this part of the system, they don't have access to make any changes.
Write access enables a user to make changes. This might mean changing a setting or sending a message.
If a user is a Team Manager your will see that all of the boxes within the table will appear as ticked green. If the user is a Team Member you will see some of the write options will be denied. If the user is not assigned to a team, it will show as No roles and all the boxes will be blocked.
To change the role of user follow see the How to Change a Team Members Permissions section.