Browse documentation

Custom fields

Add your own fields to deals, contacts, and companies: the field types, sections and drag ordering, conditional visibility, the 50-per-entity cap, and how financial fields are hidden from people without finance access.

Updated 2026-07-21

Custom fields are managed in Settings → Custom fields, in separate tabs per entity: deals, contacts, organizations, and clients. Each entity has its own independent set of fields — a field you add to deals doesn’t appear on contacts.

Field types

  • Text
  • Multi-line text
  • Number
  • Currency
  • Date
  • Select — a fixed list of options you define
  • Multiselect — pick any number of options
  • Checkbox
  • URL
  • User — a workspace member

A field’s type is locked in once it’s created — to change it, delete the field and add a new one.

Sections and ordering

Fields can be grouped into named sections — a "Commission" section, for instance — to keep a long list organized. Every entity starts with an ungrouped General section that always renders first and can’t be renamed, deleted, or reordered. Drag handles let you reorder sections, and reorder fields within a section, directly in the Settings list.

Conditional visibility

A field can be set to only show while another field on the same entity holds a specific value. Pick a parent — any Select field that isn’t itself conditional — and one or more of its options; the dependent field is hidden everywhere on the record until the parent’s current value matches. On deals, a field can additionally (or instead) be scoped to specific pipeline stages, so it only shows while the deal sits in one of those stages. Both parts can combine — a field can require both a parent option and a stage — and either part alone works too.

Hiding a field never deletes its value. If the parent moves away from the matching option (or the deal leaves the matching stage), the stored value is kept and reappears the moment the condition matches again.

Creating a field

At the bottom of each entity’s tab is a small inline form, not a popup dialog: a name (up to 40 characters) and a type. Choosing Select reveals an options editor — add, reorder, and remove options, up to 24 of them. There’s no way to mark a field required; every custom field is optional.

Each entity — deals, contacts, organizations, and clients — can have up to 50 custom fields. The counter in Settings tracks you against that limit per entity, not combined across entities.

During import

Deal imports can create custom fields on the fly for columns that don’t map to a built-in field. NeoKivo infers text, number, or date from the column’s values — it won’t create a select field for you; add those in Settings first if you need one. See the import guide in Getting started for the full flow.

Financial fields

Deal custom fields can be flagged as financial, which hides them — not just disables them — from anyone without finance access, the same permission that masks commissions and other money fields elsewhere in NeoKivo.

On the Deals tab of Custom fields, both the add-field form and each existing field carry a “Financial field — hidden from people without finance access” checkbox. Tick it when creating a field, or toggle it on a field you already have; the masking follows the flag immediately. The toggle is offered on deal fields only, since that’s where financial masking applies.

A section itself can also be marked financial. Do that and every field inside it is treated as financial — masked from anyone without finance access — regardless of that individual field’s own checkbox. When a section is financial, its fields show a disabled “Financial — from section” badge in place of the checkbox, since there’s nothing left to toggle per field.

Spotted something out of date? Email hello@neokivo.com.