Skip to main content
Make optional removes the required flag from selected fields while When matches — the opposite of Require answer. Use it to relax defaults when a section does not apply: optional invoice details when billing same as shipping, or skip phone when callback not requested.

​
When to choose this

Studio stores this action as unrequire_answer internally — the UI label is Make optional.

​
Exact behavior

  • Sets required: false on targets while When is true.
  • Last matching rule wins vs Require answer on the same target.
  • Hidden fields are never required anyway — Make optional mainly affects visible fields.
  • When When becomes false, required state may revert toward block default and other rules.

​
What changes on fill

​
Configure in Studio

1

Open a rule

Logic → Rules, or Branch / Add condition — identify fields that should stop being mandatory under some When.
2

Build When

e.g. “Same as shipping” equals Yes, Phone is empty, Plan equals Free.
3

Add Then → Make optional

Select fields to relax — VAT, Phone, Company legal name, etc.
4

Check rule order

If a global Require exists, ensure Make optional evaluates later when both could match.
5

Test submit on Fill

Confirm optional fields no longer block Next/Submit when rule active.

​
Worked examples

​
Same as shipping

When “Billing same as shipping” equals Yes → Make optional Billing address, Billing city
Fields stay visible but skippable.

​
No callback

When “Call me back” equals No → Make optional Phone, Best time to call
Pair with Hide blocks if you prefer removing fields entirely.

​
Free tier

When Plan equals Free → Make optional Tax ID, Purchase order

​
Optional attachment path

When “I have documentation” equals No → Make optional Upload supporting file

​
Test on fill

1

Default required visible

Asterisk present before rule.
2

Trigger When

Asterisk removed on targets.
3

Submit without optional fields

Succeeds if no other blockers.
4

Revert When

Required may return per block default / other rules.

​
Common mistakes

  • Make optional when Hide is clearer — hidden fields already non-blocking.
  • Rule order: global Require after Make optional re-mandates fields.
  • Expecting optional to clear validation errors from other rules on same field.

​
Troubleshooting

Later Require rule won — reorder or narrow When.
Redundant with Hide — consider Hide for cleaner UX.
Different required field still empty on current page.
Action unnecessary unless another rule adds Require — simplify logic.
Last modified on September 7, 2026