Skip to main content

Recruitment (ATS)

The Recruitment module is a full applicant-tracking system built into your workspace. You raise an internal job opening, publish a public posting to your careers site, collect applications, move candidates through a kanban pipeline, schedule interviews, extend offers, and finally convert a hire into an employee — which starts onboarding automatically.

Recruitment lives under the Recruitment section of the admin menu:

  • Job Openings — /admin/recruitment/jobs
  • Candidates — /admin/recruitment/candidates

Your public careers site is served separately at /careers and needs no login.

Who can use it​

Three permissions control access:

PermissionWhat it allows
recruitment.viewRead-only access to openings, candidates, and applications
recruitment.manageFull control — create openings, publish postings, move stages, schedule interviews, extend offers, convert to employee
recruitment.interviewSubmit interview feedback as a panel member

Interviewers do not need recruitment access to see the interviews they are on — anyone assigned to a panel sees them under My Interviews (/portal/interviews) in the employee portal.


Job openings​

A job opening is your internal requisition — the role you are hiring for, before anything is made public.

Create an opening​

On Job Openings, click New opening and fill in the title (required) plus optional department, designation, employment type, and headcount. New openings start in Draft.

Openings move through these statuses:

StatusMeaning
DraftBeing set up; not yet approved to hire
OpenApproved and actively hiring — the only status that can be published, and the only one the careers site lists
On holdPaused
FilledHeadcount reached (set for you when you convert a hire)
CancelledClosed without hiring

Open an opening to see three tabs: Details, Posting, and Applications.

  • Details lets you edit headcount and internal notes, and change the status from the sidebar. With Skills management on, a Required skills card shows the designation's requirements until you save the opening's own list; the public job page lists whichever applies. Moving an opening to Open stamps the approval. Moving it anywhere else (On hold, Filled, Cancelled) also unpublishes its posting, so the careers site and the Publishing panel agree; move it back to Open and publish again to relist it. The view count is kept.
  • Posting is the public advert (below).
  • Applications is the kanban pipeline (below).
note

An opening must be in Open status before you can publish its posting or add applications to it.


The public careers site​

Your careers site is a fast, search-engine-friendly set of pages rendered by the server — no login, clean URLs.

PageURL
Careers landing (all open roles, grouped by department)/careers/c/{workspace id} on the shared address (use View careers page on Job Openings); /careers on your own domain
A single job with an apply form/careers/{slug}
Thank-you page after applying/careers/thank-you
Sitemap for search engines/sitemap.xml

Writing and publishing a posting​

On an opening's Posting tab, fill in:

  • Slug — the URL-safe address of the page (leave blank to auto-generate from the title; a number is appended if it collides)
  • Location and Remote policy (On-site / Hybrid / Remote)
  • Description (required), What you'll do, What we're looking for, and Benefits
  • Salary min / max / currency and whether the range is per month or per year (shown after the range on the public page and sent to search engines as the unit), plus a Show salary range on the public posting toggle — the range is only ever shown publicly when this is ticked
  • Required skills are not written here: the public page lists the opening's required skills (or its designation's) under a Skills heading, set from the Details tab
  • Show this job in search engines — on by default. Untick it to keep the job on your careers page for anyone with the link but out of Google and other search engines: the page is marked not to be indexed, carries no structured data, and is left out of the sitemap. Use it for test roles and roles you only share privately; the Publishing panel then reads Hidden from search engines

Click Save draft, then Publish to careers page. The opening must be Open to publish. Once live, the panel shows how long it has been published, a link to the public page, and a running view count. Unpublish takes it back off the site at any time.

Search-engine optimisation​

Every published job page shown in search engines is built for discovery:

  • Google for Jobs structured data (schema.org JobPosting JSON-LD) is embedded, including title, description, posting date, hiring organisation, location, employment type, and salary (when visible).
  • Each page carries its own SEO meta description.
  • /sitemap.xml lists careers landing pages and every published opening shown in search engines, each dated by when its page last changed, so crawlers find new and edited roles. On the shared address it is the platform's sitemap, listing your landing and roles among other workspaces'; on your own domain it lists only yours. Either way robots.txt already points search engines at it, so there is nothing to submit. A landing page whose every role is hidden from search engines is left out and marked not to be indexed.
tip

If your workspace has an active custom (white-label) domain, your careers pages, sitemap, and job links are served under your own domain and branding instead of the platform domain.

How candidates apply​

A candidate opens a job page, fills in the apply form (name, email, optional phone, LinkedIn, current employer, cover letter), and attaches a CV. On submit they land on the thank-you page and receive a confirmation email.

Behind the scenes the system matches on email: applying twice with the same address updates the same candidate and application rather than creating duplicates, and never overwrites a decision you have already made.


Candidates​

The Candidates page lists everyone who has applied — one row per person, with their applications across all openings grouped together. Search by name or email. Open a candidate to see their contact details, CV, and application history.

The candidate list

The talent pool and tags​

