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
Enable a method of recipient authentication using the recipient's smartphone to receive a text or voice message containing a password.
Overview
Phone authentication is a premium second-factor authentication method that secures a robust verification of identity by having the recipient authenticate with a code delivered to their phone as either a text message or a voice call (upon their request).
Availability:
Phone authentication is available for enterprise license plans only.
Phone authentication 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.
How it's used
The authentication process initially presents the recipient with a notification that they must enter a verification code to access the agreement. This notification provides the following:
- The last four digits of the recipient's phone number (as entered when the agreement was composed) so the recipient knows which device the code will be sent to.
- The (linked) name of the originator is provided in case the recipient needs to contact them for any reason (e.g., To change the phone number). The link opens an email to the sender of the agreement.
- This link can be modified to guide the recipient to an explicit address, like your support team.
- This link can be modified to guide the recipient to an explicit address, like your support team.
- An option for the recipient to have the code delivered via voice call or text message.
When the user is ready to receive the verification code, they select the Send Code button:
Once the Send Code button is selected:
- The page refreshes to allow the input of the access code.
- The indicated phone number receives an automated call or text with the five-digit verification code.
- The code is valid for 10 minutes. After that, the recipient must return to the email and send a new code.
- The recipient has a limited number of attempts to enter the correct code. The agreement is automatically canceled if the recipient fails enough times, and the sender is notified.
When 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 continue.
Acrobat Sign uses a US-based service that leverages multiple carriers to deliver text and voice messages globally. The carrier used for any individual contact is based on the best combination of cost and performance at the time the contact is requested.
Based on the overall volume of transactions, the carriers may not be local providers based on the sender's data center or the recipient's number.
Configuring the Phone authentication method when composing a new agreement
When Phone authentication is enabled, the sender can select Phone from the Authentication drop-down just to the right of the recipient's email address:
After the user selects Phone as the authentication method, they must provide the phone number to be used for the recipient's verification process.
Note:
- If the recipient delegates their role in the agreement, they must provide the new recipient's phone number.
- The phone number tied to the authentication attempt can be changed for in-process agreements by editing the authentication type on the sender's manage page.
If a "bad" phone number is detected when composing the agreement, the process stops, and an error message is presented at the top of the page:
Consumption of premium authentication transactions
As a premium authentication method, Phone authentication transactions must be purchased and made available to the account before agreements can be sent with the method configured.
Phone authentication transactions are consumed on a per-recipient basis.
e.g., An agreement configured with three recipients authenticating by Phone consumes three authentication transactions.
Configuring an agreement with multiple recipients decreases one transaction for each recipient authenticating by Phone authentication from the total volume available to the account.
- Canceling a Draft agreement returns all Phone authentication transactions 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 Phone (from any other method) consumes one transaction.
- If you change the same recipient back and forth between Phone authentication and other methods, you only consume one transaction total.
- If you change the same recipient back and forth between Phone authentication and other methods, you only consume one transaction total.
- Changing the authentication method from Phone to another method does not return the transaction.
- Each recipient authenticating with Phone authentication consumes only one transaction, no matter how often they attempt the process.
Track available volume
To monitor the volume of Phone authentications available to the account:
- Navigate to Account Settings > Send Settings > Identity Authentication Methods
- Select the Track Usage link:
Phone authentication and SMS link delivery share the same pool of transactions. Usage of the transactions is broken down in the pop-out ballon to show the volume consumed by SMS delivery and Phone authentication transactions.
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
The Audit Report clearly identifies that a phone number was used for identity verification.
- Only the last four digits of the phone number are exposed.
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 Phone authentication to reduce the friction of signing and save on the consumption of the premium authentication transactions.
- The phone number tied to the authentication attempt can only be changed for in-process agreements by editing the authentication type on the sender's manage page.
- Personalize your phone authentication messages to bolster recipient confidence in your text messages and to streamline customer contacts.
- Acrobat Sign text or voice messages are never unsolicited. They are always predicated on a signer who defines the contact type from the landing page of the Phone authentication challenge (by choosing their preferred option of Text or Voice) and then selecting the Send button to trigger the contact. The recipient's spam or malicious intent concerns can be mitigated mainly because the communication (voice or text) happens in near real-time.
- Acrobat Sign voice and text contacts never prompt the recipient to take action (e.g., visit a website or provide personal information.). Only a numeric code is communicated.
Configuration
Phone 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 the Phone method and configuration of the SMS options.
- Security Settings limit the recipient's attempts to enter the correct token.
Enable the authentication method under Send Settings
The option to use phone-based authentication can be enabled for senders by navigating to Send Settings > Identity Authentication Methods
- Phone authentication checkbox - When checked, Phone is an available option when agreements are composed.
- By default, use the following country code - Requires the admin to select a default country code for agreements sent through the group being configured.
- Personalize phone authentication message - Replace the embedded link to the agreement creator with some other literal value, like the email address of your support team.
Configure the Security Settings
Phone authentication requires the admin to configure a non-zero number of failed attempts allowed before the agreement is canceled. Five is the default.
This setting can be configured on the Security Settings page:
Automatic agreement cancellation when a recipient fails to authenticate
The agreement is automatically canceled if the limited number of Phone authentication attempts fails.
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.