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
-
Account/Group Settings
- Settings Overview
-
Global Settings
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- 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
- Set a default time zone
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- Healthcare customer
- Account Setup
-
Signature Preferences
- Well formatted signatures
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow signers to print and place a written signature
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Digital Signatures
- Electronic Seals
- Digital Identity
-
Report Settings
- Security Settings
-
Send settings
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- CCs
- Recipient Agreement Access
- Field flattening
- Modify Agreements
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Signing order
- Liquid mode
- Bio-Pharma Settings
- Notarization Settings
- Payments Integration
- SAML Settings
- 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
- 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
The Adobe Acrobat Sign Technical Notifications are ordered below, with the current update at the top, and rolling back in time as you scroll down the page.
The Technical Notifications page is updated regularly with new information, making its content highly dynamic. While localized versions are available, the translation process may cause slight differences from the authoritative US English version. Always refer first to the US English page for the most accurate and up-to-date information.
[Important] The next Adobe Acrobat Sign release is scheduled for March 18, 2025
Feature Release: Adobe Acrobat Sign – February 11th Release Completed
The release was completed to all shards with no downtime to any services.
First Reported: September 2024 - Updated February 2025 |
Current |
---|
To improve Adobe Acrobat Sign service security and robustness, we will start to roll out network changes to include a web application firewall (WAF) in February 2025. These changes will route traffic into Acrobat Sign application servers through the WAF service. This routing will be invisible to most customers. Usage will not interfere with access to Acrobat Sign from any Adobe clients or integrations.
Action Required
None.
This change will not affect customer integrations, as the Acrobat Sign API and API domain names will not change. This solution is backward compatible with the published IP ranges.
Customers who have updated their security devices don't need to revert or make any other changes.
The current update schedule is:
- Production Sandbox updates February 24, 2025.
- Production shards: IN1, JP1, AU1, and SG1 will update March 3, 2025.
- Production shards: NA2, NA3, and EU2 will update March 6, 2025.
- Production shards: NA1, NA4, and EU1 will update March 11, 2025.
First Reported: June 2018 - Updated May 2024 |
Current |
---|
Action Required
All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.
First Reported: June 2018 - Updated May 2024 |
Current |
---|
Action Required
All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.
First Reported: September 2024 - Updated February 2025 |
Current |
---|
The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads.
The Sandbox environment will be updated in the March 2025 release.
The Production environments will be updated in the April release.
The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload.
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
This update only applies to the Send (Request e-signatures) page. Structured Self-signing workflows are not yet included.
First Reported: March 2024 - Updated January 2025 |
Current |
---|
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
First Reported: June 2024 - Updated January 2025 |
Current |
---|
First Reported: March 2024 - Updated February 2025 |
Current |
---|
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
First Reported: March 2024 - Updated February 2025 |
Current |
---|
This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.
First Reported: November 2024 - Updated: January 2025 |
Current |
---|
First Reported: February 2025 |
Current |
---|
First Reported: February 2025 |
Current |
---|
First Reported: February 2025 |
Current |
---|
First Reported: September 2024 |
Current |
---|
The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads.
The Sandbox environment will be updated in the March 2025 release.
The Production environments will be updated in the April release.
The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload.
First Reported: September 2024 |
Current |
---|
Action Required
All customers using the API must update their APIs to utilize the version 6 endpoints as soon as possible to ensure uninterrupted availability.
First Reported: September 2022 - Updated March 2024 |
Current |
---|
First Reported: May 2024 |
Current |
---|
Additional Resources
- Community forums
- Weekly Training - Weekly Webinar covering training topics for new users and administrators
- Adobe Sign Innovation Series - Monthly Webinar covering the hottest topics in the Adobe Sign space
First Reported: December 2024 |
Removed from Current list: February 2025 |
---|
Adobe Acrobat Sign will rotate the Adobe Acrobat Sign SSL Certificate on January 22, 2025.
In addition, a new SSL certificate is being deployed to support the WAF network changes being made in January 2025. This new certificate directly impacts access to the Acrobat Sign service and must be installed before the WAF goes online.
Action Required
- Every customer account that explicitly secures network activity must include the new WAF SSL certificate in its list of stored certificates.
- If you have custom-built integrations with Acrobat Sign using either the SOAP or REST APIs and if any of these integrations have ‘pinned’ the existing public key, no other action is required.
- If you are using Acrobat Sign’s SSL certificates for SSO, or if you’re pinning the certificate itself (or using other methods), you can find the new Acrobat Sign SSL certificates in the Adobe Acrobat Sign System Requirements.
- If your SSO configuration supports multiple public certs/chains, you can add the new certificates now and remove the old public cert/chain from your configuration after the January switch.
- If your SSO does not support multiple public certs/chains, you will need to sync your SSL switch with Acrobat Sign on January 22, 2025.
The new SSL certificates will be active on January 22, 2025.
First Reported: November 2024 |
Removed from Current list: February 2025 |
---|
The new recipient experience contains signing improvements for both desktop and mobile web browsers. This new experience is being rolled out over the first months of 2025 but will be available in the Sandbox environment in the first week of December 2024.
First Reported: August 2024 |
Removed from Current list: January 2025 |
---|
First Reported: September 2024 |
Removed from Current list: January 2025 |
---|
First Reported: November 2024 |
Removed from Current list: January 2025 |
---|
With the November 2024 release, the editable labels in the Custom Workflow Designer have been limited to 100 characters. This limit is evaluated when the workflow is created or updated.
Preexisting workflows that have labels over 100 characters can still be sent successfully, but if the workflow is updated, the label must be reduced to 100 characters or less before it can be saved. Offending labels are outlined in red for easy discovery.
New workflows will warn about the label limit before they are saved.
Action Required
It is recommended that admins with control over custom workflows open and review each workflow to ensure that they don't have errors on their template.
Archived Notifications
Listed by the date when the notice was removed from the current notice list, most recent to oldest.