Creating candidate custom fields
Last updated: August 4, 2026
Kula's default candidate fields won't always cover everything your team needs to track — things like a certification, a source-specific ID, or an internal classification. Custom fields let you add your own structured data points to every candidate record. This article covers how to create a candidate custom field, what field types are available, and what to watch for.
Who can do this: Users with the Manage fields permission — typically Admins and Super Admins.
Where to find it: Settings → Custom Fields → Candidate Fields (a separate tab from Job Fields and Offer Fields, which have their own custom field sets).
Creating a candidate custom field
Go to Settings → Custom Fields → Candidate Fields.
Choose Add field (or equivalent) and give it a name.
Select a field type (see below).
Save. The field now appears wherever candidate details are captured — the manual "New Candidate" form, the candidate profile, and CSV import mapping.
Field types available
Field Type | Description |
Text | A single line of free text, such as a referral name or portfolio link. |
Number | Numeric values only, such as years of experience or expected salary. |
Date | A calendar date, such as availability or notice end date. |
Dropdown | A single selection from a predefined list of options. |
Multi-select | One or more selections from a predefined list of options. |
Checkbox | A simple yes/no or true/false toggle. |
Note: A field's type cannot be changed after it's created. If you need a different type, create a new field and delete the old one.
Where custom fields show up
Once created, a candidate custom field appears on the manual candidate-creation form, the candidate's profile (editable inline), and as a mappable column during CSV import — you don't need to configure it separately in each place.
Good to know
The "File" field type isn't available to create today. If you need to attach documents to a candidate, use the existing file/resume attachment functionality rather than trying to create a custom field for it.
Yes/No fields have fixed options. You can't relabel "Yes" and "No" — for anything needing custom option text, create a Single choice field instead.
Mandatory/optional customization for candidate custom fields is coming but not live yet. Right now, whether a custom field is required is fixed at creation rather than being independently toggleable — check your account's current settings if this matters to your workflow.
Short text and text area fields both have length limits. If a save fails without an obvious reason, check whether you've hit the character limit before assuming something else is wrong.
Number fields preserve exactly what you type, including comma formatting — useful for compensation-style figures where formatting matters, but be precise on entry since Kula won't reformat it for you.
FAQ
Who can create a candidate custom field? Anyone with the Manage fields permission, which is typically limited to Admins and Super Admins.
Where do I go to create one? Settings → Custom Fields → Candidate Fields. This is separate from Job Fields and Offer Fields, which have their own custom field lists.
Can I create a custom field to store a document or file? Not currently — file-type custom fields can't be created from the UI today. Use the existing resume/file attachment option on the candidate profile instead.
I created a Yes/No field and both options show as "No" — is that a bug? No — Yes/No fields intentionally have fixed, non-renameable options. If you need custom option labels (for example, capturing consent language), create a Single choice field instead and write your own option text.
Can I make a candidate custom field required? Not independently yet — admin-configurable mandatory/optional custom fields are in development but not confirmed live. Today, whether a field is required is fixed when it's created.
Is there a character limit on custom field descriptions? Likely, yes — a similar field type hit a limit of around 500 characters in a real support case, though this hasn't been independently confirmed as identical for candidate custom fields specifically. If you're writing longer description text (like consent language) and it won't save, length is worth checking first.
Need help?
If you have questions or need assistance, reach out to us at support@kula.ai or use the in-app chat.