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
- Add, edit, and review active users
- Create function-focused users
- Review users who haven't completed verification
- 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
- Transaction Footer
- 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
- Restart agreement workflow
- 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
- Apply Adaptive Signature Draw scaling
- 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
- CCs
- 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
- Restrict access to shared agreemets
- 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
- System Requirements and Limitations
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
- Send (Compose) page
- Overview of landmarks and features
- Group selector
- Adding files and templates
- Agreement name
- Global Message
- Completion Deadline
- Reminders
- Password protect the PDF
- Signature type
- Locale for the recipient
- Recipient signature order/flow
- Recipient roles
- Recipient authentication
- Private message for the recipient
- Recipient agreement access
- CC'd parties
- Identity check
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
- Send (Compose) page
- Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Field types
- Common field types
- E-signature fields
- Initials field
- Recipient name field
- Recipient email field
- Date of signing field
- Text field
- Date field
- Number field
- Checkbox
- Radio button
- Drop-down menu
- Link overlay
- Payment field
- Attachments
- Participation stamp
- Transaction number
- Image
- Company
- Title
- Stamp
- Field content appearance
- Field validations
- Masked fields values
- Setting show/hide conditions
- Calculated fields
- Field types
- 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
- Sandbox
Support and Troubleshooting
Adobe Acrobat Sign release schedule and prerelease documentation
Adobe Acrobat Sign rolls out at least three updates per year, categorized as major or minor releases. Additional minor updates may be introduced as needed to address system or customer issues.
- Major Releases bring significant updates, new features, and multiple enhancements.
- Minor Releases focus on smaller improvements and user experience tweaks. These occur between major updates, typically one to two times per cycle.
To prevent disruptions, new features are disabled by default and must be manually enabled by an account or group admin.
For Health and Life Sciences customers requiring compliance validation, Acrobat Sign partners with a third-party vendor to provide a validation package for every major release containing features to minimize your risk factor.
This Prerelease Notes page is regularly updated as new information becomes available, so its content is relatively dynamic.
While this page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.
For the most accurate and up-to-date information, we recommend referring only to the US English page.
Adobe Acrobat Sign follows a structured schedule for publishing release notes and documentation updates:
8 Weeks Before Production Release
- The prerelease page publishes a summary of expected features and updates, typically four weeks before the Sandbox launch.
- Any feature changes after this point are noted in the Errata section.
- Resolved issues are not included at this stage.
4 Weeks Before Production Release (Sandbox Launch)
- The prerelease page is updated with detailed documentation on new and updated features.
- Links to prerelease support documentation (available in US English only) are added as needed.
- The initial Resolved issues section is published, with ongoing updates over the next four weeks.
Launch Day
- The official release notes are updated with final feature details and links to production support documentation.
- The prerelease page is refreshed to highlight the next release cycle.
- Documentation is published after release verification in the live system, typically after 7 pm PT, though complex updates may take longer.
- The final Resolved issues list is added to the US English release notes, with localized versions updated later.
Government Cloud Release
- The Government Cloud environment typically updates between two days and several weeks after the production release, as some features may require additional evaluation before deployment.
Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).
When the release is published, the new pages will also be published, and links will properly resolve to their production URLs.
Sandbox availability
Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.
- The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
- Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
- The Sandbox environment uses the same status page and outage procedures as the regular Production environment.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Sandbox deployment: April 22, 2025
Production deployment: May 20, 2025
GovCloud deployment: May 22, 2025
Improved Functionality
- Improve recipient data security by configuring recipients with restricted access - The Restricted Access to Agreements feature enhances privacy by preventing agreements from being attached to a recipient's Acrobat Sign userID (if they have one). When enabled, the Recipient Agreement Access option appears in the Recipient Settings section on the Compose page. Administrators can configure this setting to enable it by default and make it editable by senders.
When a recipient is marked as restricted, they are treated as if they do not have an active Acrobat Sign user account. As a consequence, the agreement does not appear on their Manage page. This prevents accidental data leakage due to group-level sharing relationships.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the Restricted access to agreements configuration controls >
Updated Request Signature documentation >
- API support for the Restricted Access to Agreements feature - Organizations that use the API to compose and send agreements can now use the Restricted Access to Agreements feature as part of their recipient configuration. The API implementation of this feature has one experiential difference with regards to when the document can be accessed if the 2nd factor authentication type is set to "None":
- Within the Acrobat Sign interface, the recipient may not View or Download the agreement until it is signed. Even if no 2nd factor authentication is configured, access to the agreement is disabled by suppressing the View and Download actions.
- When using the API, the agreement may be viewed and downloaded with the token after authentication is passed. In the case where no 2nd factor authentication is configured, the agreement can be viewed or downloaded before it is signed.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Expanded Country support for Phone Authentication – Phone Authentication and agreement delivery via SMS now support these additional Countries and Country Phone codes:
- Falkland Islands (Malvinas) (+500)
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Experience Changes
- Webform support case submission now requires login for legacy enterprise accounts - Users with legacy enterprise accounts must now sign in with their Acrobat Sign credentials before using the online webform to submit a support case. This authentication step ensures the case is linked to the correct account and routed to the appropriate support team.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; Not editable
Review the new process >
REST API/Webhook Updates
The below updates are presented in the prerelease notes for disclosure purposes. Full documentation for API and Webhook updates can be found in the Acrobat Sign developer documentation when the version update is delivered to the production servers.
- GET /agreements API Now Served from a Microservice - The GET /agreements endpoint is migrating from the Acrobat Sign core application to a dedicated microservice. As part of this transition, search requests will retrieve data from the search service (secondary storage) instead of the primary database. This change enhances service stability and prevents atypical API calls from affecting the Acrobat Sign experience.
- The maximum page size for the GET /agreements call is now 500 agreements per request. Historically, the search service did not fetch more than 100 agreements per page. If more agreements are required, multiple queries with a narrower scope may be necessary.
- Since searches now occur in secondary storage, minor additional latency may be observed when calling the GET /agreements endpoint.
- Update to API throttling - After the May 2025 release, new API throttling rules will be applied:
- When high overall system load is detected, Acrobat Sign will throttle API requests across the entire system.
- When high-usage customers are identified as contributing to overall system slowness, Acrobat Sign will throttle API requests specifically for that customer.
When an API request is throttled, it will be rejected with a 429 HTTP status code, along with the following:
Response Body
{ "code":"THROTTLING_HIGH_SYSTEM_LOAD", "message":"Acrobat Sign system is experiencing high overall load, due to which subset of the requests are being throttled. Please try again in <wait_time_in_seconds> seconds.", "retryAfter": <wait_time_in_seconds> }
Response Header
X-Throttling-Reason : "high-system-load" Retry-After : <wait_time_in_seconds>
Upon receiving the above response, you can use the Retry-After header or the retryAfter in the response body to determine when to attempt the request again.
Retry Penalty
For all new accounts created after the May 2025 release, a penalty will be applied if the account does not adhere to the specified retry time interval.
If the same request is attempted again within this interval, the request will be throttled again, and the retry time interval will be reset.
Release errata - Elements added
Below are items that have been added to this release since the initial publishing of the pre-release notes.
- Improve recipient data security by configuring recipients with restricted access - The Restricted Access to Agreements feature enhances privacy by preventing agreements from being attached to a recipient's Acrobat Sign userID (if they have one). When enabled, the Recipient Agreement Access option appears in the Recipient Settings section on the Compose page. Administrators can configure this setting to enable it by default and make it editable by senders.
When a recipient is marked as restricted, they are treated as if they do not have an active Acrobat Sign user account. As a consequence, the agreement does not appear on their Manage page. This prevents accidental data leakage due to group-level sharing relationships.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the Restricted access to agreements configuration controls >
Updated Request Signature documentation >
Release errata - Elements removed
Below are the line items that previously were announced as part of this release, but have since slipped to a later release date.
- The modern Request Signature environment has become the only experience when creating a new agreement. All existing Commercial accounts have been switched to the modern environment -
- Administrators no longer have the option to enable the classic experience through the admin menu.
- Customers using the Notarize integration will not be affected by this change.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; Not configurable
Resolved Issues
Issue | Description |
---|---|
4477748 | Summary: Users are unable to create OAUTH ACCESS-TOKEN due to a malformed domain in the API call. |
Fix: The domain list for the Swagger controller has been updated. | |
4480357 | Summary: Keyboard handling within the "Start from library" dialog is not working properly when screen readers are running |
Fix: Multiple fixes to screenreader navigation to ensure all pages start are read as expected. | |
4498103 | Summary: Incorrect Role Assignment in Bulk Send Feature. Always assigning a "Signer" role when adding yourself as the last recipient. |
Fix: Removed options for other roles for the sender when they are added to the last participant position as it is intended that the sender will always be a signer. | |
4501417 | Summary: Placing a seal signature field with a field template triggers an error that blocks further authoring. |
Fix: Added code to process text tag "signer1" text tag elements. | |
4506667 | Summary: If a Sender needs a Webform's First signer to verify their email, Webhook notifications are delayed until the first signer verifies the email. If the first signer's email is bounced, the webhook notification is delayed for 2 hrs due to an expectation that the documentsInfo parameter will be filled. |
Fix: If the Sender needs a Webform's First signer to verify email, documentsInfo will not be populated in the webhook notification payload for the Agreement events (until first signer verifies the email). If the first signer's email is bounced, documentsInfo will not be populated in the webhook notification payload for the Agreement events. | |
4511940 | Summary: The default font size of a multi-line text field does not adjust to the screen size, so the text is cut off while signing an agreement using a mobile phone. |
Fix: Multi-line text field can no longer override the base class method. | |
4513457 | Summary: Issue with parsing JSON when group name contains double quote character(s) in the group name. |
Fix: Improved parsing code for group names to manage double quotes. | |
4515610 | Summary: Calculated field values are changed when the webform is sent to additional Participants due to how floating-point numbers are handled on the backend and front end. |
Fix: Changing the implementation on the backend to use BigDecimal as the type for numbers | |
4516504 | Summary: When you create a reusable template and use the New Experience view, the checkbox and radio buttons have pink borders instead of black borders due to the color value being truncated. |
Fix: The hex value has been corrected to hold the correct value. | |
4520149 | Summary: Some agreements do not update their status after being signed due to a rare race condition when setting the next_to_sign flag. |
Fix: Additional logging has been added to catch this condition and resolve it before recipients interact with the agreement. | |
4521246 | Summary: Template sharing within multiple groups is not working and throws errors when Advanced Account Sharing is enabled, and the sending process starts from the Home page. |
Fix: The template picker sourced from the Home page has been updated to properly fetch the shared template. |
Adobe Acrobat Sign Release 16.1
Sandbox deployment: June 24, 2025
Production deployment: July 22, 2025
GovCloud deployment: July 24, 2025
Improved Functionality
- Improved control over group-based sharing - Organizations using advanced account sharing can now optionally restrict the shared view of their agreements to only those agreements sent from the user's group. Agreements sent to a user from an external group will be filtered out to protect potentially private user communications that would be inappropriate to share generally. This filter only applies to the group-level shares (sharing a group to another group or user), and does not apply to user-based shared (sharing a user to a group or another user).
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
- Acrobat Sign for Government gets a mobile-first upgrade - Government users can now access the modern interface, designed to simplify signing on mobile devices through an easy-to-configure, form field-only interface.
Available environments: Government | Available tiers of service: Acrobat Sign for Government | Configuration scope: Account or Group
- Custom Email Templates available for Acrobat Sign for Government - Customers on the GovCloud platform can now create custom email templates for their agreement notifications and reminders.
Available environments: Government | Available tiers of service: Acrobat Sign for Government | Configuration scope: Account or Group
- Use WhatsApp to send agreement links directly to a recipient's mobile device - The WhatsApp integration in Acrobat Sign has been expanded to include the option to send agreement notification and reminder links directly to a recipient's WhatsApp enabled device.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
- Auto-tagging support for PDF accessibility compliance - Acrobat Sign now identifies untagged and scanned PDFs and applies accessibility tagging automatically, preserving the tag tree from sending through signing. This reduces manual burden and supports compliance with WCAG and Section 508 standards.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Native PDF/A support for long-term document preservation - Acrobat Sign now supports conversion, validation, and export of documents in PDF/A format (ISO 19005), helping organizations meet stringent archiving standards and regulatory requirements. Documents retain their PDF/A conformity across the full agreement lifecycle—upload, signing, and storage.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- New Identity Providers (IdPs) Added to Acrobat Sign - Acrobat Sign is expanding its list of supported identity providers (IdPs) to enhance the recipient's authentication options. The following new IdPs are now available:
- Australia Post ID
- eID Easy
These additions expand Acrobat Sign's compatibility with global identity verification standards, supporting seamless and secure authentication across multiple industries.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Fast-track your template migration to Acrobat Sign with automated template conversion - The new template migration feature helps account admins quickly bring their templates from other services into Acrobat Sign. Upload a template ZIP file, convert it automatically, and review results in the authoring environment—no technical expertise needed.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
Experience Changes
- Add users directly in Acrobat Sign (VIP only) - VIP-licensed accounts can now add and configure users directly from the Users tab—no need to navigate to the Adobe Admin Console.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; not configurable
- Admin Console Role assignment now available in Acrobat Sign - To streamline setup, Acrobat Sign now allows account admins to assign key Admin Console roles—Product and Support Admin—without leaving the product interface.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- Improved digital signature application - The process for applying a cloud-based digital signature has been refined to reduce the number of interactions the signer must complete when applying their signature certificate.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: The new process is enabled by default, not configurable.
- The modern Request Signature environment has become the only experience when creating a new agreement. All existing Commercial accounts have been switched to the modern environment -
- Administrators no longer have the option to enable the classic experience through the admin menu.
- Customers using the Notarize integration will not be affected by this change.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; Not configurable
- Easier HIPAA onboarding through in-product guidance - Organizations subject to HIPAA can now begin the enablement process within Acrobat Sign via a new self-service workflow. The system sends an automated request to Support and tracks progress based on the BAA signature and system configuration.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account
- Streamlined admin setup from the Home Page - Acrobat Sign introduces a new Account Management section to help account admins quickly access key configuration tools. Add users, organize groups, connect integrations, and migrate templates directly from the Home Page—no digging required.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
REST API/Webhook Updates
The below updates are presented in the prerelease notes for disclosure purposes. Full documentation for API and Webhook updates can be found in the Acrobat Sign developer documentation when the version update is delivered to the production servers.
- OAuth 2.0 capabilities have been extended to group-level administrators - Group-level admins now have the authority to use OAuth 2.0 tokens.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Release errata
There are no items that have slipped from this release as of this time.
The September 2025 release is a minor release containing updates, and fixes for customer-reported issues.
- Sandbox release: August 19, 2025
- Production release: September 16, 2025
- GovCloud release: September 18, 2025
The October 2025 release is a major release containing features, updates, and fixes for customer-reported issues.
- Sandbox release: September 15, 2025
- Production release: October 7, 2025
- GovCloud release: October 9, 2025