Set conditions on form fields in Acrobat Sign

Last updated on Aug 31, 2026
Alert

This article contains prerelease information. Release dates, features, and other information are subject to change without notice.

Show, hide, enable, or disable form fields based on information entered elsewhere in the agreement.

In Adobe Acrobat Sign, conditions let one field respond to the value of another field. Use them when a question or input should appear or become available only when a particular response makes it relevant.

For example, you can show an additional Text field only when a recipient selects a Checkbox indicating that more information is required.

Before you begin

Add and configure the fields that will participate in the condition before creating the rule.

Use meaningful field names so you can identify the correct fields when building conditions.

Conditional behavior is available for supported form fields except Link.

Add a condition

Select the field whose behavior you want to control.

Open Customize field.

Expand Add or edit conditions.

Under Field state, choose what should happen to the selected field:

  • Show this field
  • Hide this field
  • Enable this field
  • Disable this field

Choose the field whose value should control the behavior.

Choose the comparison operator.

Enter or select the value that triggers the condition.

Review the rule and confirm that it produces the intended behavior.

Available comparison operators depend on the values being evaluated and can include comparisons such as equals, contains, or greater than.

Acrobat Sign Customize field panel showing a condition that controls a selected form field based on another field's value.
Descriptive field names make conditional forms easier to maintain because the rule builder identifies dependencies by field rather than by their position on the document.

Choose the field state

The Field state determines what happens when the condition is met.

Field state Result
Show this field The field becomes visible when the condition is met.
Hide this field The field is hidden when the condition is met.
Enable this field The recipient can interact with the field when the condition is met.
Disable this field The field remains visible but can't be completed or changed while disabled.

Choose the behavior based on whether the recipient needs to see the field or interact with it.

Use multiple conditions

Select the add-condition control when the field's behavior depends on more than one value.

Use When to determine how Acrobat Sign evaluates the conditions:

  • Any — The field state is triggered when at least one condition is met.
  • All — The field state is triggered only when every condition is met.

For example, use All when an additional field should appear only if the recipient selects a particular option and enters a value that meets another requirement.

Acrobat Sign conditions panel showing two field conditions evaluated using the All option.
Combining conditions can keep a form shorter for most recipients while exposing additional questions only for the responses that require them.

Understand Required fields with conditions

A field can be both Required and conditional.

If a condition hides or disables a Required field, the recipient doesn't have to complete that field while it remains hidden or disabled.

If the condition later makes the field visible and enabled, its Required setting applies again.

This lets you require information only when the recipient's earlier responses make that information relevant.

Review conditional behavior

After creating conditions, review the fields involved and confirm that:

  • The correct field controls the behavior.
  • The comparison uses the intended value.
  • Any or All matches the intended logic.
  • Required fields become available when they need to be completed.
  • Each signer retains a visible signature field.

For general field configuration and naming, see Add and configure form fields.

For a comparison of properties supported by different field types, see Form field properties.

Prerelease documents for this feature: