The job of this console
Advance or reject, keep the req attached, and convert a hire into Employee plus onboarding.
People · ATS
Candidates
People in the hiring pipeline — applicants on requisitions, not Employees until hired.
Scroll to Flowcharts. Scenario: Advance a candidate on a requisition.
Pipeline people
Applicants until they become employees
Candidates live on requisitions. They are not the directory, not timesheet users, and not a bench.
People → Candidates
Route
/recruiting/candidates
Org flag recruitingEnabled
HR Admin · Admin
Seat at the table
HR Admin and Admin. Interviewers see interviews, not necessarily the full candidate PII.
The working rhythm
Filter stage, open, move, schedule interview or offer. On hire, leave the ATS and open Employees.
Moments that bring you here
Screening dump. A duplicate email. Offer accepted. A withdrawn application.
ⓘ
Not the workforce register
Capacity, leave, and pay need Employee. Candidate PII stays out of Work Graph snippets.
Flowcharts
1 — Move a candidate stage
Filter, open, advance, hire into Employee.
flowchart TD
A[Open Candidates] --> B[Filter req / stage]
B --> C[Open candidate]
C --> D[Advance or reject]
D --> E{Hired?}
E -->|Yes| F[Employee + onboarding]
E -->|No| G[Stay in ATS / archive]
- 1OpenPeople → Candidates.
- 2FilterRequisition and stage.
- 3AdvanceInterviews and offers next.
- 4HireEmployee is the workforce record.
Overview
Candidates are ATS people. Employee is the workforce source. Do not assign projects to a candidate id.
How to use
1. PII care
CVs may contain sensitive data — masking and retention.
2. One person per req application
Merge duplicates rather than double-hiring.
3. Reject with reason
Keep the ATS honest for analytics.