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
- 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
- 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
Enable a method of recipient authentication using sender-defined passwords.
Overview
The Signing password authentication method requires a recipient to enter a password that the agreement's sender provides. Passwords as a security method are well understood and easily adopted by recipients who might find more complex authentication methods daunting.
The sender defines the signing password when they compose the agreement, and it must be communicated to the recipient by some out-of-band process (Phone call, email, text).
Availability:
The Signing password is available for all plans.
Configuration scope:
The feature can be enabled at the account and group levels.
The Signing password is not a metered service. There is no charge for use, regardless of volume.
How it's used
The default authentication process challenges the recipient to validate their identity by entering the agreement's signing password in a text field.
- A link is provided for the recipient to contact the sender if they need to obtain the password:
Once the authentication is passed, the recipient is granted access to interact with the agreement as long as the session between their computer and Acrobat Sign persists.
If the recipient closes the agreement window for any reason or allows their session to expire, they must re-authenticate to resume their activity.
Configuring Password authentication when composing a new agreement
When Password authentication is enabled, the sender can select it from the Authentication drop-down to the right of the recipient's email address.
After selecting the Password authentication type, the sender must provide the password string.
Passwords can be up to 32 characters long using alphanumeric characters. The Security Settings dictate the required complexity of the string.
Best Practices and Considerations
- Passwords can be tricky to track for hundreds of agreements. Having an internal convention to build decryptable passwords may be helpful to ensure recipients don't get locked out of their agreements if a password is forgotten.
- Passwords can only be changed for in-process agreements by editing the authentication type on the sender's manage page.
- Passwords should be delivered to the recipient through an out-of-band method (e.g., Phone). Do not include the password in the agreement message.
- If you have the resources, configure the support contact to streamline any customer contacts.
Configuration Options
Signing password authentication has two sets of controls, which are available to be configured at the account and group levels:
- Send Settings, which control the sender's access to the password option.
- Security Settings, which govern the recipient's experience.
The option to use Signing password authentication can be enabled for senders by navigating to Send Settings > Signer Identification Options
- Signing password checkbox - When checked, Password is an available option for the agreements composed in the group.
- (Optional) Support contact - By default, the challenge page for the recipient requiring them to enter the password provides the sender's email address if the recipient needs to contact someone. The optional Support contact field replaces the sender's email address with a phone number or an email address, providing a funnel for inbound queries to a resource dedicated to resolving issues.
- (Optional) By default, use the following method - When Signing passwords are enabled, the option to set Signing password as the default authentication method is available.
Configure a support contact for password questions
At the account or group level, the Acrobat Sign administrator can configure a contact email address or phone number that is inserted into the authentication page when the recipient is prompted to apply the password.
No interaction is required on the part of the users after the setting is configured. The custom email/phone number is automatically embedded in all password authentication screens generated from the configured group/account.
Contact customization only requires an appropriate contact value to be entered into the setting field.
- The default behavior is to use the sender's email address as the contact value.
- The customization field accepts either a phone number or email address.
- The signing password contact can be customized at the account and group levels.
- Group-level configuration overrides the account-level setting for agreements sent from that group.
Configure the Security Settings
The agreement signing password has two control options that can be configured by the admin on the Security Settings page under the Agreement Signing Password section:
- Restrict number of attempts - Enabled by default. If disabled, then recipients can try to enter the password an unlimited number of times.
- Allow Signer XX attempts to enter the agreement password before canceling the agreement - The admin can enter a threshold number to limit the number of attempts a recipient can take to authenticate. Once the number of attempts is crossed, the agreement is automatically canceled, and the sender is notified
- Document Password Strength - This setting defines the minimum complexity of the passwords that are requested for:
- Recipient authentication for agreement access
- Signed agreement encryption (downloaded agreement PDFs)
- Signer Identity Reports (as related to Government ID reporting)
- Recipient authentication for agreement access
The setting values are:
► None - Requires the password to be set with at least one non-whitespace character
► Standard - Requires a minimum of six characters
► Medium - Requires a minimum of seven characters
► Strong - Requires a minimum of eight characters
If you don't see the Security Settings available in your menu, verify that the authentication method is enabled on the Send Settings page.
Individual tier accounts don't have access to the Security Settings tab. For these accounts, the Standard setting value is applied (a minimum of six characters).
Customers in the Acrobat Sign for Government environment don't have access to adjust the document password strength. These accounts must use a password consisting of at least 14 characters, including at least:
- One uppercase alpha character
- One lowercase alpha character
- One number
Audit Report
The audit report clearly indicates the recipient entered a valid password:
If the agreement is canceled due to the recipient being unable to authenticate, the reason is explicitly stated:
Automatic agreement cancellation when a recipient fails to authenticate
If the settings restrict the number of password authentication attempts, and the recipient fails to authenticate that number of times, the agreement is automatically canceled.
The agreement's originator is sent an email announcing the cancellation with a note identifying the recipient who failed to authenticate.
No other parties are notified.