What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
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
- Edit a user's group membership through the group interface
- 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
- Account/Group Settings
- Settings Overview
- Global Settings
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup
- Add logo
- Customize company Hostname/URL
- Add company name
- Post agreement URL redirect
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send settings
- Show Send page after login
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
- Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Download Agreements in Bulk
- 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
- Restart the agreement
- 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
- 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
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library 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
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- 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
Updating the recipient's name
The original sender of an agreement can change the name value of a recipient by opening the agreement in their Manage page, selecting the recipient, and clicking the Edit link:
The audit report indicates the name change as a replaced signer with the same email value:
The option to edit the recipient's name is only available until the first recipient applies their signature. After the first recipient has completed their activities on the agreement, all name values become immutable.
Replacing the recipient
Replacing the current recipient follows the same process, with the only exception being that a name value is required when the new recipient is added:
The audit report indicates the replaced signer with new name and email values:
The recipient of an agreement can delegate their agreement authority by either clicking the delegate link in the "Review and sign" email, or through the Delegate signing to another option on the signing page:
The audit report indicates the replaced signer with new name and email values:
Current limitations
Custom workflows currently do not support requiring the name when a recipient is pre-defined.
Adding authentication that does require a name-value (e.g. Knowledge-based authentication) can still be used:
Recipient groups
Recipient groups do not require that the name-value be included for each recipient in the group:
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.
When Require recipient name is enabled, the Send page is modified to include an additional section in the recipient record to provide the name value:
When the recipient name value is enabled as mandatory, an asterisk is applied next to the field tag to identify it as a required field.
If the user attempts to send the agreement without the name value being provided, the field highlights with a red frame and an error notice is displayed at the top of the window:
When the feature is disabled, the recipient record does not provide a field for the recipient's name:
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.
Users that are known to the account (existing Acrobat Sign users in a trusted account) may display a name value on the Manage page that is different than the name entered by the sender.
This is because the name used on the Manage page is pulled from the user's profile value when building the table of agreements. This behavior will be corrected to ensure the name used reflects the name entered by the sender in a future patch.
Given: Required recipient name is enabled for the sending account.
When an agreement is sent to a user email address that is registered to a user in the Acrobat System, the recipient's profile name is used in the audit report for Reminder events (instead of the provided recipient name).