Guide
Custom fields
Capture extra data on vacancies and candidates.
Custom fields let you store information HRHandle doesn't ship with out of the box — things like tech stack, security clearance, preferred languages, or any structured data unique to your hiring process.
You can attach custom fields to vacancies and candidates, grouped into named sections.
Configure the schema
Custom fields are configured per organization in Settings → Custom Fields. Owners and admins can edit; members can only see them on records.
Each entity type (vacancy or candidate) can have up to 20 fields total, organised into any number of groups. Groups appear as named sections on the entity's detail page.
Field types
| Type | What candidates / recruiters see | When to use |
|---|---|---|
| Text | Single-line input | Short answers — "Tech stack", "Preferred location" |
| Long text | Multi-line textarea | Notes, bios, structured comments |
| Number | Number input | Counts, years, scores |
| Date | Date picker | Availability, target start, expiry dates |
| Dropdown | Select from a fixed list | Categorical data — "Seniority level: Junior / Mid / Senior" |
| Checkbox | Yes/No toggle | Boolean facts — "Remote allowed", "Background check completed" |
Mark any field as Required to enforce it on create/edit forms.
Fill the fields when creating
Custom fields show up in the create flows, not just when editing later:
- New candidate — on the Application step (step 4), above the recruitment details.
- New vacancy — on the Dates & compensation step (step 2), below the salary range.
See the fields on a vacancy
Once configured, the fields appear on the vacancy detail page's Job description tab, in the right-hand rail under Additional Information (alongside Posting details), grouped exactly as set up in Settings.
The same pattern works for candidates — their detail page shows each custom-field group as its own card in the right rail, after the Details block, with long (paragraph) values wrapping instead of clipping.
Custom fields are always grouped by section. On the edit pages each group is a bordered card with a field-count badge and a header showing usage against the per-entity cap; on the create wizards the groups are plain sections; and on the detail pages each group is its own sidebar card (short values as label/value rows, long values stacked).
Edit values
Custom field values are edited inline from the entity's detail page or as part of the create/edit form. Anyone with access to the entity can edit values — only schema changes (adding or removing fields) are restricted to admins.
Practical examples
- For vacancies: required tech stack, seniority level, salary band code, remote policy, hiring manager Slack handle.
- For candidates: security clearance, work authorisation, preferred languages, referral source, notice period, expected start date.
Why use them
Custom fields keep structured data on the record itself — no spreadsheets, no notes-buried-in-comments. You can filter and sort by them, and they export to CSV alongside the standard fields, which makes reporting and compliance traceable.