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
This article describes the new Enforce Identity Authentication experience accessed from the Bio-Pharma Settings tab of the admin menu. (Released in November 2023.)
This new experience is enabled by default for new accounts after the November 2023 release and enabled by an administrator for accounts that existed prior to the November 2023 release.
The classic Enforce Identity Authentication process document is still available and will remain so until the experience is retired.
Overview
The Enforce identity authentication feature defines the trigger events that prompt a recipient to re-authenticate when interacting with an agreement. There are three independently selectable options:
- Authenticate when opening the agreement.
- Authenticate when applying a signature.
- Authenticate when completing the agreement.
The triggers that are enabled encompass all signers included in the agreement (internal and external).
Availability:
Enforce identity authentication is limited to enterprise license plans.
Configuration scope:
The features can be enabled at the account and group levels.
The November 2023 release separated the controls for enhanced identity authentication, removing the dependency between them.
Accounts created before the November 2023 release must opt in to the separated controls experience by selecting the Enable Now button on the Bio-Pharma Settings page.
Accounts created after the November 2023 release automatically inherit the modern experience.
The modern experience can only be enabled at the account level. This means that:
- All groups that haven't explicitly configured their Bio-Pharma Settings page will continue to inherit the same configuration as the account-level controls.
- Explicitly configured groups will adopt the new separate control experience, but will also retain their existing control configurations.
It's important to note that enabling the new experience does not change any effect currently observed when signing an agreement, regardless of the group from which the agreement is sent.
The practical impact of enabling the new experience is that you can enable or disable each of the three controls discretely.
Enabling the new Enforce Identity Authentication environment has two consequences:
- The classic experience requires that Challenge the user to authenticate themselves when the agreement is opened must be enabled before either of the subordinate controls can be enabled.
The modern experience removes that requirement, allowing each of the three controls to be enabled individually.
The user interface is updated to show all three controls at the same "level," indicating that all three are equally available.
- The classic experience can show checked boxes in the subordinate controls when the parent control is disabled.
Because the parent control is disabled, the subordinate controls are not active, but the greyed-out checkboxes persist and may give the wrong impression of being active.
When the modern experience is enabled:
• If the Challenge the user to authenticate themselves when the agreement is opened control is disabled, the (previously) subordinate controls will be cleared and properly shown as unchecked.
• If the Challenge the user to authenticate themselves when the agreement is opened control is enabled, the (previously) subordinate controls will retain their values.
Enabling the modern experience is not reversible.
Once you save the enablement, the account is updated and the Enable Now banner is removed from the interface.
How it's used
Prerequisites
For Enforce identity authentication to work, the signer must be authenticating their identity with either:
- Phone authentication (SMS) - Recommended for external signers.
- Acrobat Sign authentication - Recommended for internal signers.
The agreement processes normally if any other authentication method is defined, but Enforced identity authentication isn't applied for that recipient. Configuring some recipients to apply Enforced identity authentication and others to bypass it by leveraging different authentication methods in the same transaction is permissible.
The authentication method is defined on the Send Settings page in the Identity Authentication Methods section.
The recipient experience
The recipient is presented with the authentication UI upon triggering an authentication challenge.
The two authentication options are:
- Phone authentication - An SMS-based text that provides a five-digit code that the signer must enter before affixing the signature
- Acrobat Sign authentication - A request to authenticate to Acrobat Sign through the Adobe identity management system. Because authentication to Adobe is required, this method is primarily recommended for internal recipients where the sender can reasonably expect such an account exists.
Recipients that authenticate using the Acrobat Sign authentication method must authenticate through the Acrobat identity management system. All social authentication options (Google, Facebook, and Apple) are removed during the authentication process.
Accounts that configure their Admin Console organization to allow SSO authentication will authenticate against their configured identity provider, removing the requirement for their internal recipients to be entitled with a license for Acrobat Sign.
Once the authentication is passed, the recipient can continue the form-filling/signing process.
Configuration
To enable Enforce identity authentication options, navigate to Bio-Pharma Settings > Enforce identity authentication.
Enforce identity authentication contains three independently selectable options:
- Challenge the user to authenticate themselves when the agreement is opened - When enabled, each recipient must authenticate before the agreement is opened for viewing.
- Challenge the user to authenticate themselves when the signer clicks a signature field in the agreement - When enabled, all recipients must authenticate every time a signature field is selected (before the signature can be applied).
- Only signature and signature block fields are re-authenticated; initial fields are not.
- The setting impacts both required and optional signature and signature block fields.
- Challenge the user to authenticate themselves when the Click to Sign button is selected after the signing ceremony is complete - When enabled, the recipient must reauthenticate after selecting the Click to Sign button (when they have completed their interaction with the agreement).
Related settings
The option to Challenge the user to authenticate themselves when the agreement is opened can be suspended for recipients in your account if they are logged in to Acrobat Sign when the agreement is opened. This can eliminate some of the friction for your internal signers.
To allow your users to skip the agreement opening authentication if logged in:
- Navigate to Account Settings > Send Settings > Signer Identification Options.
- Enable Don’t challenge the signer to re-authenticate if they are already logged in to Acrobat Sign.
- Save the page configuration.
Audit report changes
When any of the Enforce identity authentication options are enabled, the audit report explicitly logs every authentication in the audit report, and to a lesser degree, in the activity panel of the agreement.
Things to keep in mind...
- Enforced Identity works with authenticated self-signing.
- Enforced identity authentication works with digital and electronic signature fields.
- Enforced authentication does not apply when only a Stamp is used as a signature.