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
Enterprise accounts have the option to configure individual agreement recipients to include one or more CC'd parties who are notified about the agreement at the same time as the recipient.
This recipient-bound CC can be helpful in situations such as:
- An internal party must review the agreement as a non-involved participant.
- A recipient wants to leverage an assistant to notify them when the agreement demands their attention.
- A specific step in the signature process demands heightened attention.
The CC'd party does not need to have the same domain as the recipient, allowing for broader notifications of the agreement's progress.
Availability:
The feature to include CC'd party notifications when a recipient is notified is available for Acrobat Sign Solutions license plans in the commercial environment only.
Configuration scope:
The feature can be enabled at the account and group levels.
When the feature is enabled, the recipient record (on the Send page) will include a CCs option in the configurable Recipient settings section of the recipient record.
- If the CCs field isn't configured, the value shows as None.
- If one email value is added as a CC for the recipient, the email address of the CC'd party is displayed.
- If more than one email value is configured for the recipient, the CC value shows a numerical value describing the number of configured CC'd parties.
When the feature is not enabled, the Recipient settings section does not have the CCs option exposed in any way.
Adding CC'd parties to a recipient record does not replace the function of the global CC field. Both can be configured.
The difference between the two is when the CC'd party is notified.
- The Global CC only notifies the CC'd parties when the agreement is completed.
- The recipient-aligned CC party is notified when the recipient is notified as part of the signature cycle.
- Note that the recipient-aligned CC'd party is only associated with one individual recipient record. If one person is configured to interact with the agreement multiple times (using multiple recipient records), each recipient record for that person must be configured (or not, as desired). Acrobat Sign does not assume that if the same email is used in multiple recipient records, the same CC notification rules apply to all records.
If the CCd party is expected to review the agreement's content, they must have an active Acrobat Sign account.
When the agreement's signature cycle moves to a new recipient, any recipient-related CC'd parties are notified concurrently with the recipient.
The CC'd party receives an email indicating they have been included in an agreement as a CC'd party. A link is provided for the CC'd party to view the agreement from their Acrobat Sign account. Access for CC'd parties is read-only. If the CC'd party does not have an Acrobat Sign account, they cannot view the agreement.
Other settings to consider
Modifying/Delegating the recipient
There currently is no method to alter the recipient-related CC'd party after the agreement is sent. Modifying the recipient from the Manage page or delegating the signature authority through the recipient's action does not allow the recipient-related CC'd party to be edited.
Limited Document Visibility
Limited Document Visibility (LDV) works as expected.
LDV is designed to expose only the files of an agreement that contain at least one field for the recipient to interact with.
Because the CC'd party isn't the recipient and fields cannot be assigned to them, no pages will be available for the CC'd party to view. An error is triggered indicating this condition.
The exception to this is when the LDV settings enable the option for CC'd parties in the sender's account to view all files. If the sender has a CC'd party with an active Acrobat Sign account, that CC'd party will be able to view the agreement files.
Audit Report and Activity Log
If Audit Reports are configured to show viewing of the agreement emails, the view events are logged for the CC'd party in both the Audit Report and the Activity Log, even if they are denied access to view the agreement itself.