Requirements
Supported document formats: PDF, Word, Excel, PowerPoint
Permissions to configure Field Rules (contact [email protected] if unavailable Or make use of the in-app chat) - available at no additional charge
Clearly labelled fields for triggers and dependent sections
Instructions
Field Rules operate using IF → THEN logic:
IF a signer selects a specific option
THEN another field or section becomes required or visible
Step 1: Label trigger fields
Identify fields that will drive the rule (checkboxes, choice fields, or text inputs).
Select the field → Show Advanced Setup → update the Field Name to indicate its purpose.
This trigger field is what the rule will reference.
Visual: Label a field
Step 2: Label resultant fields or sections
Label the field or group of fields that should appear when the trigger is activated.
Apply clear, unique labels for each dependent field or section.
Visual: Label an individual field & Field Groups
Step 3: Open Field Rules configuration
Click the Document tab above Page 1 → select Configure Field Rules.
If unavailable, request permission via in-app chat or email [email protected].
All conditional logic is managed here, not on the fields themselves.
Visual - Where to find field rules.
Step 4: Create your first rule
Click Add new field condition → Add Condition → select the trigger field.
Define the reaction when the signer interacts with the trigger.
Select the field or section that should appear when the condition is met.
Examples of conditions:
If ticked / If not ticked
Is equal to
Contains
Visual - Full setup of a rule (1 trigger field revealing 1 text field)
Visual - Full setup of a rule (1 trigger field revealing section of multiple fields)
Step 5: Save and test
Save your configuration.
Test the document in setup or preview mode.
Interact with the trigger field to confirm the correct fields appear or hide.
Best Practices & Notes
Field Rules only work if labels are correct. Keep labels clear, consistent, and unique.
Always mark both trigger and resultant fields as Required if the information is essential.
For triggers with multiple options, enable Mutually Exclusive Checkboxes to prevent conflicting inputs.
Test every Field Rule before sending to ensure correct behaviour.
To save time, configure Field Rules in templates, so rules do not need to be recreated for every document.
Example Use Case:
A health declaration:
Question: “Do you have any existing health conditions?”
If Yes → A follow-up section appears, marked as required.
If No → The signer moves to the next section without additional prompts.
This ensures signers only complete relevant sections, keeping documents concise and compliant.
Expected Outcome
Documents dynamically adjust to signer inputs, revealing only the sections that apply. This improves clarity, reduces unnecessary fields, and ensures required information is always collected.
FAQs
What happens if a field is not labelled correctly?
The rule will fail. Ensure both trigger and dependent fields have unique, clear labels.
Can Field Rules be reused across multiple documents?
Yes. Apply Field Rules in templates to avoid repeated setup. Be sure to avoid duplication of field labels where not intended across the pack.
Do signers see all fields before submitting?
No. Signers only see fields that are not linked to conditional rules. Dependent fields are revealed dynamically based on their inputs and the logic set up in the document.
Contact Support
Should you require any further assistance with this, please contact our Solutions team at [email protected]