Previously, changes to Administrator permissions required contacting the Customer Success team for changes to the instance configuration.
It is now possible to directly manage the 4 types of Administrator roles available in Confirm directly from the People administration section.
Those 4 types of Administrators are:
System administrators - full system access to your Confirm instance
HR Administrators - Access to specific groups of people across all campaigns
Engagement dashboard administrators - can view results of engagement surveys
Rating dashboard administrators - can view the rating dashboard and all Performance ratings
Each of the 4 types of Confirm Administrators are assignable by expanding the section of the People administration section that corresponds to the role.
To assign administrator access, simply click the section to expand it, and then click the blue button labelled “Add administrators”
When adding HR administrators, you may wish to restrict access to certain departments, locations, etc. Clicking the “Add” button brings up a window that asks you to specify the people who need administrative access, and the audiences for which they will be able to see data.
Once you add a condition to the Target audience text box, you’ll also see the option to add (or delete) additional conditions, and establish logical IS and IS NOT relationships between them.
So, for example, an HR administrator might need access to everyone in Engineering, and also everyone in the office in Italy (using the Match at least one condition operator):
Alternatively, they might need to see only Engineers who are located in Italy (using the Match every condition operator):
Filters also affect what Administrators see in terms of historical data. For example, an HR Administrator who can see members of Engineering will see everyone who is in Engineering at the time of the snapshot for the current cycle, as well as past campaigns for everyone currently in Engineering (even if they were not in Engineering at the time of a past cycle). Likewise, anyone who transfers out of Engineering during a cycle period will still be visible to an HR Administrator with permissions to view Engineering for the current cycle, but will no longer have their past cycles visible to this HR Administrator.
It is even possible to create nested groups of conditions. For example, an HR Administrator may need to see all of the Level 5 Engineers in Italy, and only these employees. They could create a set of conditions like this:
This condition set specifies that Department must be Engineering, but also, within this condition being met, the Country must also be Italy, and the employee Level must be 5.
The available conditions are: Business unit, Business unit ID, Cost center, Cost center ID, Country, Department, Department ID, Function, Function ID, Level, Level ID, Locations, Person, Manager, and Manager or above.
The Person condition is particularly useful when combined with the IS NOT condition to exclude certain people from HR Administrator visibility - for example, the CEO!
If your organization is using the Person condition in this way, remember to make it a top-level condition and use "Match every condition" to combine it with other conditions. This accomplishes 2 things:
The person is always excluded regardless of which other conditions are used to create the access group.
Meeting the exclusion condition for a particular person doesn't accidentally replace the other conditions.
Click the “Add administrators” button when finished adding conditions, and your newly-created administrators will display.