Configuring roles and permissions
Where Admins and HR users adjust what each role can do in your organisation, and how those changes save and take effect.
Where Admins and HR users adjust what each role can do in your organisation, and how those changes save and take effect.
Roles decide the baseline of what people can do in Recruit. The Roles & Permissions page in Settings lets you adjust that baseline for your organisation: who can move candidates, who can see CVs, whether agencies see pipeline stages, which hiring manager abilities are switched on, and which locations an HR user can work in. For what each role can do by default, see "Understanding roles and permissions".
Who can open the page
Admins and HR users can open Settings > Team & Access > Roles & Permissions. Members, agency users, hiring managers and interviewers do not see the card, and if they reach the address directly they get the message "You don't have permission to view this page."
Opening the page and changing a setting are not the same thing. HR users can change the two pipeline switches. Everything else, including HR location access, can be changed by Admins only. HR users see the agency, approval and anonymised application settings, but the switches are greyed out and a line at the top of the page reads "Only administrators can change these settings." The other candidate access settings, the notification, interview and template settings, and the HR location table are hidden from HR altogether.
If your organisation manages subsidiary companies, a company selector appears at the top right of the page. Each setting applies to the company you have selected.
How settings save
Every setting is a switch. It saves the moment you click it, and a message confirms the change, for example "Pipeline permissions updated". If the save fails you see an error such as "Could not update pipeline permissions" and the switch stays where it was. There is no Save button. The switch is greyed out while a save is in progress.
The settings are grouped under seven headings, in this order: Pipeline permissions, Candidate access permissions, Agency permissions, Approval permissions, Notification permissions, Interview permissions and Template permissions. HR location access sits at the bottom of the page.
When changes take effect
The server checks these settings each time someone acts, so a change applies to their next action without them signing in again. Screens that are already open can be slower to catch up. The agency and notification settings are loaded along with a person's session, so someone already signed in may need to refresh the page to see the interface change, for example to see a hidden or read only notifications page. HR location changes apply the next time the HR user loads a job or candidate list.
If someone reports that they can or cannot do something you expected, first check the switch on this page, then check their role in Settings > Users, and ask them to refresh.