Skip to main content

Custom Fields

Define custom fields to capture additional candidate information.

Overview​

Custom Fields let you add extra data points to candidate profiles beyond the standard fields. Define fields once and they appear on all candidate profiles for your company.

Access​

Go to Manage > Custom Fields.

Required role: Super Admin or Admin.

Field Types​

TypeDescription
TextPlain text input
NumberNumeric input
Boolean (Yes/No)Yes/No toggle
DateDate picker

Creating a Field​

  1. Click Add Custom Field
  2. Fill in the form:
FieldRequiredDescription
Field LabelYesDisplay name (max 255 characters). Example: "Visa Status", "LinkedIn URL"
Field TypeYesOne of the 4 types above
DescriptionConditionalHint text shown below the field. Becomes required when Auto Extract is enabled — describe what the AI should extract. Max 500 characters.
RequiredNoWhether the field is mandatory on candidate profiles
Auto ExtractNoWhen enabled, AI automatically populates this field from parsed resumes
Sort OrderNoDisplay order on profiles (lower numbers appear first)
  1. Click Create Field

Field Key​

A unique field key is automatically generated from the label:

  • "Visa Status" becomes visa_status
  • "LinkedIn URL" becomes linkedin_url

The field key is read-only and cannot be changed after creation.

Auto Extract​

Enable Auto Extract to have AI automatically populate the field from candidate resumes during parsing.

How it works:

  1. When a resume is uploaded or imported, the AI resume parser analyzes the document
  2. For each custom field marked "Auto Extract", the AI attempts to extract relevant information based on the field's description
  3. The extracted value is automatically merged into the candidate's custom fields
  4. Users can still manually edit or correct extracted values

Example use cases:

  • Visa/work authorization status
  • Certifications and licenses
  • Security clearances
  • Languages spoken
  • Willingness to relocate
Auto Extract overwrites manual edits on every resume parse

Every time a candidate's resume is parsed — whether from a new upload or a manual re-queue — the AI re-extracts all Auto Extract fields and overwrites the existing values, including any manual corrections you've made.

Key points to understand:

  • There is no lock or override protection for auto-extracted fields. The latest resume parse always wins.
  • If the AI cannot find a value for a field, it may write null, erasing any value that was there before.
  • Non-auto-extracted (manual-only) fields are never touched by resume parsing.

If a field value needs to be stable and protected from AI overwrites, keep Auto Extract disabled on that field. Manually entered values on those fields are never changed by resume parsing.

tip

Write a clear, specific description when enabling Auto Extract — this is the instruction the AI uses to know what to look for. For example: "Visa or work authorization status, such as US Citizen, H-1B, OPT, or Green Card holder."

info

All custom fields appear as columns in Candidate Search and Find Candidates, allowing you to sort and filter by their values.

Field List​

The list page shows all defined custom fields:

ColumnDescription
LabelField name and description
Field KeyAuto-generated key (monospace)
TypeColor-coded badge
RequiredRequired or Optional indicator
Auto ExtractAI badge when enabled, dash when disabled
OrderSort order number
ActionsEdit and Delete links

Use the search box to filter by label, key, or type.

Editing a Field​

  1. Click Edit on a field row
  2. Update the field properties
  3. Click Update Field
note

You cannot change the field type after creation. If you need a different type, delete the field and create a new one.

Deleting a Field​

  1. Click Delete on a field row
  2. Confirm the deletion
warning

Deleting a field removes the definition and any data stored in this field across all candidates.

Tips​

  • Use clear, descriptive labels so team members understand what to enter
  • Set sort order to control how fields appear on candidate profiles
  • Mark fields as required only when the data is essential for your workflow