# Field mapping

Edit field mapping in **Tomba Setup › Field mapping**: pick the object, change the target field, policy or
active flag of any mapping, or **Add mapping** to send another Tomba value to a field of your choice, then
**Save and deploy**. Changes are deployed as custom metadata in the background (a few seconds) and apply to the
next lookup. You need the Customize Application permission.

Behind the scenes this is the **Tomba Field Mapping** custom metadata type. Each record says: for this object,
write this Tomba value to this field, with this policy.

| Policy      | Meaning                                                    |
| ----------- | ---------------------------------------------------------- |
| `FillEmpty` | Only write when the field is blank (default for standard fields) |
| `Overwrite` | Always write (default for Tomba fields)                    |
| `Never`     | Don't write                                                |

You can change **Target field**, **Policy** and **Active** on the records that come with the package, and add
your own records, for example to send `seniority` to a custom field.

## Tomba values

| Value                                                                 | Comes from                                    |
| --------------------------------------------------------------------- | --------------------------------------------- |
| `email`, `email_status`, `email_score`                                | Email finder, enrichment, verifier            |
| `first_name`, `last_name`, `position`, `department`, `seniority`      | Email finder, enrichment, domain search       |
| `linkedin`, `twitter`, `country_code`, `phone`                        | Email finder, enrichment, phone finder        |
| `company_name`, `company_domain`, `company_industry`, `company_employees` | Enrichment, company enrichment          |
| `company_description`, `company_revenue`, `company_founded`, `company_linkedin`, `company_city`, `company_country_code` | Company enrichment |
| `phone_status`, `phone_line_type`, `phone_carrier`, `phone_intl`      | Phone validator                               |
| `company_technologies`                                                | Technologies                                  |

Values are converted to the field type. Values that don't fit (a range like `51-200` in a number field) are
skipped, and fields the user cannot edit are never written.