Overview
How the field system works across candidates, applications, and forms.
Custom fields are the building blocks of your data model. They define what information you collect from candidates, what appears in candidate profiles, and what you can filter by in the pipeline and talent pool.
How fields work
Fields are defined once at the org level and reused everywhere:
- Added to application forms to collect data from candidates
- Displayed on candidate profiles and in table columns
- Available as filters in the pipeline and talent pool
- Usable in workflow conditions and actions
Identity fields vs custom fields
Three identity fields are built into every candidate record: first name, last name, and email. These cannot be modified or removed. Everything else (phone, location, LinkedIn, resume, and any fields you create) is a custom field.
Default fields
When you create your org, Bringboard seeds a set of default fields:
Tier 1 - included in the default form template
- Phone (candidate-scoped)
- Location (candidate-scoped)
- LinkedIn URL (candidate-scoped)
- Resume (application-scoped)
Tier 2 - available in the field library
- GitHub URL
- Website URL
- How did you hear about us?
- Visa sponsorship required?
- Earliest start date
- Salary expectation
You can remove these from forms or add new fields at any time.
Previous
Data model
Next
Candidate fields