<aside> 💡 Ashby supports opening, job, and offer approval processes.

</aside>

Approvals can be set up on the following plans:

Foundations Legacy Plus Plus

Section overview:

Approvals overview

You can create an approval process when multiple stakeholders need to review and sign off on a workflow. We currently support opening approvals, job approvals, and offer approvals. You can set one or more approvers at each stage of the approval process.

When would I use each type of approval process?

Approval Type Use Case Common Approvers
Opening Approval Commonly use to validate that headcount has been approved by finance. Finance, Talent
Job Approval Commonly used to ensure the accuracy of the interview plan stages and other job settings and the quality of job postings. Talent
Offer Approval Commonly used to ensure appropriate stakeholders have reviewed offers. CEO, Finance, Talent, Hiring Manager

Create and configure an approval process

Create a new process

Navigate to Approvals in Admin to build an approval process. Before you click + New make sure that you’ve selected the correct object type tab. Options include:

https://cdn.zappy.app/bf102370483db9901175edd9ad3b12a8.png

Configure a new process

To configure a new process, you’ll select the scope, add steps, and add approvers to each step. The scope triggers the process to start, the steps are the rounds of review. The approvers are the specific stakeholders completing the review.

You can include multiple approvers at each step or select a pool of users based on their role on the job consideration. You can then choose whether all, one or some approvers need to provide approval.

Once you’ve created your approval, click Create. Once the approval has been created, you will have the option to edit, take a copy of, or archive your approval process.

Ordering the process list

https://cdn.zappy.app/2cbaecb3b0dcef51e748c42cc153940f.png

https://cdn.zappy.app/259b5f684366610845b5ccd2cdf0d6a9.png

https://cdn.zappy.app/47890b2d96c0135970bad878e874d3e5.png

Activated processes in the list are processed in order. If multiple processes have a scope that would apply, the one highest in this list will be used.

You can drag and drop each process to re-prioritize as needed.

https://www.loom.com/share/b88bca5adf924ac9b4ecd04831802675

Example scopes

<aside> ☝ Setting the scope is highly flexible, but the most common options selected are the department and the role. Examples of each are below.

</aside>

Scope by department

In this example, the scope is set to the department. All job considerations that an offer is generated for in the engineering department will follow this process.

https://www.loom.com/share/cf690af4dda746bbabfdb8985f24c141