Who is this article for? | Administrators |
After you finish this article, you will be able to: |
|
Choosing the right role type
Choosing the correct role type for your users is important as it determines what permissions a user has.
This article will describe the different role types that are available and examples of when you may wish to use them.
Recommended role types
Typically, your firm will need to use only two role types:
Administrator
Employee
These roles are suitable for nearly all staff at your firm. However, there are three additional role types for specific circumstances where a user may not be required to complete pulses, access the platform, or both.
Role types
Role type | Description | Use cases | Everperform recommends |
Administrator | Full access to the platform, administration settings, and all user passports | Managing Partners, Performance Advisory team, HR team, nominated system administrators | We recommend this role for <10% of the users in your firm. This role should be restricted to those who use the platform regularly and require visibility of all users. |
Employee | Able to complete pulses, view own performance, and view performance of subordinates. Both managers and individual contributors fall into this category. | Partners, managers, individual contributors, billable and non-billable staff. | Most users in your firm should have this role. |
Guest | Only able to complete pulses. This role cannot log into the platform and does not have measures imported. | Some contractors - for example, a person who contributes to a team but does not require access to the platform. | Case-by-case basis |
Measures only | As the name suggests, this user's measures are imported to the app but they do not complete pulses. | Some contractors - for example, a person whose measures are relevant to the organisation but who does not need to complete pulses. | Case-by-case basis |
Pulses | Able to complete pulses and log in but has limited access to the platform. | Some contractors - for example, a person who contributes to the team but does not require full platform access. | Case-by-case basis |