Is the employer pipeline the same as my operator applicant review?

No. The employer pipeline is the employer's own view of applicants for their company's jobs, scoped to their approved company membership. Your operator applicant review is board-wide and based on board ownership. They are separate surfaces.

Which applicants show up in the pipeline?

Only native applications submitted on your board. Jobs that send candidates to an external application URL do not produce applicants here, because your board cannot see what happens on the employer's site.

Does the applicant pipeline need a specific plan?

Yes. The built-in applicant pipeline (and native Quick apply) requires the Starter plan or higher.

Managing Applicants

The employer's applicant pipeline on your board, and how it differs from your own operator applicant review.

By Abi Tyas Tunggal and Jack Walsh

When a job uses native applications, the people who apply flow into an applicant pipeline the employer manages from their dashboard on your board. This page explains that employer-side pipeline and how it differs from your own operator applicant review.

The employer pipeline

An employer opens a job's applicants from their dashboard and works through them in a pipeline of stages, moving each applicant along as they review. Access is scoped to the employer's approved company membership: an employer only sees applicants for the jobs belonging to a company they represent.

How it differs from your operator review

Your board has two distinct applicant surfaces, and it helps to keep them separate:

The employer pipeline (this page) is the employer's own view, scoped to their company's jobs, authorized by company membership.
Your operator applicant review is board-wide and authorized by your ownership of the board. It is documented separately in review applicants.

They serve different people, so a candidate, a job, and an application can appear in both, viewed through each side's own lens.

Availability

Plan: The built-in applicant pipeline and native Quick apply require the Starter plan or higher.
Setting: None specific to the pipeline. It depends on jobs using native applications rather than an external URL, and on the employer having an approved company membership.
Setup required: None beyond a Starter (or higher) plan and jobs configured for native applications.

Limitations

Only native applications appear in the pipeline. Jobs that use an external application URL produce no applicants here, because your board cannot confirm what happens on the employer's site.
An employer sees applicants only for the company whose membership they hold approved.

Example

For example, an approved Acme recruiter can move applicants for Acme's native-apply role through its stages. They cannot see applications for another company's role, and an Acme job that sends candidates to an external ATS shows no native applicant records.

Next steps

Follow Review applicants for the employer's review actions and test one native application end to end. Use Employer accounts if a reviewer cannot reach the company dashboard.