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
-
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
Content Protection enables authentication-based security to view the contents of completed agreements.
Overview
Content Protection applies an authentication-based security layer to view an agreement after it has been completed. This protection applies to all agreements regardless of how they were created (through the user interface, REST API, SOAP API, Send in Bulk, Custom Workflows, etc. Every agreement is in scope.)
Protection can be applied passively by enabling the inherited protection method. When enabled, all agreements sent from the enabled group must pass an authentication challenge before they can be viewed.
Additionally, senders can be empowered to explicitly configure their agreement to apply protection or not. This method embeds the configuration into the metadata of the agreement and can not be modified once the agreement is sent.
When trying to view an agreement with protection enabled, the participant is challenged to authenticate, either by using the original authentication method or optionally using a one-time password delivered to the participant's email address.
Supported authentication types:
- Adobe Acrobat Sign authentication
- Password
- Phone authorization
- OTP via Email (OTPvEM)
- Knowledge-Based Authentication (KBA) (with required name enabled)
Unsupported authentication types:
- None (Email)
- Knowledge-Based Authentication (KBA) (without required name enabled)
- Government ID
- Digital Identity
Unsupported authentication methods use the OTP via Email fallback method when enabled.
How it's used
There are two methods by which content protection can be applied to an agreement:
- Inherited protection allows the group-level setting (whether explicitly set or inherited from the account) to dictate the content protection value for all agreements sent from the group. Changing the setting immediately impacts if viewing the agreement is subject to the content protection authentication challenge.
- Embedded protection requires the user to explicitly choose if content protection should be embedded into the transaction metadata. The protection values are immutable once the agreement is sent. Inherited protection values don't impact agreements that have embedded the content protection defined.
Both application methods have controls to discretely enable or disable internal and external participants.
- Internal participants are defined as any participant (as identified by their email) who is within the authority of the Acrobat Sign account. If the email is on your user list, they are internal.
- External participants include every email that isn't an internal participant.
The authentication method used to grant access to view the agreement is based on the original authentication method used during the signature process.
To overcome issues like participants with no authentication method, unsupported authentication methods, and CC'd parties, there is an option to enable the Email One-Time Password via Email authentication method as an alternative vehicle to grant access. This option requires the participant to access their email, retrieve a passcode, and enter it in the challenge field.
If content protection is enabled, and the alternative Email One Time Password authentication method is not enabled, participants that use KBA, Government ID, or don't have an authentication method will receive a message that they cannot access the agreement.
This includes CC'd parties and anyone to whom the agreement is shared.
For recipients with a defined signature authentication method, the experience changes depending on that method:
- Password, Phone, and Acrobat Sign authentication methods use the same method (leveraging the same password and phone number).
- OTP via Email, Knowledge-Based Authentication, and Government ID leverage the OTP via Email method (provided it's enabled).
- If OTP via Email is disabled, then an error is presented, and the participant is denied a view of the agreement.
Configuration
Availability:
Content Protection is available for enterprise license plans only.
Configuration scope:
The feature can be enabled at the account and group levels.
The controls for this feature can be assessed by navigating to Account Settings > Send Settings > Content Protection
The configurable options are:
Best practices
It is strongly recommended that you enable One-Time Password via Email authentication if you intend to use content protection. There are agreement participants who don't have authentication methods. This free service allows an option for them to view the agreement with very little demand on their time or understanding of the process.
Most enterprise customers can likely benefit from the inherited content protection method.
- Vetting the participant's access to the agreement, even when no authentication was initially required, is generally a good idea. It offers little friction to the participant and provides security when a viewing link is accidentally forwarded in an email.
- Inherited protection also has the advantage of being dynamically applied, meaning if something breaks a downstream process, the setting can be turned off, and there's no persistent damage.
- Customers who employ authentication methods like password and phone authentication must contend with the password and phone number long term. Being able to turn off content protection provides a method of access when phone numbers change, or passwords are forgotten.
Requiring a sender to configure the embedded content protection should be carefully considered. There are certainly some processes that demand this granular level of control, but keep in mind that:
- Every agreement sent from the group must be configured explicitly by the sender; this adds process and invites eventual human error.
- There is no option to define the default values. Senders must explicitly configure the enabled drop-downs.
- Embedded content protection has no method to be changed after the agreement is sent.
- Using phone and password authentication methods presents the opportunity to be locked out from viewing the agreement if the password is lost or the phone number is changed.