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).
The new pages will be published when the release is 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.
Adobe Acrobat Sign release v18.0
Sandbox deployment: November 17, 2026
Production deployment: January 12, 2027
GovCloud deployment: January 19, 2027
Improved Functionality
- Inline Document Editing During Agreement Authoring – Edit document text directly in the authoring experience
Senders can edit document text directly in the authoring environment without downloading and re-uploading the file. The Edit Document option preserves existing fields and agreement configuration, reducing disruption during pre-send updates. Editing is available only while the agreement is in a draft state and is not available after the agreement is sent.
In-line document editing is to be released on a rolling schedule, as referenced in the technical notification.
This feature is disabled by default for all users in supported accounts. Account and group admins can enable document editing through the Send Settings.
In-line document editing is not available in Acrobat Sign for Government or for accounts using the legacy user management system.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions ETLA customer accounts | Configuration scope: Account and Group; Disabled by default
Enable or disable in-line document editing >
How to edit text during field authoring >
- Automatic PDF accessibility tagging – Improve accessibility for untagged documents
Account and group administrators can enable automatic accessibility tagging for eligible untagged PDFs sent through Request Signature. The feature adds basic document structure, including headings and reading order, to improve navigation for recipients using assistive technologies.
Available environments: Commercial, Sandbox | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group; Disabled by default
Enable automatic PDF accessibility tagging
- Schedule agreements to send later
Senders can prepare agreements in advance and schedule them to be sent automatically at a selected date and time, from 30 minutes to 30 days ahead. Scheduled agreements remain available under Drafts on the Manage page, where senders can edit, reschedule, or cancel them before delivery.
Scheduled Send is supported in the modern Request Signatures experience and through the REST API v6. It is not supported in Classic Request Signature, Send in Bulk, or Custom Workflows.
Scheduled Send is enabled by default, with no customer-facing administrator control to disable it. Administrators must contact Adobe Support to request account-level disablement. Disabling the feature does not prevent previously scheduled agreements from being sent.
Additional details about disabling Scheduled Send and managing existing scheduled agreements will be provided in the Technical Notifications documentation.
Available environments: Commercial, Sandbox, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Adobe Support; Enabled by default
- Workflow-level reminders – Configure reminder schedules in the Workflow Designer
Workflow creators can now configure reminder frequency directly in the Workflow Designer, allowing agreements sent through a workflow to use a predefined reminder schedule. This reduces manual setup and helps ensure participants receive consistent follow-up. Senders can adjust reminders for individual agreements when using the custom Compose page.
Workflow-level reminders are not supported through the classic Workflow Designer. Administrators must enable Global Settings > New custom workflow experience to use this feature.
Available environments: Commercial, Sandbox, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Policy-based digital signatures – Control which digital certificates recipients can use
Administrators can enable predefined digital signature policies at the account or group level to support specific regulatory requirements. Senders can apply an approved policy to individual recipients, restricting which cloud-based digital signature certificates they can use to sign an agreement.
Administrators can allow senders to select a policy or require them to choose one whenever a recipient must apply a digital signature. Policies restrict the available signing providers and certificates to those that meet the selected requirements.
Note: Signature policies apply only to Cloud Signatures. They do not apply to the Download and Sign with Acrobat workflow.
Available environments: Commercial, Sandbox, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group; Disabled by default
- Configurable password complexity – Define custom password requirements for agreements
Administrators can now define custom password requirements for agreements, including minimum length, required character types, and a minimum number of character types. This provides greater flexibility to align password protection with organizational security policies.
The new Custom option under Security Settings > Document Password Strength supports passwords from 4 to 32 characters and applies to signer authentication, signed agreement PDF protection, and Signer Identity Reports. Existing password-strength presets remain available and unchanged. User login passwords are unaffected.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Define the complexity of user-applied passwords
- Retention policy email reminders – Notify senders before agreements are permanently deleted
Administrators can enable automated email reminders that notify senders before completed agreements are permanently deleted under their organization's retention policy. Reminders are sent 14 and 7 days before deletion and include a link to view, print, or download the agreement, giving senders an opportunity to preserve important records.
For retention periods shorter than seven days, a single reminder is sent immediately. Extremely short retention periods may not generate reminders. Notifications do not delay or prevent agreement deletion.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- New Review & Send experience – Review agreements before sending
Senders can review agreements before sending them for signature. The new Review & Send step provides a read-only document preview, lets senders inspect fields assigned to individual recipients, and offers desktop, tablet, and mobile signing previews. Senders can return to document preparation to make corrections before sending.- Administrators can configure the review step as optional or mandatory for eligible accounts.
- The feature is available in the modern sending experience for supported accounts as it is gradually enabled. The review preview does not simulate the complete signing process.
Available environments: Commercial (VIP Licenses only; phased rollout), Sandbox | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group; Disabled by default
- Customize suggested field detection – Control which field types are suggested during document preparation
Senders can choose which types of automatically detected form fields appear as suggestions when preparing agreements and library templates. They can apply their selections to the current document or save them as personal defaults for future documents, reducing unnecessary field placement and cleanup.
Available environments: Commercial (VIP only; phased rollout), Sandbox | Available tiers of service: Acrobat Sign Solutions | Configuration scope: User preferences
- Formula Builder in modern authoring – Create calculated fields and custom validation rules without switching to Classic
Senders can now use the guided Formula Builder in the modern authoring experience to create calculated fields and custom formula-based validation rules. The builder provides a searchable list of fields, keywords, and functions, with syntax checking and error feedback to help senders create valid expressions without switching to Classic authoring.
The available functions match those supported in the Classic Formula Builder. Existing formula evaluation and the recipient signing experience remain unchanged.
Available environments: Commercial, Sandbox | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Available by default
- Recipient delivery status in data exports – Identify bounced recipient emails across agreements
Reports users can now include recipient email delivery status in CSV data exports. The new Recipient Delivery Status field identifies delivered, bounced, and not-yet-initiated initial invitation emails, helping administrators identify delivery failures across agreements without reviewing each agreement individually.- The field is available through the existing Column Chooser in modern Reporting.
- Delivery status data is not available for recipient records created before the 18.0 deployment.
Available environments: Commercial, Sandbox | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Available by default
- Acrobat Sign MCP in Adobe connectors – Work with agreements from supported AI assistants
Users can access Adobe Acrobat Sign capabilities from supported Adobe connectors to start agreement workflows, check agreement status, and send reminders without leaving the AI assistant where they are working.
Sending remains under user control. Where supported, users review the agreement in the Acrobat Sign experience or explicitly confirm the action before it is sent. Assistant-composed sending is not included in this release.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration
- Expanded digital identity provider support – Additional options for signer identity verification
Adobe Acrobat Sign is expanding its Digital Identity Gateway integrations with additional identity providers. These integrations give eligible organizations more options for verifying recipient identities during the signing process.
Provider availability and activation requirements may vary by organization. Additional identity providers include:- DAON ID Verification
- Verimi
Available environments: Commercial, Sandbox | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Additional cloud signature providers – Use more regional trust service providers for digital signatures
Adobe Acrobat Sign adds support for additional cloud signature providers, giving organizations and signers more options for applying certificate-based digital signatures through supported regional trust services. New providers in Release 18.0:- Digidentity: v1 migration has been validated in Sandbox.
- Evrotrust: Complete onboarding.
- Rubrix: TEST service
- Savis (Vietnam)
- Telecom Italia Trust: DCCR-6258.
- TSP for Bangladesh: DCCR-5409.
- TSP for Gov.br (Brazil)
Available environments: Commercial; Sandbox | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Improved user migration with customer-managed encryption keys
User migration now supports accounts that use customer-managed encryption keys (BYOK). When a user moves between accounts and either account uses BYOK, Acrobat Sign re-encrypts affected agreements as needed so the migrated user retains access to their existing agreements.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account
Experience Changes
- User migration between accounts with customer-managed encryption – Preserve access to agreements after migration
Adobe Acrobat Sign now supports migrating users between accounts when customer-managed encryption is involved without causing applicable agreements to become inaccessible because they were encrypted using the source account's key.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Available by default
- Saved signatures in the modern e-signing experience – Reuse saved signatures while signing
Recipients using eligible modern e-signing workflows can now use a previously saved signature instead of drawing or uploading it again. When permitted by the sending account, eligible recipients can also save a newly drawn or uploaded signature for future agreements.
Available environments: Commercial, Sandbox, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Existing Signature Preferences configuration
- Cloud Signatures supported in the modern recipient experience - Recipients can now apply cloud-based digital signatures using the modern recipient experience. The updated experience supports the Cloud Signature provider selection, authentication, certificate selection, signature appearance, and signing process while providing the accessibility and usability improvements of the modern signing experience.
Digital signatures that require Download and Sign with Acrobat continue to use the classic recipient experience.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default
- Sign multiple agreements with electronic signatures – Complete multiple signing tasks in one session
Signers can now select multiple agreements from the Manage page, review them together, and apply their saved electronic signature to eligible agreements in one session. This reduces repetitive signing steps for users who regularly process large numbers of agreements.
Signers must review each agreement before signing. Agreements requiring additional authentication or manual field completion are not eligible for bulk electronic signing.
Available environments: Commercial, Sandbox, Government | Available tiers of service: Adobe Acrobat Sign | Configuration scope: Account-level (Adobe Support); Enabled by default
- Modern e-signing experience supports custom workflows
Agreements created using custom workflows can now open in the modern e-signing experience, providing recipients with a more accessible and streamlined signing interface. Supported workflows include sequential, parallel, hybrid, and recipient-group routing.
Agreements that use other features not yet supported in the modern experience continue to open in the classic signing experience.
No additional configuration is required. Eligible agreements automatically use the modern experience when it is enabled for the account.
Available environments: Commercial, Sandbox, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default
- Improved integration discovery – Find integration options where you already work
Acrobat Sign now surfaces integration options at more useful points in the workflow. Eligible users see a Microsoft 365 recommendation on the post-send page during their first three sends, while account administrators receive a one-time integration email and see clearer integration messaging on the Home page.
The Microsoft 365 recommendation opens the Microsoft AppSource listing. The administrator email links directly to the Integrations Hub.
Available environments: Commercial, Sandbox, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by Default
- Modern Custom Workflow Designer becomes the default
All Commercial and Government accounts are automatically switched to the modern Custom Workflow Designer experience. Admin controls remain available for customers who need to temporarily fall back to the classic experience.
Full removal of classic fallback controls is planned for a later release.
Available environments: Commercial, Sandbox, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Completion notifications for delegated recipients
Recipients who delegate their participation in an agreement now receive the completed agreement notification even when another participant completes the delegated action. This makes completion notifications consistent across single-recipient and multi-recipient agreements.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Sender email suggestions in recipient fields
When adding recipients to an agreement, senders can now select their own email address from the autocomplete suggestions instead of entering it manually.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
The updated experience displays the sender's email address directly rather than using the Myself label from the classic experience. This change applies to both standard sending and custom workflows.
- New release notes format – Easier navigation and clearer feature information
Starting with the Adobe Acrobat Sign 18.0 release, release notes will use a new format designed to make it easier to find new features, understand changes, and identify feature availability and configuration requirements.
These 18.0 prerelease notes retain the classic format. The updated format will take effect with the published 18.0 release notes.
Preview the new release notes format
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.
- Expanded EU Digital Identity Wallet Support – Broader compatibility with European trust service providers
Adobe Acrobat Sign expands its support for EU Digital Identity Wallets by adding compatibility with additional authentication and authorization methods used by European trust service providers. This enhancement supports broader interoperability for qualified electronic signatures, allowing organizations to use compatible wallet-based signing services through the existing digital signature workflow.
The update does not introduce new signing controls or change the existing recipient experience.
Available environments: Commercial, Sandbox | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Provider-level enablement
- Webhook TLS 1.3 support - Adobe Acrobat Sign webhooks support TLS 1.3 for HTTPS callback endpoints, allowing integrations to register webhooks and receive notifications when the receiving endpoint requires TLS 1.3.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: None; Core functionality
Release errata
There are no items that have slipped from this release as of this time.
Technical notification
- Rollout schedule for the modern Request Signature experience
All accounts will use the modern Request Signature experience in 18.0. Links for switching to the classic experience and administrator controls for reverting to it will be removed, ending access to the classic interface.
- Rollout schedule for the modern Create Template experience
All accounts will use the modern Create Template experience in 18.0. Links for switching to the classic experience and administrator controls for reverting to it will be removed, ending access to the classic interface.
- Rollout schedule for the modern Custom Workflow Designer
All accounts will transition to the modern Custom Workflow Designer after the 18.0 release. Users will no longer see links to switch between experiences, but administrators can still restore the classic experience or enable switch links. The classic experience is scheduled for permanent retirement in 18.1 (May 2027).
- reminderFrequency=NEVER API behavior changes
The Agreements API now treats reminderFrequency=NEVER as an explicit instruction to disable reminders, overriding applicable workflow, group, or account defaults. Previously, this value was treated as unset, allowing the agreement to inherit the default reminder frequency.
Integrations that rely on inherited reminders must omit reminderFrequency from their POST or PUT requests rather than specifying NEVER. The change affects standard agreements, Send in Bulk, and custom workflows. GET requests also return the resolved reminder frequency.
- Bulk electronic signing enabled by default
Bulk electronic signing will be enabled by default for eligible VIP and ETLA accounts in Acrobat Sign 18.0. Signers can select multiple agreements from the Manage page, review them, and apply their saved electronic signature in a single session. No administrator action is required to enable the feature. Administrators who want to disable it must contact Adobe Support before activation.
- Microsoft Power Automate embedded integration retirement
The embedded Microsoft Power Automate experience has been removed from the Adobe Acrobat Sign web application. Users are no longer able to create, view, or manage Power Automate workflows within Acrobat Sign. Existing workflows continue to run and can be managed directly through Microsoft Power Automate.
For retirement details, licensing considerations, and support options, see Power Automate embedded integration retirement.
Resolved Issues
| Issue number | Resolved issue details |
|---|---|
4536757 |
Summary: After sending an agreement from Salesforce, users could see a blank Home page when opening Acrobat Sign in the same browser session. |
4545653 |
Summary: On iOS, signers could be offered the Sign with Acrobat option when local signing was the only permitted digital-signature method, even though local signing isn't supported on mobile devices. |
4553811 |
Summary: Saved profile signatures and initials could be deleted when an agreement that used them was destroyed, even though the saved signature belonged to the user rather than the agreement. |
4573860 |
Summary: In certain custom workflows, signature fields assigned through text tags could be presented to the wrong recipients because field assignments were not preserved consistently between authoring and signing. |
4576058, |
Summary: Some PDFs containing existing AcroForm fields could display duplicate form fields after upload because document repair incorrectly treated existing fields as orphaned. |
4576609 |
Summary: Repeatedly using Preview & Add Fields in a custom workflow with group-shared templates could fail with an invalid-template error or lose an added document when returning to the send page. |
4577224, |
Summary: With Limited Document Visibility, internal document links could be handled incorrectly when the recipient did not have access to the destination page. |
4579304 |
Summary: Updating agreements through the API could take an excessive amount of time when requests contained large dynamic-participant payloads. |
4579560 |
Summary: Currency-formatted PDF fields could lose their currency symbol and number formatting in the modern signing experience and completed PDF. |
4580193 |
Summary: Some Safari signers could successfully authenticate but be returned to the authentication prompt instead of continuing to the agreement because their authenticated session was not retained through the redirect flow. |
4581589, |
Summary: On iPhone and iPad browsers, signers could enter an authentication loop after successfully signing in because the authentication session was not consistently recognized by the signing experience. |
4582851, |
Summary: Modifying an in-progress agreement again shortly after a previous modification could fail because the second request reused an outdated document reference. |
4583756 |
Summary: The POST /search/agreementAssetEvents API could omit recent completed-agreement events when callers paged through results using onlyShowLatestEvent, preventing integrations from reliably detecting status changes. |
4585898 |
Summary: When an agreement combined templates containing same-named radio groups with numeric option values, the completed PDF could show the selection on only one instance of the group. |
4587315 |
Summary: A radio-button group assigned to Any Recipient could disappear for later recipients when an earlier recipient left it unselected because the PDF’s unselected value was treated as an actual selection. |
4588396 |
Summary: Radio-button text tags sharing a field name could create separate fields instead of one radio-button group when one option included a default value. |
4588621 |
Summary: Users moved between accounts could lose access to existing agreements when either account used customer-managed encryption keys (BYOK) because the agreements remained encrypted with the source account’s key. |
4589289, |
Summary: AGREEMENT_ACTION_REQUESTED webhook notifications could be sent without ParticipantSetsInfo when participant details could not be retrieved, resulting in an incomplete webhook payload. |
4589692 |
Summary: Some bounced-recipient emails could fail to generate the expected bounce event when an already-processed bounce occurred earlier in the same processing batch. |
4589893, |
Summary: Cross-shard user provisioning could time out and roll back when migration processing included an unusually large amount of related user data, leaving the user unprovisioned in the destination account. |
4590142 |
Summary: When Group administrators can edit user permissions was disabled, a group administrator could still grant Group Admin access while adding a new group membership because the restriction was not applied to new memberships. |
4590210 |
Summary: When an agreement was delegated back to a signer who had already participated in the agreement, form field values entered by that signer could be missing from reports and downloaded form-field data. |
4590491 |
Summary: The help text for well-formatted signatures and initials could imply that initials receive the same date formatting as signatures, although initials are not timestamped. |
4592066 |
Summary: GET /users/{userId} could omit primaryGroupId even though the field is defined in the API response schema. |
4592185 |
Summary: Admins could be unable to edit certain web forms built from templates containing matching checkbox or radio fields because repeated field-option data caused the update process to fail or time out. |
4592401 |
Summary: Palau (+680) could be absent from Phone Authentication country selectors even after the country code was enabled for the account. |
4592677 |
Summary: Text tags on a PDF page could fail to convert into Acrobat Sign fields when document text extraction encountered a character without a usable Unicode mapping. |
4593392 |
Summary: When an authenticated web form signer used Sign on Mobile, the agreement could complete while the captured signature was missing from the final PDF. |
4594180 |
Summary: Dutch agreement emails could use wording that described the signing deadline as an expected date rather than a required due date. |
4594244 |
Summary: Hosts of API-created in-person signing agreements could receive an error when opening the signing link if no explicit recipient authentication method had been provided. |
4594582 |
Summary: A Date of Signing field could appear during signing but be missing from the completed PDF for certain document structures. |
4594805 |
Summary: When the API throttled a client for polling too frequently, the response could incorrectly describe the condition as high system load even though the error code identified excessive polling. |
4594862 |
Summary: Applying an existing field template to another template could change radio-button option values when the options were placed on different pages, breaking conditional logic that depended on those values. |
4595222 |
Summary: The Learn More link in the Proof/Notary administration settings used an outdated HelpX destination. |
4595395 |
Summary: Account administrators could receive another BAA/HIPAA confirmation email after an unrelated account-setting change even though the HIPAA setting had already been enabled. |
4595882 |
Summary: Canceled agreements could remain listed under Waiting for You on the Manage page and be selected for Bulk Sign, causing the Bulk Sign job to fail. |
4596142 |
Summary: Replacing a recipient could incorrectly fail with an agreement-not-delegatable error even when the sender’s configuration allowed recipient replacement because validation also considered the original recipient’s delegation permissions |
4598008 |
Summary: WhatsApp delivery consumption could fail to be recorded when the delivery method was changed to WhatsApp while editing an agreement before sending, causing usage counts in settings and reports to be inaccurate. |
4599010 |
Summary: On mobile devices, an image field displayed by conditional logic could appear available but not respond when the signer selected it, preventing the signer from uploading an image. |
Streamline your work with Acrobat Sign
Manage and sign documents online quickly and easily.
