A signable web form can be created to embed on your website (or send as a web link), allowing multiple people to easily access your form or document and create an agreement.
A web form can be configured to have one or more participants, multiple counter-signers, and multiple CC'd parties as well. The signature flow for a web form is:
Business and Enterprise service levels have the option to configure the web form access and signer options.
Web form access and signer options can be enabled or disabled at the account or group level by navigating to Account > Account Settings > Global Settings > Web Forms
Web forms are subject to several general settings that cover all agreements in a specific group. However, the practical use of a web form is often different than an agreement sent directly to a known recipient, and the related settings regarding authentication and email options can be in conflict.
Customers that have enabled Users in Multiple Groups may find it useful to create a new group with customized settings for the web form experience (eg; Internal web forms that require less stringent authentication).
In terms of controls that directly influence web forms, there are several configuration options:
Checking this option exposes the Publish a web form option on the Home page, allowing users to create forms as needed.
When enabled, email addresses can be added as CC'd parties to the web form. Otherwise, the option to add CC'd parties is removed from the creation process.
When enabled, a Download PDF link is exposed in the web form Options, allowing the recipient to download the blank web form as a PDF.
Web forms require that each participant provide their email address so the signature action can be explicitly attributed and validated.
The Require an email address in the signature block setting dictates when the email is collected, within the fields of the web form itself, or in an overlay after the signing process.
When the setting is enabled, an Email address field is required for each signer within the bounds of the document. This field can be an individually placed Email field or the built-in email field included when a Signature Block is placed.
The system automatically places a Signature Block field at the bottom of the last page for every recipient that does not have an Email field on the document.
When the setting is disabled, the web form does not require an email field to be present within the bounds of the form. After committing their signature, the recipient is prompted to provide an email address via an overlay interface.
In all cases, an email address must be collected for each participant
When Require Signer to verify their email address is enabled, the recipient is required to verify their signature before the participant's is signature completed.
The participant is informed of the requirement to verify their signature via emailed link:
The audit report clearly indicates that the email was verified:
When Require Signer to verify their email address is disabled, the participant does not need to verify their email to complete their signature process. The agreement assumes a completed status or progresses to the next participant.
The audit report for unverified email addresses indicates that verification was waived:
Unverified signatures are subject to repudiation.
If you disable the email verification for the participant, and you require a legally binding signature, ensure that you are using some form of authentication that identifies a unique person (e.g.: KBA).
If additional participants are included by the first signer, then email verification must be completed before the second participant is notified (regardless of this setting).
When Allow additional participants is enabled, the web form interface exposes an Add Participant link that inserts one additional participant record per click (up to a maximum of 25 additional participants).
When Allow additional participants is disabled, the interface does not permit adding additional participants, and web forms only allow one external signer.
Only when the web form is in a Draft status.
After a web form is created, the name of the web form can not be updated.
The web form creator always receives the completed agreement (unless settings are in place to suppress the notification).
If another party is required to be notified when the web form agreement is signed, the CC field can be used to ensure that party is automatically included.
After the web form is published, the counter-signers can only be edited on the Manage page.
Only the email addresses can be edited. The number of counter-signers may not be changed.
If the creator of the web form has been added to the web form counter-signers, that user may not be edited
After a web form is created, you can edit the CC'd parties on the Manage page.
Templates in the Acrobat Sign library can be used as the base for a web form by attaching them through the Add Files link.
Digital Signature fields are not currently supported in web forms.
Attempting to save a web form with a digital signature will trigger an error message identifying unsupported field types.
Instruction for disabling the email verification process can be found in the Configuration section.
Disabling email verification does not remove the requirement for the signer to supply an email address.
If you disable the email authentication of the signature, and you require a legally binding signature, ensure that you are using some form of authentication that identifies a unique person (eg: KBA, Password).
The URL to a web form is just a URL like any other.
Adding the URL to a web form as a hyperlink does not logically link any agreement generated by the web form to the source agreement.
Data collected on a web form is contained within the transaction ID of the agreement. The data is not populated anywhere else in the Acrobat Sign system, and if the agreement is completely deleted, the data is deleted as well.
Reporting on the web forms pulls the content from the agreement(s) to populate the report but does not save the data in any new locations.
The Activity section of the parent web form template records the major events like Creation, Enable/Disable, and replacing participants