Application fields
Fields specific to a single application.
Application fields are scoped to an individual application. Each application preserves its own values, independent of the candidate's other applications.
Common application fields
- Resume - the document the candidate uploads when applying. Each application keeps its own resume.
- Cover letter - free-text field for a position-specific cover letter
- Salary expectation - the candidate's salary range for this specific role
- Earliest start date - when the candidate can start this role
- How did you hear about us? - attribution for this specific application
- Visa sponsorship - whether the candidate needs sponsorship for this role
Behavior
A candidate applying to both "Senior Engineer" and "Product Designer" can submit different resumes, salary expectations, and cover letters for each. The values don't interfere with each other.
When to use application vs candidate fields
| Use application fields when | Use candidate fields when |
|---|---|
| The value differs between positions (resume, cover letter, salary) | The value is the same regardless of position (phone, location, LinkedIn) |
| You want to preserve what was submitted at application time | You want the latest value to be reflected everywhere |
| The field is only relevant in the context of a specific role | The field describes the person, not their application |
Managing application fields
Go to Settings → Data model and select the Applications object type to manage application-scoped fields and the default form template.