There are two types of permission that need to be understood to use Applied effectively:
Org-level permission and job-level permission.
Org-level permission
When you first add a new user to the platform as a member of your organistion/company, you must decide what org-level permissions to grant. This determines their level of control over things that apply to the whole company/organisation, such as email templates, company settings, your careers page and aggregated reports. You have two choices:
An admin user, with unlimited access to the platform;
This means the user can update company settings; view and manage all vacancies posted by your organisation; access candidate data for all vacancies; view reports on a vacancy-by-vacancy basis; and view aggregated reports for the whole organisation. Admin permissions should ordinarily be reserved for people whose job it is to oversee hiring in your organisation (normally members of the Talent or HR function).
Or a standard user, with restricted access to the platform.
Standard users have very few permissions by default. They cannot alter the organisation’s settings or add new users; they can't view aggregated reports for the whole organisation; and they can only access those jobs that they have been given explicit access to. The level of access granted to a Standard user is determined from role to role, and is outlined below.
Job-level permission
Each new job/vacancy that you add to the platform will need its own hiring team: the people who will help you make a good, balanced decision about who to hire. When you add someone to the hiring team, you will have the opportunity to set more granular permissions governing what they can see and interact with.
So first ask yourself:
Who should be able to view, edit and manage this job and its candidates?
and
Who will help us assess, review and interview the candidates that apply?
Contributor
Contributors can be invited to review sift responses and CVs anonymously and can take part in interviews. They cannot access the ‘build’ section (where details of the opportunity are outlined) or the ‘manage’ section (where candidates are tracked, engaged and progressed). This is the lowest access level for a role.
Hiring Manager
Hiring Managers can be invited to review sift responses and CVs anonymously and can take part in interviews, just as contributors can, but they can also access the ‘build’ section (where details of the opportunity are outlined). However, they will not be able to access the ‘manage’ section (where candidates are tracked, engaged and progressed).
Limited Access Hiring Manager
If you wish, you can further limit a Hiring Manager to just a handful of key fields in the ‘build’ section. These sections are:
- Job description
- Skills
- Any hiring stages that have been added to the role
- Interview stages
This allows the hiring manager to access and focus on only those sections where they can provide the most value to you and your team without distraction.
Job Admin
A Job Admin has full access to manage and administer the job. They can invite others to review sift responses and CVs, as well as take part in assessments themselves. They can access the ‘build’ section (where details of the opportunity are outlined), the ‘manage’ section (where candidates are tracked, engaged and progressed), and the 'report' section (where metrics are tracked).
Please note, if a user is given Admin User permission at the org-level, they can ONLY be a job admin at role-level. This is because they already have unrestricted access to the whole platform.
PERMISSION |
STANDARD USER |
ADMIN USER |
||
Contributor |
Hiring Manager |
Full Access |
||
View and access roles listed on the Dashboard |
Only when on the hiring team |
Only when on the hiring team |
Only when on the hiring team |
Yes |
Add, edit or remove other users at platform-level |
No |
No |
No |
Yes |
View aggregated diversity data and hiring stats for the organisation. |
No |
No |
No |
Yes |
Add contributors to a hiring team |
No |
Only when on the hiring team |
Only when on the hiring team |
Yes |
Add hiring managers to a hiring team |
No |
Only when on the hiring team |
Yes |
|
Grant full access on a hiring team. |
No |
No |
Only when on the hiring team |
Yes |
View and edit the job settings via the ‘Build’ tab. |
No |
Only when on the hiring team |
Only when on the hiring team |
Yes |
View and manage candidates via the ‘Manage’ tab. |
No |
No |
Only when on the hiring team |
Yes |
View job-related data via the ‘Reports’ tab. |
Only when on the hiring team |
Only when on the hiring team |
Only when on the hiring team |
Yes |
Be invited to review applications anonymously (both sift and CV) |
Only when on the hiring team |
Only when on the hiring team |
Only when on the hiring team |
Only when on the hiring team |
Be invited to interview candidates |
Only when on the hiring team |
Only when on the hiring team |
Only when on the hiring team |
Only when on the hiring team |
Be invited to compile feedback for rejected candidates |
Only when on the hiring team |
Only when on the hiring team |
Only when on the hiring team |
Only when on the hiring team |
Most users will be standard users who have been allocated a role on a particular hiring team. The role they are allocated from job to job will govern their specific access.
Please note that it is possible to switch on and off these permissions at any point if you made a mistake or changed your mind.
Comments
0 comments
Article is closed for comments.