Job Admin levels are defined sets of permissions that are granted to Job Admin users on a per-job basis, and permission stripes are the individual permissions that can be assigned to or removed from each Job Admin level. In this article, we will discuss the implications of the Can advance candidates / prospects permission stripe.
To learn more about configuring Job Admin levels and view a full list of available permission stripes, see the following articles:
- Edit or Delete Job Admin Level
- Create New Job Admin Level
- Job Admin: Custom
- Job Admin Levels and Permission Stripes
Note: Only organizations with an Advanced or Expert subscription can customize the permissions associated with Job Admin levels. Organizations with an Essential subscription cannot edit existing Job Admin levels or create custom Job Admin levels.
As the name suggests, the Can advance candidates / prospects permission stripe allows Job Admins to advance candidates on jobs or prospects within pools, and functions similarly to the Can reject candidates / prospects permission stripe.
If a Job Admin does not have the Can advance candidates / prospects permission stripe on a job, they will not see the Move Stage option available, and will be able only to leave feedback for the candidate or prospect. In the example below, the Job Admin has the permission stripe for Can reject candidates / prospects, but does not have the permission stripe for Can advance candidates / prospects.
Job Admin users without this permission stripe cannot advance a candidate during Application Review, and will have only the option to leave feedback.
Granting the permissions to advance or reject candidates to only some Job Admins can be a good way to train your team on hiring best practices. Rather than giving all users complete control on a specific job, you can allow them to provide candidate feedback in Application Review without the threat of them making a bad decision, or rejecting a candidate without following your team's typical rejection process.