A User Role can be defined as “what a user can do," and each Role is made up of a collection of Permissions. A Permission is a specific activity type or behavior that can be checked for "On" or unchecked for "Off" for any Role. A checkmark indicates that Users assigned to this role are permitted to take the defined action. No checkmark indicates that Users assigned to this role are restricted from taking the defined action. For unique access scenarios, we recommend that an Admin follow the steps to Create New Roles.
For example, let’s assume you wanted to have a custom User Role called “Generalist,” and you wanted users with that role to be able to process applicants but not Post Jobs. In that scenario, you would enable all checkboxes within Applicant Tracking and Processing and exclude all checkboxes from Jobs & Templates. Any User that you assign to the Generalist Role would be able to process applicants but not create job templates or post jobs.
User Role Permissions
Hiring system access and visibility are dictated by every registered user's assigned Role. Each User Role is broken down into individual permissions based on key areas of functionality:
- System Setup
- Content Management
- Jobs & Templates
- Applicant Tracking and Processing
- Visibility
- Integrations Access
Permissions can be adjusted as needed per User Role, with the only exceptions being the System Administrator and Read Only. These two system default User Roles cannot be modified, and will always behave as designed. The other two default system User Roles, Manager and Standard User, can be updated/modified.
Roles and Permissions can be reviewed, changed, or created at any time under Admin > Roles by clicking on existing Role titles or by clicking Create New Role.
Note: Updating User Role permissions is a global behavior. For example, if you update the "Hiring Manager" Role and disable the ability to Post/Close/Pause Jobs, as soon as you click Save, all Hiring Managers within your hiring system will not be able to post, close, or pause a job in the system.
Tip: For unique access scenarios, we recommend that an Admin follow the steps to Create New Roles.