When is a computed field worked out?

Every time the record is saved, and for every record when you change the formula. The value is stored, so filters, boards, views and segments use it like any field. Nobody can type over it.

What can a formula use?

The record's own fields by their key, built-in values such as @created (and @amount and @close_date on a deal, @priority and @status on a ticket), + - * /, & to join text, comparisons, and IF, AND, OR, NOT, ISBLANK, CONCAT, ROUND, ABS, MIN, MAX, DAYS, ADD_DAYS and LEN. Formulas that use each other in a circle are refused when you save.

Is a hidden field really hidden, or only on the screen?

Really hidden. The server leaves it out of every answer for a role that may not view it: the record, lists, exports, the API, the AI assistants and the Brand My Inbox bridge. It also refuses filters, boards and segments on it. A computed field is shown only to people who may view every field it reads.

Can an integration change who sees a field?

No. Integrations and AI assistants can add and change fields, but permissions are set by a person here in Settings.

Can a board be grouped by a multiple-choice field?

Yes. A card appears in the column of every value it holds. Dragging between those columns is off, because a drag cannot say which value to replace; change the values on the record.

Fields and structure: your own fields, computed fields and who sees each one

One screen for every field in the CRM: contacts, companies, deals, service tickets and modules. Add fields of any type, including multiple choice and computed fields, drag them into order, decide who may view and who may edit each one, and archive a field without losing a single value.

Steps

Settings → Fields and structure (owners and admins). Pick a tab: Contacts, Companies, Deals, Service tickets or Modules.
Add a field and choose its type: text, number, date, a list (one choice), multiple choice, yes or no, a link, a computed field, or an Israeli ID, company number or phone. Tick Required, or Sensitive to mask it for analysts.
For a computed field write a formula, for example ROUND(budget * 1.18, 2) or IF(@amount >= 10000, 'large', 'small'), and choose whether it makes a number, text or a date. The editor checks it as you type and shows the result on an example.
Under Permissions choose who may view the field and who may edit it, role by role, including Integrations (the API and AI assistants). The owner always may.
Drag fields into the order the record shows them, and look at the preview of how the field appears on the card.
To remove a field, read how many records use it, then Archive. Archived fields wait under Archived with their values, and Restore brings both back. Renaming a field keeps every value.

Questions

When is a computed field worked out?: Every time the record is saved, and for every record when you change the formula. The value is stored, so filters, boards, views and segments use it like any field. Nobody can type over it.
What can a formula use?: The record's own fields by their key, built-in values such as @created (and @amount and @close_date on a deal, @priority and @status on a ticket), + - * /, & to join text, comparisons, and IF, AND, OR, NOT, ISBLANK, CONCAT, ROUND, ABS, MIN, MAX, DAYS, ADD_DAYS and LEN. Formulas that use each other in a circle are refused when you save.
Is a hidden field really hidden, or only on the screen?: Really hidden. The server leaves it out of every answer for a role that may not view it: the record, lists, exports, the API, the AI assistants and the Brand My Inbox bridge. It also refuses filters, boards and segments on it. A computed field is shown only to people who may view every field it reads.
Can an integration change who sees a field?: No. Integrations and AI assistants can add and change fields, but permissions are set by a person here in Settings.
Can a board be grouped by a multiple-choice field?: Yes. A card appears in the column of every value it holds. Dragging between those columns is off, because a drag cannot say which value to replace; change the values on the record.

Updated 2026-10-25 · llms-full.txt