Skip to main content
Hide blocks removes selected fields from the fill experience while When matches — respondents cannot see or edit them, and stored answers are cleared so hidden data never submits. Use it to strip irrelevant sections, collapse optional paths, and enforce “out of scope” UX.

​
When to choose this

​
Exact behavior

  • Targets become not visible on fill.
  • Answers on hidden fields are cleared on recalculation — prevents stale smuggling on submit.
  • Hidden fields are never required — engine clears required flag even if Require answer ran earlier.
  • Last matching rule wins vs Show blocks on the same target.
  • Default-hidden blocks (hidden in block settings) start hidden; Show can override while its rule matches.
Hiding clears data. If When toggles back, users re-enter answers — Show does not restore previous values.

​
What changes on fill

​
Configure in Studio

1

Open a rule

Logic → Rules, or Branch / Add condition on a field.
2

Build When

e.g. Plan is not Enterprise, Company is empty, Country is none of US.
3

Add Then → Hide blocks

Select blocks to remove from fill.
4

Avoid Show conflicts

Do not Hide and Show same target without mutually exclusive When clauses.
5

Pair with user messaging (optional)

Static copy explaining why sections are absent — Hide alone gives no explanation.
6

Test toggle on Fill

Fill field → trigger Hide → confirm data cleared in submission preview if available.

​
Worked examples

​
Hide enterprise SSO

When Plan is not Enterprise → Hide blocks SSO details, Audit log

​
No company → no invoice block

When Company is empty → Hide blocks Invoice address, Tax ID

​
Domestic-only shipping

When Country equals US → Hide blocks International customs form
Often paired with inverse Show on international path.

​
Cleanup “Other” follow-up

When Industry is not Other → Hide blocks Please specify industry
Clears free text if they switch away from Other.

​
Test on fill

1

Trigger Hide

Targets disappear from form.
2

Had data before hide

Re-show (When false) — fields empty.
3

Submit with hidden required fields

Submit succeeds — hidden fields cannot block.
4

Toggle When repeatedly

No ghost data in submission.

​
Common mistakes

  • Hiding without inverse Show when users can return to qualifying answers — field stays hidden until Show rule matches.
  • Expecting hidden values in integrations — cleared answers omit from payload.
  • Hide vs Make optional — optional visible fields still show; Hide removes entirely.

​
Troubleshooting

Later Show rule won, or When false. Check rule order.
Different visible required field empty — not the hidden one.
Should not happen after hide recalc — retest Fill fresh; inspect integration mapping.
Require ineffective while hidden — by design. Show first on another rule if needed.
Last modified on September 7, 2026