Help centre
Setup guide · step 18 of 52 · stage 4, Shape your pipeline

Custom fields and the record page layout

Add your own fields, choose their type, show or require them only when they matter, and arrange them into sections on the record page.

Your own fields live in Settings › Data fields. They appear in forms, on record pages, as list columns, in filters, in reports and in the API. Custom fields are on every plan.

You can add fields to opportunities, contacts and organisations. Leads don't have custom fields.

Owners, admins and team managers can add and change fields. Everyone else sees the fields that are open to them but can't change the set.

Add a field

  1. Go to Settings › Data fields and pick the tab for the record type.
  2. Type a label, choose a type, and add options if the type needs them.
  3. Tick In list to have it in the default columns on that list, and Required if a record can't be saved without it.
  4. Set Who can see and Who can change — Everyone, or Managers only.
  5. Add field.

Two things can't be changed afterwards: the type, and the key that the API and CSV imports use. Renaming the label is fine and doesn't change the key. Deleting a field hides its stored values rather than erasing them, so adding the field back brings them into view again.

The field types

Type Good for
Text a short line, up to 10,000 characters
Large text several lines
Numerical any number
Monetary an amount, shown with the record's currency
Date a single date
Single option one choice from a list you set
Multiple options any number of choices from your list
Yes / No a tick box
Phone a number, dialable on a phone
Email an address, shown as a mail link
Link a web address, opening in a new tab
User someone in your workspace
Rating (1 to 5 stars) a quick score
Address a street address
Calculated (formula) a number worked out from your other number fields

Rating

Five stars, 1 to 5. Click a star to set it, and click the star that's already selected to clear it. A rating counts as a number, so you can filter on it, measure it in a report and group a report by it.

Address

Four boxes — Street address, Suburb, State and Postcode — any of which can be left blank. On the record it reads as a street line and then suburb, state and postcode.

Worth knowing: an address field is plain text as far as filters are concerned, so you can match part of a postcode but not "postcode is between". There's no address lookup, and it isn't the address that Territories checks — territories use the organisation's own address field.

Calculated (formula)

A calculated field works out a number from your other number fields on the same record type. Write the formula with + - * /, round brackets and field keys in curly braces, for example {seats} * {price_per_seat} * 12. The settings page lists the keys you can use.

  • It can read Numerical, Monetary and Rating fields. It can't read a calculated field, so formulas can never loop.
  • There are no functions — no SUM, IF, ROUND or percentages. Arithmetic and brackets only, up to 300 characters.
  • Empty fields count as 0, and the result is blank when every field it reads is empty, or when the sum doesn't work out to a number (dividing by zero, for instance).
  • Nobody types into it. It recalculates whenever a record is saved, and when you create or edit the formula, every existing record of that type is recalculated.
  • You can't delete a field another field's formula reads. Change the formula first.
  • The result is shown as a plain number, even when the fields it reads are money.

Show or require a field only when it matters

Rather than showing everyone every field, a field can appear only when another field says it should. On the field's row, use the Rules button.

  • Show this field — always, or only when another field matches.
  • Require this field — no extra rule, or only when another field matches.

The comparisons are is, is not, is any of, is filled in and is empty. For a multiple-options field, "is" means "includes".

A rule looks at one other custom field of the same record type. You can't key a rule off the stage, owner, value or tags, and you can't combine two conditions on one field. You can chain them, though: if A shows only when B has a value and B shows only when C does, then hiding C hides both.

Two behaviours to plan around:

  • A hidden field's value is cleared when the record is saved. It isn't just hidden from view. Flipping the controlling field back and forth loses what was typed. (Manager-only fields are the exception and keep their value.)
  • "is not" is true when the field is empty, so a rule like "show when Source is not Referral" shows the field on a brand-new blank record.

A field hidden by a rule is never required, even if Required is ticked. With Required ticked, it's required whenever it is shown.

This is a different thing from required fields per stage, which lives in Settings › Pipelines and stops an opportunity moving on until the details are there. See Playbooks, margins and field permissions.

Arrange the record page

Once a record type has more than one custom field, a row appears under the field table: Arrange on record page. It groups your fields into named sections on the opportunity, contact or organisation page.

  1. Add section and give it a name.
  2. Move fields between sections with each field's section dropdown, and order them with the arrows.
  3. Tick Start collapsed for a section that should open on click rather than be open from the start.
  4. Save layout.
  • The layout is the same for everyone in the workspace. Owners, admins and team managers can change it; other members can view it. (Your choice of list columns is the opposite — that's personal to you. See Filters, quick views and bulk actions.)
  • Up to 12 sections. With no layout saved, every field sits in one Details card.
  • A field the layout doesn't mention — including every field you add later — lands in a final Other details section rather than where you added it. Move it after you create it.
  • A section whose fields are all hidden, by a rule or by permission, doesn't appear at all.
  • Reset to default puts everything back into one Details card.

The layout changes the record page only. The create and edit forms still show fields in the order they were added.

Who sees which field

Who can see and Who can change are set per field, as Everyone or Managers only, where managers means owners, admins and team managers. Setting "who can see" to Managers only sets "who can change" to match.

A manager-only field is left out entirely for everyone else — they don't see it on the record and its value isn't in what their screen loads. A field anyone can see but only managers can change is read-only on the record page for everyone else.

Using your fields elsewhere

  • Lists — any custom field can be a column, and In list decides whether it's there by default.
  • Filters — every field is filterable, and a filter can be saved and shared.
  • Reports — Numerical, Monetary, Rating and Calculated fields can be totalled or averaged as a measure; Single option, Multiple options, Text, User, Yes/No and Rating fields can group a report. See Reports, goals and insights.
  • Automations — fields can be tested in conditions and set by an Update a field step. Calculated fields can't be set, since nothing writes to them. See Automations.
  • Import and export — CSV columns use cf. and the field's key, for example cf.contract_value. An address exports as one line. See Importing your data.
  • API — GET /api/v1/custom-fields lists your definitions, record values are keyed by field key, and you can filter with cf_ and the key. See API, webhooks and Zapier.
Still stuck? In ZyfrHub, click ? in the top bar, then Contact support, or email support@zyfrhub.com.
New to ZyfrHub?
14 days of the full Pro plan, no card needed.