A good person you could not place is worth keeping. On a candidate's page, Add to pool puts them in the talent pool with a note on why they are worth coming back to; tags ("senior", "remote", "data") are free words you give any candidate, pooled or not. The Candidates page filters by Talent pool and by tag, and an opening's Applications tab lists From the talent pool: pooled candidates who have not applied to that opening, with Add to pipeline putting them at Applied as a manual entry. Being in the pool changes nothing about the person's applications; it is a flag for you.

Candidate skills and the match​

With the skills feature on, a candidate's page has a Skills card where HR records the skills seen on the CV or in the interview, each with a level on its type's scale (a level the scale does not have is refused). Against an opening's required skills (its own list, or its designation's), every application shows a match: the share of requirements the candidate meets, with the met, below-level and missing skills on hover. A skill recorded without a level counts as met. The pool list on an opening is ranked by that match. An opening that asks for nothing shows no match.


Applications and the kanban pipeline​

Each application is one candidate applied to one opening. The Applications tab of an opening shows a board with a column per stage, then Hired, Rejected and Withdrawn:

Applied → Screening → Interview → Offer   |   Hired · Rejected · Withdrawn

Drag a card to another column to move the application; dropping it on Rejected asks for the reason first. Hired, Rejected and Withdrawn are end states, not stages: an application can reach them from any column.

Your own stages​

The four stages are the built-in list. Recruitment › Pipeline settings lets you rename and reorder them and add your own between them ("Phone screen", "Technical test", "Final round"): the list is the columns every opening's board shows, in that order. The built-in four stay, because scheduling an interview moves an application to Interview and an offer needs Offer; a stage that still holds applications cannot be removed until they are moved.

Those two moves only ever go forward along the list as you ordered it. Scheduling another interview for an application already in a stage you placed after Interview (a technical test, say) leaves it there, and revising an offer leaves an application in a stage after Offer where it is. The buttons follow the same order: Schedule interview shows from Interview up to Offer, Extend offer from Interview on, and Convert to employee from Offer on, whatever stages of your own sit between or after them.

An opening can have its own stages: Give this opening its own stages on its board copies the list it uses today, and from then on only that opening's edits apply. Reset to workspace stages drops the copy, as long as no application sits in a stage the workspace list lacks. Nothing is configured until you edit the list, so a workspace that never opens the page runs on the built-in four as it always did.

Refuse reasons​

Pipeline settings also holds the refuse reasons: the reasons an application is turned down, each deciding what the candidate hears. A reason either sends the standard Application Rejected email with your note as feedback, sends its own wording (a subject and an HTML body with the same variables, through the same template switch and layout), or sends no email at all (a duplicate application, say). On Reject you pick a reason, add a note, or both; the application records the reason and the note as "reason: note". A reason that was ever used is retired rather than deleted, so the record keeps pointing at it. With no reasons configured, rejecting works as before: a note, and the standard email.

