Custom fields

Custom fields store extra data on contacts or companies that the built-in fields don't cover: a shirt size, a membership number, a giving-level note. You define each field once for your whole workspace on the Custom fields settings page, at Settings > Data model > Custom fields. Only account owners and admins can open this page.

Adding a field

Click Add field to open the Add a custom field dialog. It asks for the following:

• Display name: the label that appears on records and, if you flag it, as a column header. Required.
• Field key: the stable internal identifier you type yourself (for example shirt_size). It must start with a lowercase letter and contain only lowercase letters, digits, and underscores, matching [a-z][a-z0-9_]*. The key cannot be changed after the field is created.
• Applies to: Contacts or Companies. A field belongs to one entity and is fixed once created. See the note below on where company fields are filled in.
• Field type: one of Text, Number, Date, Single-select, Multi-select, Checkbox, URL, or Email. Like the key, the type is fixed once created.
• Options (one per line): appears only for Single-select and Multi-select. Enter each allowed value on its own line. Blank lines are ignored, and a select field saved with no options is rejected.

Three checkboxes control how the field behaves:

• Required: marks the field as required on the entity.
• Show in list table: adds the field as a column in the contacts list and includes it in the contacts CSV export.
• Sensitive (PII): encrypts the field's values at rest and gates plaintext access behind a reveal. See Sensitive fields for the full reveal-and-audit flow.

Click Add field to save. The field key must be unique for that entity within your workspace: reusing a key on the same entity is rejected. Once saved, a contact field appears inside the Details tab of every contact.

How sensitive fields change the other flags

A sensitive field is stored encrypted, so it can never be shown as a plaintext column or used as a filter. If you check Sensitive (PII), Show in list table is forced off regardless of whether you also checked it, both on creation and when editing. A sensitive field never appears as a column or in the CSV export.

Editing a field

Click the pencil icon on a row to open the Edit custom field dialog. You can change the Display name, the select options, and the three flags. The Field key, entity, and Field type cannot change. The dialog states this directly: "Field key … and type … can't change: delete and recreate if you need that."

The field key is the identifier under which every value is stored. Changing it would orphan the data already on your records, which is why it is locked after creation. Pick a key you can live with: the display name is the part you can rename later.

Removing a field

Click the trash icon on a row to remove a field. A confirmation prompt appears: "Remove "<name>"? Existing values stay on contacts but the field won't appear in editors." Removing a field is a soft delete: it disappears from the Custom fields settings page, from record editors, and from any list column, but the values already stored on records are kept and are not deleted.

Because the key is immutable and removal is non-destructive, the way to change a field's key or type is to remove the old field and add a new one with the key, type, and options you want.

Filling in field values

Values are entered per contact. Open a contact, and its custom fields appear in a Custom fields group inside the Details tab, listed with an inline editor matched to each field's type. Non-sensitive fields edit in place; a sensitive field shows a lock and a Reveal control instead of its plaintext value. When your workspace has no custom fields defined, the group does not appear at all.

What each flag does

Flag	Effect	Sensitive override
Required	Marks the field as required on the entity	Unaffected
Show in list table	Adds a column in the contacts list and CSV export	Forced off
Sensitive (PII)	Encrypts values and gates them behind reveal	—