Approvals Engine overview
Updated at August 26th, 2026
Table of Contents
The Approvals Engine allows you to create a hierarchy of approval by which actions can be completed in the system. Once a request is submitted, then the assigned approver will be notified of the request and will either approve or deny it, ensuring that actions are made accurately and in line with management approval.
Use cases
- Management who wants visibility and oversight into the actions taken in the system, which currently include posting a job and/or sending an offer letter.
- Management who wants to maintain consistent business standards.
Configuration
The process for enabling Approvals is the same for all features. Click here to learn about this process.
Approvals process
The Approval Engine’s process is as follows:
- User creates an approval request from the My Jobs page (post a job) or the Candidate Inbox (send an offer).
- Approver is alerted of the request.
- Approver approves or denies the request.
- The next level approver is alerted of the request, if applicable.
- That approver approves or denies the request.
- Repeat steps #4-5 for each additional approver.
Approver level example
If 3 levels of approvers are set, the first being Mark Smith (Manager, Employer Brand), the second being Francisco Rivierez and Molly Andrews (Sr. Manager, Talent Acquisition), and the third being Naomi Lee (VP, Talent Acquisition).
The following process will occur when it comes to approvals:
- Hugo Reyez (Recruiter) submits an approval request to send an offer to a candidate.
- Mark Smith (Manager, Employer Brand) is notified of the request and then either approves or denies the request. If approved, then the request will move to the next reviewer.
- Francisco Rivierez and Molly Andrews (Sr. Manager, Talent Acquisition) are notified of the request and then one of them either approves or denies the request. If approved, then the request will move to the next reviewer.
- Naomi Lee (VP, Talent Acquisition) is notified of the request and then either approves or denies the request. If approved, then the request will be fulfilled.
Relevant documentation
Click here to learn more information about this feature.
Permissions
By default, no user roles have full access to Approvals. Users with full access to Roles and Permissions can provide users one or more of the following permissions:
- Approvals – The entire Approvals feature.
- Approval Flows – The section where approval flows are created and managed.
-
Approval Requests – The section where users review and act on pending requests.
- Full Approval Visibility – Determines whether a user sees all approvals across the Pending and Completed tabs, or only the ones assigned to them.
- Job Approvals – Whether job requests appear in the Approval Requests section of the Approvals page. Access can also be set individually for each job field in the job approval.
- Offer Approvals – Whether offer requests appear in the Approval Requests section of the Approvals page.
Job Approvals Permissions Notes
- Full Access to a job field allows users to edit that field when reviewing an approval request. All job fields default to View Access.
- For Multi-Location Jobs, Brand Name, Candidate Journey, Internal Title, Job Code, Job Description, and Locations job fields are view-only regardless of the user's access level.
- For Integrated Jobs, Brand Name, Candidate Journey, Hiring Team, Internal Title, Job Code, Job Description, Locations, Public Title, and Shifts job fields are view-only regardless of the user's access level.
If Full Approval Visibility is set to Full Access and Job Approvals or Offer Approvals is set to No Access, the For Review tab will be removed for those request types.