Skip to main content

Conditional fields and signers

Control signing flow with conditional fields.

Conditional fields in SignNow let you control how and when fields are completed, ensuring documents follow a specific signing sequence. This feature can be applied within a single signer’s role (for example, making one field visible only if another is filled out) or between multiple signers (for example, one signer must complete their section before the next person can start).

Practical use cases include:

  • HR forms – An employee fills in personal details, and only then HR sees the payroll section.

  • Sales contracts – A client selects a service option, and only the matching pricing fields become available.

  • Legal workflows – One party must sign and confirm terms before another party is invited to sign.

By using conditional fields, you reduce errors, guide signers step by step, and keep sensitive or irrelevant fields hidden until they’re needed.

📝 Conditional fields are available on specific plans only. Please refer to the SignNow pricing page for more information.

Conditional fields setup

1. Open your document/template in SignNow by clicking its name or hitting the Prepare and Send option on the right side of the form in question. The Prepare and Send option is only available if you haven't set up fields and recipients yet.

2. In editing mode, select the field(s) that should appear conditionally, and then choose the field that will serve as the condition trigger. To do so, click on a field that should be conditional and scroll down the tab on the right side to enable the Add Conditional Rule setting. In this example, we want to only show the information about the accompanying person if the parent consented via the checkbox. So the condition that we will be setting is to hide the text fields related to the Accompanying person role unless the parent ticks off the checkbox during their portion of signing the form.

Depending on your use case, you can set the following:

  • whether the field is filled out/empty;

  • the field that the condition depends on.

📝 If a condition depends on whether a checkbox is ticked or a field is filled in, make that trigger field itself optional. Otherwise the signer can't complete signing without filling it out, which defeats the purpose of the conditional field.

You can create multiple conditions by clicking the + symbol and then choosing how they should relate to each other:

  • OR – The field will appear if any of the listed conditions are met.

  • AND – The field will appear only if all conditions are met.

  • NOT AND – The field will appear only if none of the conditions are met.

  • NOT OR – The field will appear if not all of the conditions are met.

You can add conditions into a subgroup, and remove a condition by clicking the trash icon next to it.

Grouping matters because conditions inside a group are evaluated together as a single unit. Without a group, the conditions are read one after another and the logic can collapse into something you didn't intend — for example, a stray "OR" can make one condition alone enough to show the field. Putting related conditions into a subgroup locks them together, so the whole group must resolve before the field is shown or hidden. Use it whenever a field should depend on a combination of answers rather than a single one.

Conditional signing

An entire signing role can be set as conditional. This means the invite will only be routed to that additional signer if certain conditions are met in a previous step. If the condition isn’t met, the invite is skipped, and the document is treated as fully completed.

Did this answer your question?