Show or hide a field based on another field’s value
Make the form shorter: “Loss reason” shows only when the status is “Lost”, and “Company details” shows only when the type is “Company”.
Before you start · for ownersThe permission to edit units
Before you start · for owners
The permission to edit units
- You need: The permission to edit units
Steps
1
Open the field’s settings → Conditional visibility, and turn it on.
2
Choose the action: Show when the condition is met, or Hide when it’s met.
3
Add one or more conditions with Add condition: the trigger field, the operator and the values.
4
Choose how the conditions combine: all of (every condition) or any of (one is enough).
5
Turn on Clear this field’s value when hidden if you want the value cleared when the field hides.
6
Save.
Hiding isn’t protection
A hidden field is still in exports, document templates and the API, and automations can write to it. To control who sees data, use permissions.
How it works
The operators: is, is not, is one of, is not one of, is empty, is not empty. They work like the ones in required on a condition.
In multi-select and tag fields, “is” is met if any chosen value is one of the condition’s values.
The condition stores the option’s ID, so renaming the option doesn’t break the rule.
Fixed rules
- A hidden field isn’t required, so it never blocks saving.
- A hidden value stays saved by default, unless you turn on clearing it.
- If the rule can’t be evaluated, or the trigger field is deactivated, the field shows and works normally.
- Hiding only applies to the form and the details page. The table, Kanban and exports aren’t affected.
If something goes wrong
What you see
Why
What to do
“A field can’t show or hide itself”
The trigger is the field itself.
Choose another field.
A message about fields depending on each other in a loop
Two rules that point at each other.
Delete one of them.
The field shows despite the condition
The trigger is deactivated or deleted, so the field shows as a fallback.
Activate the trigger again, or choose another one.
Good to know
The trigger is from the same unit.
A field can’t hide itself, and two fields can’t each depend on the other.
When you copy the field to another unit, the rule is deleted if its trigger doesn’t exist there.
Did this guide solve it?
If not, we’ll ask what was missing.