Custom fields
Nine field types you define yourself, with per-role visibility.
Defining a field
In Settings → Custom fields, admins and above can add fields to contacts and offerings. Each field has a label, a short machine key, an optional description, a type, and optionally a required flag and a minimum role.
Field types
| Type | Behaviour |
|---|---|
| Text | Free text. |
| Number | Numeric, with optional minimum and maximum. |
| Boolean | A yes/no checkbox. |
| Date | A date, filterable by range. |
| Single select | One value from a list you define and order. |
| Multi select | Several values from that list; filterable by any or all. |
| Link | A URL. Restricted to http and https addresses. |
| Phone number | Validated and searchable by digits. |
| Validated as an address. |
Who can see a field
Set a minimum role and anyone below it will not see the field at all — not in forms, not in lists, not in the filter builder, and not in the activity timeline. The server also refuses to accept a value for it from someone below that level, so the restriction is real rather than cosmetic.
A related safeguard: a comment that appears to contain a restricted field's value or label is rejected, so sensitive figures cannot be laundered into a comment everyone can read.
Quick view
Mark a field as visible in quick view to surface it in compact record summaries.
Using fields elsewhere
- Search — the global search box matches custom field values.
- Filters — every field appears in the advanced filter builder with operators suited to its type.
- Sorting — list columns can sort by custom field.
- Forms — contact custom fields can be placed on public capture forms.
- History — changes are recorded like any other field.
Deleting a field
Deleting a definition also removes that field's stored values from every record in your account, so no orphaned data is left behind. This cannot be undone.
Something inaccurate or missing? Tell us — we would rather fix the docs than have you guess.