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 authentication for recipients in the United States using the recipient's public information sourced from multiple public databases.
Overview
Knowledge-based authentication (KBA) is a premium second-factor authentication method that secures high-level identity verification. KBA is only valid for vetting the identity of US-based recipients.
The authentication process challenges the recipient to enter their first and last name and home address. The recipient may optionally enter the last four digits of their US social security number.
After successfully answering several questions, the recipient can interact with the agreement.
Availability:
Knowledge-based authentication is available for enterprise license plans only.
KBA is a premium authentication method that has a per-use charge:
- Transactions must be purchased through your Adobe sales representative.
- Transactions are an account-level resource. All groups consume from the same global pool.
Configuration scope:
The feature can be enabled at the account and group levels.
KBA is only applicable to US-based recipients.
How it's used
When the recipient accesses the Review and sign link, they are delivered to the KBA identity verification page, where they are prompted to enter their name and address:
The information entered is used to query multiple public databases, generating a list of three to four nontrivial questions for the recipient.
Example questions:
- Select the correct house number of the address you shared with {some name}
- Which of the following aircraft have you owned
- In which of the following cities have you attended college
- From whom did you purchase the property {some address}
- Which age range matches the age of {some name}
Once the authentication is passed, the recipient can interact with the agreement.
If the recipient closes the agreement for any reason before completing their action, they must re-authenticate.
To secure against brute force attempts to authenticate, the KBA method can be configured to cancel the agreement after a defined number of failed attempts.
Configuring the Knowledge-Based Authentication method when composing a new agreement
When KBA is enabled, the sender can select it from the Authentication drop-down just to the right of the recipient's email address:
An optional configuration of the KBA method may require that the sender insert the recipient's Name.
This option ensures that the name of the recipient remains consistent throughout the lifespan of the transaction.
If KBA is not an option for the sender, then the authentication method isn't enabled for the group from which the user is sending.
Consumption of premium authentication transactions
As a premium authentication method, KBA transactions must be purchased and available to the account before agreements can be sent with KBA configured.
KBA transactions are consumed on a per-recipient basis.
e.g., An agreement configured with three recipients authenticating by KBA consumes three authentication transactions.
Configuring an agreement with multiple recipients decrements one transaction for each recipient authenticating by KBA from the total volume available to the account.
- Canceling a Draft agreement with KBA configured returns all KBA authentication transactions back to the total volume available for the account.
- Canceling an In-progress transaction does not return the authentication transaction to the total volume available for the account.
- Changing an authentication method to KBA (from any other way) consumes one transaction.
- If you change the same recipient back and forth between KBA and other methods, you only consume one transaction total.
- If you change the same recipient back and forth between KBA and other methods, you only consume one transaction total.
- Changing the authentication method from KBA to another method does not return the transaction.
- Each recipient authenticating with KBA consumes only one transaction, no matter how many times they attempt the process.
Track available volume
To monitor the volume of KBA transactions available to the account:
- Navigate to Send Settings > Signer Identification Options
- Select the Track Usage link:
Accounts that have purchased the service under the VIP licensing program have a modified format Track Usage pop-out to represent better the number of transactions within the context of their licensing scheme.
Audit Report
A successful KBA identity verification is explicitly logged in the audit report with the authentication token provided by LexisNexis.
If the agreement is canceled due to the recipient being unable to authenticate, the reason is explicitly stated:
Best Practices and Considerations
- If second-factor signature authentication isn't required for your internal signatures, consider the Acrobat Sign Authentication method instead of KBA to reduce the friction of signing and save on the consumption of the premium authentication transactions.
Configuration Options
Knowledge-based authentication has two sets of controls, which are available to be configured at the account and group levels:
- Send Settings control the sender's access to and configuration of the KBA option.
- Security Settings govern the recipient's experience insofar as how many attempts they can make before the agreement is canceled.
Enable the authentication method under Send Settings
The option to use knowledge-based authentication can be enabled for senders by navigating to Send Settings > Signer Identification Options
- Knowledge-based authentication checkbox - When checked, KBA is an available option for the agreements composed in the group.
- (Optional) Require signer name on the Send page - When checked, senders must provide the recipient's Name. This name value persists throughout the signature cycle; the recipient cannot change it.
- Enabling this option prevents delegation of the agreement by the recipient (including auto-delegation).
- Replace Signer will work for the sender from the modern Manage page.
- (Optional) Once KBA is enabled, you can define it as the default method when composing a new agreement.
- Save the change to the page.
Configure the Security Settings
Knowledge-Based Authentication has three configurable options that can be found on the Security Settings page:
- Restrict number of attempts - Enabled by default, this checkbox enables the security option to cancel the agreement if a recipient fails to authenticate within the defined number of. If disabled, recipients can try to authenticate an unlimited number of times.
- Allow Signer XX attempts to validate their identity before cancelling the agreement - The admin can enter any number to limit the number of attempts to authenticate. Once the number of attempts is crossed, the agreement is automatically canceled.
- Knowledge-Based Authentication difficulty level - Defines the complexity of the validation process:
- Default - Signers will be presented with three questions and must answer them correctly. If they only answer two correctly, they will be given two more questions and required to answer them correctly.
- Hard - Signers will be presented with four questions and must answer them correctly. If they only answer three correctly, they will be given two more questions and required to answer them correctly.
If you don't see the settings in your menu, verify that the authentication method is enabled on the Send Settings page.
Automatic agreement cancellation when a recipient fails to authenticate
If the settings restrict the number of KBA 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.