What's New
Get Started
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
- 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
-
Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- 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
- 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
- Send (Compose) page
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
-
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
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable 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
- Agreement data extraction
- Agreement notifications
- Agreement generation
- Custom Send workflows
- Share users and agreements
Integrate with other products
- 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
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.
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.
- One-Time Password via Email - Single-factor authentication; best for internal recipients or external recipients that sign with a TSP-backed digital signature.
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.
- One-Time Password via Email - A password is sent to the recipient's email address that must be entered to gain access to interact with the agreement.
Because the password is sent to the same email address as the recipient's email notification, this authentication method only serves as a single-factor authentication method. This may be acceptable for some use cases (such as internal recipient workflows). It's recommended to pair this method with cloud-based digital signatures when a more robust authentication assurance is required.
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.