Hire for Craft CMS
Applications and the pipeline
Applications are elements too, so the inbox is Craft's own element index — sources, sorting, keyword search across everything the candidate wrote, bulk actions and Craft's exporter, none of it reimplemented.
Sources
All applications, Unread, one source per stage, Archived and Marked as spam. The Hire sidebar item carries a badge with the number of unread applications.
Stages
A stage is a column in the pipeline, and each one declares what it means:
| Type | Means |
|---|---|
| Open | Still in the running |
| Hired | Got the job — moves the job's filled count |
| Not proceeding | Out |
That declaration is what lets a job's filled count move by itself when somebody is hired, and what makes "open applications" a meaningful filter. Stages live in project config, under Hire → Settings → Pipeline stages.
Lite has the four the installer creates — New, Shortlisted, Hired and Not proceeding. Pro lets you design your own: Phone screen, Take-home, Final interview, Offer.
On a lapsed Pro licence nothing moves. Every application stays on the stage it is on; what Lite stops is creating another.
Moving candidates
From the application screen, or in bulk from the index with Move to stage. Both go through the same code path, so a bulk rejection still sends the rejection email and still writes the history.
History
Every stage change, email and first open is written to an append-only log on the application:
who moved whom, when, and from where. A stageId column can say where somebody is; it can't say
how they got there.
Ratings and notes (Pro)
Star ratings and reviewer notes, for the conversation between the people reading the applications.
Your team's own fields
Under Settings → Application fields there is a Craft field layout for what your team records about a candidate — interview date, salary expectation, a referral. The applicant never sees it.
Applications outlive their job
Deleting an advert does not delete the people who applied for it. The application keeps a copy of the job's title, so "who applied for the 2026 warehouse job" can still be answered after the advert is tidied away.
Duplicates (Pro)
When the same email applies to the same job again, Hire can flag it (the default — the commonest reason for a second application is a better CV), block it with a message, or allow it without comment. Set under Settings → Uploads & privacy.
The applicant status page (Pro)
An optional page showing the candidate their own stage and nothing else, reached through an
unguessable link (/hire/status?hireToken=…). Switch it on under Settings → Uploads & privacy,
then put {{ statusUrl }} in the applicant confirmation or a stage email — see Emails.
Copy _portal/status.twig to change how the page looks.