User roles and permissions
A user’s access role within ChartHop determines what data they can see within the org and what actions they can take within ChartHop. Access roles are the broadest way to grant employees access to ChartHop.
For example, users with the Owner role can create new surveys, while users with the Employee role can only take surveys and cannot create them. Users in your organization with the Recruiter editor role can create new jobs in ChartHop.
Each role includes the permission of standard access, which means access to the non-administrative features of ChartHop, including shared Scenarios for review purposes. Administrative tasks, such as creating new surveys or importing employee data, are restricted to those with advanced access, such as an Org editor, Owner, or Technical owner role.
Assigning access roles to the members of your organization should be a thoughtful process and follow the principle of granting users only the permissions they need and no more than that. For several roles within your organization, including members of HR, recruiting, finance, IT, and more, additional access may be appropriate, depending on your organization's needs.
For roles with access to sensitive data such as personal information for employees, you can further filter what data those that role can see. For example, you can assign the Org editor role to multiple people in your organization but filter each person to have those permissions only in their department or division.
ChartHop Basic provides two access roles to assign to employees in your organization: Owner and Employee. Non-employees cannot be allowed access.
The following table gives a general overview of each role. Select the role name to view more specific details on pages and data that the role can access.
Allowed to see their own personal information and the compensation data of anyone in their reporting line. This is the default access level appropriate for most organization members.
The same access as an employee but can see cash compensation data, including cash compensation for individuals outside their reporting line.
Same as an employee but can see all compensation data, including both cash and equity.
The same access as an employee but without permission to view compensation data for those in their reporting line.
The same access as an employee but can see all equity compensation data, including equity compensation for individuals outside their reporting line.
Can view org public data. Recommended for users outside the organization. Users who are org members can also see their own personal data but not the sensitive data of individuals in their reporting line.
Access to all sensitive data, including compensation, with the ability to edit and make permanent changes to the primary environment. Does not have admin capabilities such as the ability to install applications or change organization-wide settings.
Allowed full access to everything, including inviting new users and assigning roles. They can also configure integrations, and manage organization-wide settings. Because of the scope involved, this access should be tightly restricted.
Same as an employee and can view open jobs and the sensitive data associated with those jobs, including target compensation.
Cannot merge scenarios but can create view scenarios shared with them.
Same as employee but can create open jobs in the primary timeline as well as in scenarios.
Allowed to view and edit sensitive information about open jobs, including target compensation levels and other sensitive data.
Same as an employee but can also see all sensitive data except compensation for those outside their reporting line.
Sensitive data viewer
Same as an employee but can also see all sensitive data, including for those outside of their reporting line.
Allowed to create and invite new users as well as assign user roles. Can configure apps and integrations, update custom fields, and alter organization-wide settings. However, they do not receive direct access to sensitive people data in the application. Because of the ability to configure data access and API keys, a Technical Owner could indirectly establish access to sensitive data (although such activity would be auditable). This role should be granted with care to the appropriate IT staff.
The following roles are deprecated:
- Time Off Viewer
- Personal Contact Viewer
Access remains unchanged for users who have already been assigned these roles. You cannot assign new users these roles.