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 through the Adobe identity management system.
Overview
Adobe Acrobat Sign Authentication is a single-factor identity verification method that requires the recipient to authenticate to the Acrobat Sign identity system. For recipients with an existing Acrobat Sign identity, this is an easy verification request to a known entity.
Additionally, there are options that can pre-fill the recipient's email address into the verification panel when challenged or even bypass the manual re-authentication process entirely if the recipient is already authenticated to Acrobat Sign. These qualities make Acrobat Sign Authentication the smoothest experience for internal recipients required to provide an authenticated signature.
Recipients who don't have an Adobe account tied to the email address the agreement is sent to will be required to create a new Adobe user account to complete the verification process.
Availability:
Acrobat Sign authentication is available for enterprise license plans only.
Configuration scope:
The feature can be enabled at the account and group levels.
Acrobat Sign authentication is not a metered service. There is no charge for use, regardless of volume.
How it works
The default verification process challenges the recipient to validate their identity by authenticating to the Acrobat Sign service. A button to the authentication panel is provided:
After selecting the button, the authentication panel allows the recipient to authenticate to their Acrobat Sign account.
- Options are available for the native Acrobat Sign identity system and the Adobe Admin Console.
Once the authentication is passed, the recipient can interact with the agreement.
If the recipient closes the agreement window before completing their action, they must re-authenticate to resume.
Configuring the Acrobat Sign Authentication method when composing a new agreement
When Acrobat Sign authentication is enabled, the sender can select it from the Authentication drop-down just to the right of the recipient's email address:
Audit Report
The audit report clearly indicates the recipient identity verification with Adobe Acrobat Sign:
Best Practices and Considerations
- Acrobat Sign Authentication isn't a second-factor authentication and should not be used when the signature requires additional authentication (beyond email authentication).
- Acrobat Sign Authentication requires that the recipient have an Acrobat Sign Identity. If they don't, a new account must be created before the recipient can authenticate, and that level of friction is likely to cause frustration. For this reason, using Acrobat Sign Authentication for external recipients isn't recommended.
- The Acrobat Sign Authentication method is best used for internal authentication as all internal recipients are known to have Adobe IDs.
- Customers who manage their users in the Adobe Admin Console can configure their organization to leverage their SSO solution through Acrobat Sign authentication, removing the requirement for recipients in the customer's company to have a licensed user in the Acrobat Sign system.
- Before configuring your account to auto-populate the recipient's email or bypass the re-authentication process, check with your legal team to understand your requirements for a valid signature. Ensure the options you configure still comply with the needs of the resultant document.
- When recipients access agreements directly from the Acrobat Sign Manage page, Acrobat Sign Authentication is the primary (and only) authentication factor. The email link (typically providing the default primary authentication element) is bypassed and replaced with the authenticated session to Acrobat Sign. In this scenario, Acrobat Sign Authentication duplicates the primary authentication factor.
- Accounts that purchase premium authentication transactions may want to consider setting the account-level settings to limit internal recipients to only using the Acrobat Sign Authentication method if extra authentication isn't required for the internal signers. This could prevent the accidental usage of premium assets. Groups can always be configured for other authentication methods as needed:
Configuration Options
Configure the Acrobat Sign Authentication method by navigating to Send Settings > Signer Identification Options
There are five controls relevant to the Acrobat Sign Authentication method:
- Acrobat Sign Authentication - The core feature; checking this box enables access to the authentication method for senders when composing agreements
- By default, use the following method - Defines the default value inserted into the recipient's Authentication option
- Identity authentication for internal recipients - Enabling this option allows internal recipients to be configured with different authentication options and defaults.
- Generally, it's recommended that Acrobat Sign Authentication be used only for internal recipients.
- The Acrobat Sign Authentication access option and the By default selector are replicated to set the internal recipient experience.
- Allow Acrobat Sign to auto-populate the Signers email address for each authentication challenge - When enabled, the recipient's email is imported from the agreement into the authentication panel. The imported email value is fixed, and the recipient may not change it.
- Don't challenge the signer to re-authenticate if they are already logged in to Acrobat Sign - When enabled, the recipient isn't challenged to re-authenticate when opening an agreement if they are already authenticated to the Acrobat Sign service.
- This requires the agreement to be opened in the same browser as the authenticated session to Acrobat Sign.
- This requires the agreement to be opened in the same browser as the authenticated session to Acrobat Sign.