Security roles based permissions allow administrators the ability to set granular access to their users.
As an administrator, you have the ability to create new security roles and modify them as you see fit. However, you must really understand what a security role is and how it may affect your users.
Most functionality on DutySheet is controlled by permissions. These permissions range from being able to send an email to be able to edit the contact details of a user.
You then set up a security role where you choose which of the available permissions should be applicable to that security role or not.
⚠️ Important: It is possible to assign a security role to a number of users, but then also deny certain users the rights that their security role may give to them.
Charge Levels
Another important consideration when setting up security roles are the charge levels. A lot of functionality that is available to non-volunteers for them to view information is free, level C1.
However, the core functionality of DutySheet, such is booking a duty/shift and being invited to an event is a fully chargeable permission.
There is also another charge level called C2, which is for lightweight users. These may be coordinators who themselves are not volunteers and will therefore never be booking a duty/shift for themselves, however, they may need to manage a team of volunteers.
When you create a security role, if any permission of a higher charge level is assigned to that security role, then all users of that security role will be charged at the higher charge level.
Example: You may create a security role with all permissions to be that of C1, however, if you assign one single C3 permission, then the security role becomes a C3 role.
Each permission is clearly labelled with their appropriate charge levels, as are each security roles.
You can, at any time, go to your organisations DutySheet Settings page where you will see a breakdown of your C1/C2/C3 users. (Historical and current figures.)
Troubleshooting User Specific Permission
DutySheet staff frequently receive emails from users who are asking why they can not perform a certain action or see a certain report. In most cases the problem can be solved by looking at their details and seeing what security role they have associated with them.
If the user has the default role that is associated with their role, then the system will say: Rank Security Role: [Role name].
The terminology of rank may be different for your system. If they were issued a custom role, then the system will display Custom Security Role: [Role name].
You can then check the permissions associated with that security role and make sure that security role has the required permission.
If it does and the user still doesn't have access to the required permission, then it may be worth editing their details and making sure they haven't been denied that specific permission.
Administrator Security Roles
Organisations are not able to assign their own administrators or modify the security role of an administrator.
You will never see your own security role as an administrator on DutySheet. If you believe your role is missing some permissions, please contact DutySheet.