What's New
Get Started
Administer
- Admin Console Overview
-
User Management
- Adding users
- Create function-focused users
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
-
Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Claim your domain
- Report Abuse links
Send, Sign, and Manage Agreements
-
Recipient Options
- Cancel an email reminder
-
Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
-
Send Agreements
- Send (Compose) page
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
-
Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Authoring FAQ
- Sign Agreements
-
Manage Agreements
- Manage page overview
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
-
More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates
- Transfer ownership of web forms and library templates
-
Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
-
Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Agreement data extraction
- Agreement notifications
- Agreement generation
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
Support and Troubleshooting
Overview
Many agreements (such as tax documents, land registry, powers of attorney, transfers of assets, and so on) require that the recipient sign their agreement in the presence of a witness. The witness can be almost any party physically present to observe the signer's application of their signature.
Acrobat Sign provides a selectable "role" in the configuration process that inserts a "signer" recipient with an associated "witness" recipient that the signer must define.
- Before the signer can review the agreement, they must provide the witness's name and email address.
- After the signer completes their signature process, the witness receives an email requesting their attestation to the witnessing of the signature process. The witness is asked to review their name and email address before they can interact with the agreement.
- Additional fields can be assigned to the witness to capture any information your compliance requirements demand.
A "witness" is different than a "notary public."
A "witness" can be any person who is:
- of majority
- of sound mind
- an independent, non-biased person who is not a party to the agreement
- physically present at the time the signer applies their signature to the agreement
Witnesses may not be paid for the act of witnessing the signature process.
A "notary public" is typically a type of witness that is commissioned by a governing body (such as the State). The notarization process tends to be considerably more formal insofar as documenting the identity of the signer and usually requires a fee for processing.
E-notary services are also available through Acrobat Sign.
Work with your legal department to confirm if a witness or a notary is the requirement for your compliance demands.
Availability
The e-Witness role is available through different interfaces based on the enterprise service you have purchased.
Please select the version of Acrobat Sign you are using:
The configurable options are:
- Allow senders to mark recipients as signers with witness - When enabled, signers have the option to select the Sign with Witness role on the Send page and in the Custom Workflow Designer.
- When disabled, the role is not available in the sender's pick list for the recipient role.
- Allow signers to co-witness each other's signature - When enabled, recipients that are signers on an agreement can also be witnesses for other signers.
- When disabled, any participant who is part of the agreement (as identified by their email address) may not be a witness for another recipient within the scope of that one agreement.
When the control is enabled, the Sign with Witness role is exposed in the list of roles available to the sender on the Compose page and in the custom send workflow designer:
Once the role is enabled, senders can find the Sign with Witness role listed in the Role selector on the Compose page.
When a signer selects the Sign with Witness role, an additional configurable property is added below the recipient's record to identify that a witness is required and allow for configuring the authentication and private message for the witness.
Due to the nature of the witnessing process and how the witnesses are indexed, only a sequential signature flow is supported.
Phone authentication is available for use cases where a second-factor One-Time Password (OTP) is required for the witness (e.g., HMLR deeds).
Phone authentication is configured by the sender when composing the agreement, but the sender isn't asked to provide the witness's phone number. The signer provides the phone number of the witness when they identify them.
The witness is required to use a mobile phone to authenticate, and a text message is delivered (the phone call option is suppressed).
If a landline is used, an error is displayed informing the witness that they must use a mobile phone.
The check to ensure the phone is a mobile device is in development and expected to be available in the March 2025 release.
Second-factor OTP witness authentication is optional in the sender's interface but may be required for your business use. Check with your legal team to understand your compliance obligation.
Private messages may also be added for the witness:
Designing custom send workflows
Users who design custom sending workflows can find the Signer with Witness option when selecting a new recipient in the recipient flow chart.
Setting the Signer with Witness role installs both the signer (Recipient) and the witness (Witness Recipient) signer objects.
Configuration of witnesses in the Workflow Designer is expected to be in place for the March 2024 release. The current Insider Access version does not yet support this functionality.
Ensure that the required fields are placed on the agreement for the witness
Fields must be authored into the document where the witness's signature is required. If a signature field is not placed for the witness, one is automatically placed at the end of the document.
Some use cases may require additional information from witnesses to complete a valid witnessing. Work with your legal team to determine what information is needed. Add the fields to capture this information, assign them to the witness, and mark the fields as required.
Limited Document Visibility rules apply to witnesses like any other participant. Only the files that contain fields for the witness can be viewed.
In-app Authoring: Assigning fields to the witness
The in-application authoring environment identifies the witnesses in the signature flow order and provides color-coded identifiers for them in the Recipients list.
Text tags
Witnesses are recipients with regard to the indexing of participants. If you have two recipients that each require a witness, then:
- The first signer is _es:signer1
- The witness attached to the first signer is _es:signer2
- The second signer is _es:signer3
- The witness attached to the second signer is _es:signer4
The assignment of the text tag identifiers is consistent with the signature flow of the agreement. However, the indexing on the compose page does not account for the witnesses in the interface. (Witnesses are presented as an ancillary record of the identified recipient.)
Take the time to design and test your forms carefully to ensure the signature flow is correctly processed and participants are given access to the correct fields.
Manage page status
An agreement on the Manage page reflects the status of Out for Witnessing when the signature cycle is waiting for a witness to complete their attestation.
Note that recipients who are not witnesses continue to show the status appropriate for their role in the agreement (Out for signature, Out for approval, and so on).
The Activity list provides the same events of the audit report in a condensed format. The witness activities are clearly identified, but the signer's event does not include their requirement for a witness.