[Integrations](https://www.cv-transformer.com/yue/docs/integrations) [Field mapping](https://www.cv-transformer.com/yue/docs/integrations/field-mapping)

# Field mapping

閱讀需時 1 分鐘

A candidate linked to your ATS brings its ATS data along, such as their address, salary expectations or availability. The AI uses this data to fill in the layout, and layouts can show it directly as `{{external.…}}`. Field mapping describes this data, so CV-Transformer knows each field's name and type.

## [Viewing a candidate's ATS data](#viewing-a-candidate-s-ats-data)

In the candidate editor, the sidebar shows the candidate's data from your ATS under **… data**, such as **Bullhorn data**.

## [Editing the schema](#editing-the-schema)

Click **Edit schema** in that panel to describe the fields:

- **Infer schema from data** creates fields from the data of the open candidate, as a starting point.
- For each field, set its key, as the ATS names it, and its type, such as inline text, number, date, date range, enum, rating, image, list or object.
- Mark fields as **Sensitive** to hide them in anonymized proposals, or **Public**.

Click **Save** to store the schema. Two fields can't have the same key.

The schema applies to every candidate of the organization. With a schema, the ATS data shows as readable fields instead of raw data, and layouts can use it as `{{external.<key>}}`, such as `{{external.availability}}`.

## [Updating ATS data](#updating-ats-data)

**Update** in the same panel writes data back to the ATS: it fills the candidate's fields in the ATS from their attachments and the values filled in CV-Transformer. This overrides the data stored in the ATS for this candidate.

[之前Tigris](https://www.cv-transformer.com/yue/docs/integrations/tigris) [下一個Developers](https://www.cv-transformer.com/yue/docs/developers)