# Custom fields

The facts your team keeps on each lead, typed, with a merge field for messages, shown on the screens and forms you choose.

Custom fields hold what your team checks before a call: capital, monthly income, the webinar a lead came from, the setter and the closer, a recording link.

## Who can open it

Owners and admins. Anyone on the team fills in a lead's fields on the lead's page.

## Types

Text, number, money, date, dropdown, multi-select, team member and link. A money field keeps its amount in one currency, the workspace's unless you set another. A dropdown or multi-select has its options, one per line. A team member field picks someone on the team.

Each field has a key, made from its label, which is also its merge field: a field called Monthly income is `{monthly_income}` in a text or an email. The key and the type never change once the field is made, because messages, forms and filters use them. Keys that are already merge fields for every contact, such as `{first_name}`, are taken.

## Where a field shows

- **Lead page**: in the Custom fields panel, where anyone can fill it in.
- **Board cards**: under the lead's name on the [Pipeline](/docs/features/pipeline) board (the first three such fields).
- **List view**: as a column in the Pipeline list.
- **Forms**: pick the field on a question in the [form builder](/docs/features/forms), or list the keys of PYLO's forms here, and an answer whose question key or wording matches the field fills it in when the form is sent. An answer that does not fit the field's type stays on the response and is marked in the form's Results.

A **required** field cannot be cleared on the lead's page.

## Using fields

- **Filters**: filter the board on any field, for example capital more than 5000 or webinar date before a day.
- **Workflows**: an if/else or a wait can test a field with a field condition, using its key.
- **Messages**: put `{key}` in a text or email.
- **Close and GoHighLevel**: map their custom fields onto yours under [Pipelines](/docs/settings/pipelines).

## Changing and archiving

Edit a field to change its label, options, whether it is required and where it shows. An option some leads already have cannot be removed, so rename it instead. Archive a field to hide it everywhere with its values kept; bring it back from the Archived list. A field used as a pipeline's card value cannot be archived until the pipeline uses another.