The job of this console
Open a role, keep it accurate, attach pipeline, close when filled. Do not use this list as the org chart.
People · ATS
Requisitions
Open roles the ATS is hiring for — demand that staffing and offers hang off, not a capacity assignment.
Scroll to Flowcharts. Scenario: Open a hiring requisition.
Open roles
Demand the pipeline hangs from
Requisitions are the ATS openings. Candidates, interviews, and offers point here. Project staffing requests are a different demand stream.
People → Requisitions
Route
/recruiting/requisitions
Org flag recruitingEnabled
HR Admin · Admin
Seat at the table
HR Admin and Admin. Hiring managers may collaborate on their reqs if the product scopes them.
The working rhythm
Create or filter, edit the opening, watch attached candidates, close on hire or cancel.
Moments that bring you here
New approved headcount. A backfill. Freeze. After an offer is signed.
ⓘ
Not a project and not Employee
Filled work still needs an Employee row before timesheet and leave.
Flowcharts
1 — Open or close a req
Create the role, attach pipeline, close when hired.
flowchart TD
A[Open Requisitions] --> B[Create or edit req]
B --> C[Pipeline candidates]
C --> D[Interviews / offer]
D --> E[Fill or cancel]
E --> F[Employee + onboarding if hired]
- 1OpenPeople → Requisitions.
- 2AuthorRole and hiring manager.
- 3PipelineCandidates hang off the req.
- 4CloseHired becomes Employee.
Overview
Requisitions are ATS demand. Resources staffing requests are project load. Do not treat a req as a Project.
How to use
1. One req per role opening
Not per applicant.
2. Fill path
Offer → Employee → onboarding.
3. Cancel cleanly
Do not leave ghost openings for capacity.