Skip to content
English
  • There are no suggestions because the search field is empty.

Permissions an Admin can adjust

The switches under Roles & Permissions that let an Admin widen or narrow what hiring managers, Members, agencies and HR can do.

The switches under Roles & Permissions that let an Admin widen or narrow what hiring managers, Members, agencies and HR can do.

This article is for Admins. Role access in Recruit has a standard setup, described in Understanding roles and permissions. The switches below change parts of it. Each starts off, except the notifications switch, which starts on.

Where to find them

Go to Settings, then Roles & Permissions in the Team & Access group. The switches are grouped as Pipeline permissions, Candidate access permissions, Agency permissions, Approval permissions, Notification permissions, Interview permissions and Template permissions. An Admin can change every one. An HR user can see some of them, but only the pipeline switches can be saved by HR. The others appear greyed out under the note "Only administrators can change these settings."

Older settings pages that used to hold some of these now show a note such as "Pipeline permissions have moved to Roles & Permissions", with a Go to Roles & Permissions button.

Pipeline and candidate access

  • Allow hiring managers and interviewers to move candidates: when off, only Admin, HR and the job's Recruiter can move, reject or withdraw candidates. Stage visibility rules still apply on top. Reactivating a rejected application is not covered by this setting.
  • Allow hiring managers to edit a candidate's sub-status: lets Hiring Managers change a candidate's sub-status.
  • Hide candidate CVs from Members: when on, Members cannot view, preview or download CVs anywhere. Admin and HR are unaffected.
  • Allow Hiring Managers to add a CV: a Hiring Manager can then add the first CV for a candidate on a job they are assigned to.
  • One switch per offer type, in Candidate access permissions: a Hiring Manager can send a draft offer of an allowed type after an Admin or HR user has saved it. Nobody but Admin and HR can create, edit or withdraw an offer. Admin and HR can always send every type. Reviewing and sending a draft offer as a Hiring Manager explains the Hiring Manager's side.
  • Show gaps on anonymised applications, under the card Anonymised applications: when on, hiring managers see gap dates and explanations on anonymised applications, without employer or qualification names. The free text of a gap whose reason is Medical is withheld, notes under other reasons are shown, the gap analysis PDF is not offered, and every view is recorded in the audit log. Admin can change it. HR can see it but not change it.

Agencies, approvals and notifications

  • Let agency users see their candidates' pipeline status: when off, agency users cannot see which stage their candidates are in.
  • Enable admin bypass lets Admins skip the approval workflow. Allow editing of job details after approval opens job details and the justification for editing by Admin and HR.
  • Allow people to edit their own notifications: on by default. Turned off, everyone follows the organisation defaults. Setting organisation-wide notification defaults explains what people then see.

Interviews and templates

  • Allow Hiring Managers to manage interviews: a Hiring Manager can then create, edit and publish interview events, send invitations and manage bookings on jobs they are assigned to. Exporting bookings still needs Admin or HR. Without the setting, a Hiring Manager who tries sees "You don't have permission to manage interviews on this job." Letting Hiring Managers manage interviews has the full steps.
  • Allow Members to create and edit their own feedback templates: Members can then create shortlisting checklists and interview feedback forms, edit the ones they created and copy existing ones. They cannot delete or archive templates, or change video interview templates. A Member who opens a template they did not create is told "Only the person who created this form, an Admin or HR can change it. Use Duplicate to make your own copy." Letting Members create feedback templates and checklists has the full steps.

Job privacy settings

Settings on each job also change what people see. On a job's Settings tab, Confidential Shortlisting hides candidate details from the hiring team, Recruiters included, until an identity is revealed. That happens either by hand, or automatically when the candidate reaches the reveal stage. Blind Scoring hides reviewer identities from everyone except Admin and HR. On a shortlisting stage, Reviewer Scoping limits non-recruiters to their own evaluation.

Only Admin, HR and the job's hiring lead can change these on the job's Settings tab, whatever role they hold on the job team. Organisation-wide defaults are under Settings then Shortlisting. Blind scoring and confidential shortlisting have their own article, Blind scoring and confidential shortlisting.