A reason's own wording is checked when you save it, so a mistake shows on the form and not as an email that failed to reach a candidate:

  • The subject and the body can use the variables listed under the body field, written as {{candidate.firstName}}, and {{#if rejectionReason}} … {{/if}} (or {{#unless}}) around a part that should only appear when a variable has a value. A misspelt or unclosed variable, a variable this email has no value for, and anything else from the template language are refused, with a message that says which.
  • The body is plain rich text: paragraphs, bold and italics, headings, lists, simple tables and links. Scripts, styles, images, embedded content and every attribute except a link's address are removed on save. A link can point at a web address, a mailto: address, or your own workspace with {{appUrl}} ({{appUrl}}/careers, for example).
  • The subject is kept as one line.

Adding a sourced candidate manually​

For candidates you found yourself (LinkedIn, a referral, a headhunter), click Add candidate manually on the Applications tab. Enter their details and a source, and they enter the pipeline at Applied with a confirmation email — just like a public applicant.

Working an application​

Click any card to open the application. The detail page shows a stage stepper and the actions available at the current stage:

  • Move to next stage — advances one step (for example Applied to Screening).
  • Schedule interview — appears at the Interview stage, and at any stage of your own between Interview and Offer (see below).
  • Extend offer — appears from the Interview stage on when no offer exists yet; while an offer is out (sent, or sent and expired) it reads Revise offer, opens with the current terms, and updates the same offer and candidate link.
  • Convert to employee — appears once the candidate is hired, or the application is at Offer or a stage after it.
  • Move to… — any stage of the opening's list, when the order is not the point (a candidate skipped a round, say). Offer stays behind Extend offer.
  • Reject — always available; a refuse reason, a note, or both. What the candidate is emailed depends on the reason.
note

You cannot jump straight to Offer with the plain "move to next stage" button — you must use Extend offer so a real offer (with letter, link, and email) is created. Likewise, moving to Hired while an offer is out is done by the candidate accepting the offer, not by hand.

The application page also shows the cover letter, all interviews with their feedback, the offer, and a candidate sidebar with contact links and a CV download.


Interviews​

Scheduling​

On an application at the Interview stage, click Schedule interview. In the dialog set:

  • Title, date/time, and duration — the date and time are in your workspace's time zone (Company Profile), whatever zone your own computer is in; the dialog names the zone under the field
  • An optional branch — picking one auto-fills the location with the branch address (you can still edit it to add a floor or room)
  • An optional meeting link for remote interviews
  • One or more interviewers — hold Ctrl/Cmd to select several; the first is the primary interviewer

Saving does several things at once:

  1. The application advances to the Interview stage if it had not reached it yet. One already at Interview, or in a later stage, stays where it is.
  2. The candidate gets an email with the interview details, a calendar .ics attachment, and a personal link to confirm.
  3. Each interviewer gets a heads-up email with the same calendar invite.

The interview time is shown in the workspace's time zone everywhere: on the application, in the emails, on the candidate's page, under My Interviews and in the portal dashboard's upcoming interviews. The .ics invite carries the exact moment, so each calendar app shows it in its own owner's zone.

The candidate confirmation page​

The candidate's link opens a no-login page at /careers/interview/{token} where they can Confirm or Request a reschedule (with a short note). Their response — Confirmed, Reschedule requested, or Awaiting — is shown on the application, and interviewers are notified when the candidate acts. The candidate can also re-download the .ics invite from that page.

Reminders​

An automatic reminder is sent about 24 hours before each scheduled interview — one to the candidate, one to each interviewer. Reminders are sent once and won't duplicate on repeated runs.

Interviewer portal and feedback​

Panel members open My Interviews (/portal/interviews) in the employee portal to see the interviews they are on and submit feedback: a 1–5 rating, a recommendation (strong_no, no, yes, strong_yes), optional per-competency scores, and free-text strengths, concerns, and notes. Feedback appears back on the application for the hiring team.

The page lists Upcoming interviews soonest first and Past interviews most recent first. An interview that is no longer scheduled (completed, cancelled or a no-show) is listed under Past, even when its date has not come yet.


Offers​

Extending an offer​

Click Extend offer on the application and enter the proposed monthly salary, joining date, offer expiry date, and internal notes. On send, the system:

  1. Creates the offer and moves the application to the Offer stage (an application already at Offer, or in a stage after it, stays where it is).
  2. Renders an offer-letter PDF.
  3. Emails the candidate with the offer details, the PDF attached, and a link to respond.

The candidate offer page​

The candidate's link opens a no-login page at /careers/offer/{token} where they can Accept or Decline (a reason is required to decline) and download the offer-letter PDF.

  • Accept moves the application to Hired and notifies the hiring manager and the person who issued the offer.
  • Decline moves the application to Withdrawn, records the reason, and notifies the same people.
  • An expired offer (past its expiry date) can no longer be accepted from the link; the Offer card on the application shows it as Expired. Revise it to give the candidate a new window.

Back on the application, the Offer card shows the current status, links to the candidate offer page and the PDF, and — if declined — the candidate's reason.


Convert to employee (handoff to onboarding)​

Once a candidate is Hired (or has an active offer), the application shows a Convert to employee prompt. This opens the employee create form at /admin/employees/create?applicationId=..., pre-filled from the candidate and their offer. Review and complete the remaining details (department, designation, employment type, official email, joining date, and so on), then create the record.

Creating the employee this way:

  • Links the candidate to the new employee so they can't be converted twice.
  • Automatically spawns the onboarding pipeline for the new hire — no extra step. See the onboarding guide for what happens next.
  • Marks the job opening Filled once its headcount is reached.
tip

Because conversion runs through the normal Add Employee flow, everything that a manual new hire gets — a login account, the default onboarding checklist, and the welcome sequence — applies to a converted candidate too.


Automated emails​

Recruitment sends templated emails at each key step. All of them are managed alongside your other templates, so you can edit the wording:

  • Application received — to the candidate when they apply (public or manual entry)
  • Application rejected — to the candidate, with your reason
  • Interview scheduled and Interview reminder — to the candidate, with the .ics invite
  • Interviewer invited, candidate confirmed, reschedule requested and Interview reminder — to the panel, the invitation and the reminder with the same .ics
  • Offer extended — to the candidate, with the offer-letter PDF
  • Offer accepted / declined — to the hiring manager and the offer issuer

If a template isn't configured for a trigger, that particular email is simply skipped — the pipeline action still succeeds.

The .ics is a proper invitation: the primary interviewer is the organiser, the candidate and the rest of the panel are attendees, and its sequence number rises every time the interview is edited. Change the time, the room, the link or the panel and the scheduled and invited emails go out again with the updated file, so every calendar replaces the earlier entry rather than keeping two. The candidate's confirmation page serves the same file.

What goes into the file is written as plain text, whoever typed it: a candidate's name, the title and the location cannot add anything to the invitation beyond their own words. The meeting link is offered as a link only when it is a web address (https://…); anything else typed in that field still shows as text in the event's description. On the careers form, a name with a line break or a control character in it is refused.