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
Customers in regulated environments may need to ensure that the name value associated with their recipients remains consistent throughout the agreement lifecycle. This can become problematic when a name value is provided and that name changes during the signature process.
For example, a sender can include a recipient that is also an Acrobat Sign user in their account. Including an internal recipient provides a profile that is known to the Acrobat Sign system, and at the time the agreement is sent, the user's profile name is imported to the audit records and Manage page.
When the internal recipient opens the agreement, their profile name is prefilled into the signature field. If the signer does nothing, their name is used as the signature, and the audit report is generated with their internally defined name. However, the signer can change their name within the signature block. If they do so, the new name value is used from that point on throughout the audit report and on the Manage page.
If a customer is examining the interim audit report to establish system compliance, the change from the interim to the final audit report may be seen as non-compliant.
To overcome this, admins can configure their account or groups to prompt the sender to include a name value for each recipient as part of the agreement configuration process. The name value can be defined as either mandatory or not, depending on the document's requirements.
This feature only applies to agreements and web forms created through the Acrobat Sign web application.
When enabled, all recipients have the recipient name field available. When the name is mandatory, all recipients must have a name value provided.
If a name value is provided by the sender, the name is presented as a read-only field during the signature process, and the recipient may not alter it.
Only recipients are impacted. CC'd parties do not require a name-value to be included.
Supported functions
Current limitations
Configuring web forms
When Require recipient name on Send is enabled, web form configuration also allows for a name-value for any defined counter-signers:
The recipient experience
The recipient experience is not dramatically different when the required name value is applied. The practical differences are:
- Typed signatures automatically populate the name-value as defined and cannot be edited.
- Drawn/Image signatures present the name field in a read-only state.
The name-value associated with the audit report (and other surfaces where the name is exposed) is separate from the signature image. Because of this, Drawn (including Mobile) and Image signatures may display a different image of the name string than the name-value that is referenced throughout the document and auditing trail.
Configuration
Availability:
Require recipient name is available for enterprise license plans.
Configuration scope:
The feature can be enabled at the account and group levels.
The controls for this feature can be assessed by navigating to Send Settings > Require recipient name when sending from Adobe Acrobat Sign web application.
The configurable options are:
The setting to require recipient names is embedded into the transaction when the agreement is sent. Changing the setting takes effect immediately for newly created agreements, but does not impact previously sent agreements.
Related settings
Signers can change their name or initials
Enabling Signers can change their name or initials allows the recipient to change their name at the time they apply their signature.
If this setting is disabled, then the name value provided by the sender is read-only for the signer.
If a recipient changes their name value from the sender's provided value, an explicit record is logged in the audit report to reflect that change:
Authentication methods that lock the name value
In the Send Settings menu, there are authentication methods with sub-settings requiring a signer name on the Send page (e.g. Knowledge-based authentication).
When these settings are enabled in conjunction with the Require recipient name on Send setting, the name added on the recipient record is automatically imported to the authentication name fields.
If the name value is changed in the authentication method, the name values in the recipient record are updated to match. There is no method to have different values in these two interfaces.