Custom fields
Field types, validation rules, and the org-level field library.
Custom fields are defined at the org level and reused across positions. Each field has a type, a name, an optional description, and optional validation rules.
Field types
| Type | Input | Stored as |
|---|---|---|
| Short text | Single-line text input | String |
| Long text | Multi-line textarea | String |
| Email input with format validation | String | |
| Phone | Phone with country picker and national formatting | E.164 string |
| URL | URL input with optional regex validation | String |
| Location | City autocomplete via OpenStreetMap | JSON (city, country, code) |
| Date | Date picker | ISO date string |
| Number | Numeric input | Number |
| Select | Dropdown with predefined options | String |
| Boolean | Yes/no toggle | Boolean |
| File | File upload (PDF, DOC, images up to 10 MB) | Storage reference |
| Resume | Resume upload (PDF, DOC, DOCX) | Storage reference |
Field scopes
Fields belong to one of two object types:
- Candidate fields - shared across all of a candidate's applications. Phone, location, and LinkedIn are candidate-scoped. Updating a candidate field on one application updates it everywhere.
- Application fields - specific to a single application. Resume, cover letter, and salary expectation are application-scoped. Each application preserves its own values.
Validation rules
- Required - toggled per form, not per field definition. The same field can be required on one position's form and optional on another.
- Regex patterns - URL fields support regex validation. Curated presets exist for LinkedIn profile URLs and GitHub profile URLs. You can write a custom regex through the data model settings.
- Phone validation - phone fields validate country code, length, and number structure automatically.
Managing fields
Go to Settings → Data model to manage your org's field library. The split-pane layout shows:
- A list of all fields on the left, grouped by object type (candidates, applications)
- A detail panel on the right when you select a field, showing name, type, options, validation rules, and description
- A drag handle to reorder fields within the default template
Changing a field's type affects all positions that use it. Existing values may not display correctly if the type changes (e.g. changing a text field to a number field). Consider creating a new field instead.