Overview
In this article we will review a real-case scenario of integration with HRS system. You will learn how to maintain control and allow different personas in your organization to view data that is relevant to their role without compromising sensitive information.
Example
Let’s imagine you are an admin in Quantive Results. The HR team in your organization has 2 main initiatives this year:
Boost employee satisfaction - Collaborating closely with team managers, the HR team will focus on improving the Employee Net Promoter Score (eNPS). Managers will take ownership of a Key Result centered around improving the average eNPS for their respective team members.
Standardize salaries across similar positions – the HR team is aiming to create a comprehensive Insightboard that presents detailed information on the average salary per position across all countries in which the company operates. To measure progress towards this goal, a Key Result will be assigned, tracking the percentage of salary alignment across different positions.
The information for both eNPS and salaries lives the HRS platform, and you’ve been asked to setup a connection to Quantive Results so that people can measure and track the respective progress.
To prevent sensitive data leakage, you need to allow different teams to access different sets of information.
This is how the configuration should look like
The HRS Data Connection permissions:
On data connection level you define who will administrate the connection and its data sources. Make sure to include the responsible people.
Everyone in HR team has full permissions
Everyone in Admin can Read and Edit (so they can re-authenticate if needed)
Each Data Sources should have different permissions:
On Data Source level you define who will have access to a specific set of information and use it to create insights.
Survey Results – contains scores and survey answers the employees give. This data is used for the eNPS calculation
HR Team – Read permissions
Everyone with permission role Manager – Read permissions
You and Admins – full permissions
Employee Detailed Information – contains people's salary information. This is sensitive information accessible to the HR team only.
HR Team – Read permissions
You and Admins – full permissions
Employee Profile – contains general information about people like name, team, manager, position. This Data Source does not contain sensitive information and is required for filtering people by teams (for the eNPS calculation) and position/country (for the standardizing salaries initiative); thus, it should be accessible to everyone.
Everyone in the account – Read permissions
You and Admins – full permissions
Result
People with Manager role will be able to create insight to calculate the eNPS, filter by their team members and automate KRs. This insight will also be accessible to everyone in HR team and users with admin role.
HR team members will be able to create insights and calculate the average salary per position and country. Users with admin role will have access to this insght; users with Manager role will not have access to it (it will not be listed in the Manage Insights section).
Everyone will be able to use the information for employees details to create insights.
Note: In any of the above insights is added to an inisghtboard, the visibility to the displayed information is controlled by the Insightboard permissions.
Best Practices
Pro-tip: To ensure continued data set management in your absence, always grant complete permissions to at least one other individual, ideally with admin role in Quantive Results.
Pro-tip: To create insights and automate KRs and KPIs, users must hold the Manage Data permission within their assigned role. The default admin and data roles include this permission.