Add, edit, reorder and deactivate a field Add a field of the right type, give it a name, a label and an icon, and set its settings. The type can’t change after the field is created.
Before you start · for owners
The permission to edit units (and to create units, to add a field)
You need: The permission to edit units (and to create units, to add a field)Steps 1 Press Units settings (the gear next to Units in the sidebar), open the unit on the Cortex Unit tab, then press Add Field .
3 In Configure Field , enter the Field Name and the Label , and choose the Icon .
The name is an internal ID, and the label is what your team sees.
4 Set the type’s settings (options, limits, format), and the Required field and Default value if you need them.
5 Save.
The field shows in the form and the table straight away.
6 To reorder fields, drag them in the list.
7 To search, type in Search a field... . Shared fields show with the unit’s own fields.
A field’s type can’t change after it’s created. And deleting a field for good deletes its data in every record.
Settings every field has Setting
What it does
Guide
Required field
Stops saving without a value
Conditional requirement
Required only when a condition is met
Require unique values
Stops the same value being used twice
Default value
Fixed, or calculated when the record is created
Conditional visibility
Shows or hides the field based on another field
Group
Its place in the form
API only
Only the API can write it
Deactivating or deleting Deactivate hides the field from forms and pickers, and keeps its data. You can activate it again at any time.
If a Kanban board groups by the field, a warning names the boards. Once the field is deactivated, no one can set its value, so new records pile up in the “no value” column. Confirm only if that’s what you mean.
Deleting a field for good deletes its column and all its values, and deletes the Kanban boards grouped by it. It’s Delete in the field’s menu, for roles allowed to delete, and a required field can’t be deleted until you turn off Required field .
The Field Manager The Field Manager shows every field, its home unit, and the units it shows in. See Share a field across several units, or copy it to them .
If something goes wrong What you see
Why
What to do
“A field with this name already exists”
A repeated name in the unit.
Change the internal name. The label can repeat.
“This is a system field and cannot be deactivated”
A core field of the unit.
Only change its label, or hide it from the view.
A warning that boards group by the field
A Kanban board depends on it.
A message that the field would use a column another field writes
A clash with a shared field on the unit.
Good to know A field’s name and label are 1 to 100 characters. A field’s name can’t repeat in the same unit, and upper and lower case count as the same. System fields can’t be renamed, change type, or be deactivated. Did this guide solve it?
If not, we’ll ask what was missing.
We read every answer. To get a reply, use Contact support .
