> ## Documentation Index
> Fetch the complete documentation index at: https://support.yena.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Custom fields
> Extend candidate, job, and company records with the fields your desk actually tracks.
Every desk tracks something the standard schema doesn't: notice periods, salary bands, security clearances, source agreements, regional licensing.
## Where
**Tenant Admin → Custom Fields**. Fields are defined per record type — candidates, jobs, companies — and appear on the records alongside the built-in details.
## What to add (and what not to)
The useful test: will someone filter or report by it? Notice period ("kündigungsfrist") earns its place because "available within 3 months" is a real search. A free-text "misc" field doesn't — that's what [Notes](/en/pipeline/notes-references-files) are for.
Common DACH agency fields: notice period, target salary vs current, willingness to relocate, driving licence class, language levels beyond German/English, works-council experience.
## Custom fields and data quality
Fields you add become part of the completeness picture in **Tenant Admin → Data Quality** — add only what your team will actually fill, or the dashboard turns permanently red.
Define custom fields before a [CSV migration](/en/guides/migrating-from-spreadsheets), so the columns in your spreadsheet have somewhere to land.