User Guide Cancel

Adobe Acrobat Sign Release Schedule and Prerelease Notes

Last updated on Jan 10, 2026

Adobe Acrobat Sign

Open app

Adobe Acrobat Sign Guide

What's New

Get Started

Administer

Admin Console Overview
User Management
1. Add, edit, and review active users
2. Create function-focused users
  1. Technical accounts - API driven
  2. Service accounts - Manually driven
3. Review users who haven't completed verification
4. Check for users with provisioning errors
5. Change Name/Email Address
6. Edit a user's group membership
7. Edit a user's group membership through the group interface
8. Promote a user to an admin role
9. User Identity Types and SSO
10. Switch User Identity
11. Authenticate Users with MS Azure
12. Authenticate Users with Google Federation
13. Product Profiles
14. Login Experience
Account/Group Settings
1. Settings Overview
2. Global Settings
  1. Account tier and ID
  2. New Recipient Experience
  3. Self Signing Workflows
  4. Send in Bulk
  5. Web Forms
  6. Custom Send Workflows
  7. Power Automate Workflows
  8. Library Documents
  9. Collect form data with agreements
  10. Limited Document Visibility
  11. Attach a PDF copy of the signed agreement
  12. Include a link in the email
  13. Include an image in the email
  14. Files attached to email will be named as
  15. Attach audit reports to documents
  16. Merge multiple documents into one
  17. Download individual documents
  18. Upload a signed document
  19. Delegation for users in my account
  20. Allow external recipients to delegate
  21. Authority to sign
  22. Authority to send
  23. Power to add Electronic Seals
  24. Set a default time zone
  25. Set a default date format
  26. Users in Multiple Groups (UMG)
    1. Upgrade to use UMG
  27. Group Administrator Permissions
  28. Replace recipient
  29. Audit Report
    1. Overview
    2. Allow unauthenticated access on the transaction verification page
    3. Include reminders
    4. Include view events
    5. Include agreement page/attachment count
  30. Transaction Footer
  31. In Product Messaging and Guidance
  32. Accessible PDFs
  33. New authoring experience
  34. Healthcare customer
3. Account Setup / Branding Settings
  1. Overview
  2. Add logo
  3. Customize company Hostname/URL
  4. Add company name
  5. Post agreement URL redirect
4. Signature Preferences
  1. Well formatted signatures
  2. Allow recipients to sign by
  3. Signers can change their name
  4. Allow recipients to use their saved signature
  5. Custom Terms of Use and Consumer Disclosure
  6. Navigate recipients through form fields
  7. Restart agreement workflow
  8. Decline to sign
  9. Allow Stamps workflows
  10. Require signers to provide their Title or Company
  11. Allow signers to print and place a written signature
  12. Show messages when e-signing
  13. Require signers to use a mobile device to create their signature
  14. Request IP address from signers
  15. Exclude company name and title from participation stamps
  16. Apply Adaptive Signature Draw scaling
5. Digital Signatures
  1. Overview
  2. Download and sign with Acrobat /content/help/en/sign/config/admin-managed-sharing.
  3. Sign with Cloud Signatures
  4. Include metadata for Identity Providers
  5. Restricted Cloud Signatures Providers
6. Electronic Seals
7. Digital Identity
  1. Digital Identity Gateway
  2. Identity Check policy
8. Report Settings
  1. New report experience
  2. Classic report settings
9. Security Settings
  1. Single Sign-on settings
  2. Remember-me settings
  3. Login password policy
  4. Login password strength
  5. Web session duration
  6. PDF encryption type
  7. API
  8. User and group info access
  9. Allowed IP Ranges
  10. Account Sharing
  11. Account sharing permissions
  12. Agreement sharing controls
  13. Signer identity verification
  14. Agreement signing password
  15. Document password strength
  16. Block signers by Geolocation
  17. Phone Authentication
  18. Knowledge-Based Authentication (KBA)
  19. Allow page extraction
  20. Document link expiration
  21. Upload a client certificate for webhooks/callbacks
  22. Timestamp
10. Send Settings
  1. Show Send page after login
  2. Agreement creation experiences
  3. Require recipient name when sending
  4. Lock name values for known users
  5. Allowed recipient roles
  6. Allow e-Witnesses
  7. Recipient groups
  8. CCs
  9. Required fields
  10. Attaching documents
  11. Field flattening
  12. Modify Agreements
  13. Create a copy (of an agreement)
  14. Agreement name
  15. Languages
  16. Private messages
  17. Allowed signature types
  18. Reminders
  19. Signed document password protection
  20. Send Agreement Notification through
  21. Signer identification options
    1. Overview
    2. Signing password
    3. Knowledge-based authentication
    4. Phone authentication
    5. WhatsApp authentication
    6. One-Time Password via Email
    7. Acrobat Sign authentication
    8. Cloud-based digital signature
    9. Government ID
    10. Signer Identity reports
  22. Content Protection
  23. Enable Notarize transactions
  24. Document Expiration
  25. Preview, position signatures, and add fields
  26. Signing order
  27. Liquid mode
  28. Custom workflow controls
  29. Upload options for the e-sign page
  30. Post-sign confirmation URL redirect
  31. Restrict access to shared agreements
11. Message Templates
  1. Overview of Message Templates
  2. Creating new Message Templates
  3. Editing Message Templates
  4. Deleting Message Templates
12. Bio-Pharma Settings
  1. Overview
  2. Enforce identity authentication
  3. Signing reasons
13. Workflow Integration
14. Notarization Settings
15. Payments Integration
16. Signer Messaging
17. SAML Settings
  1. SAML Configuration
  2. Install Microsoft Active Directory Federation Service
  3. Install Okta
  4. Install OneLogin
  5. Install Oracle Identity Federation
18. Data Governance
19. Time Stamp Settings
20. External Archive
21. Account Languages
22. Email Settings
  1. Email header/footer images
  2. Permit individual user email footers
  3. Customize the Signature Requested email
  4. Customize the To and CC fields
  5. Enable Linkless Notifications
  6. Customize email templates
23. Migrating from echosign.com to adobesign.com
24. Configure Options for Recipients
Guidance for regulatory requirements
1. Accessibility
2. HIPAA
3. GDPR
4. 21 CFR part 11 and EudraLex Annex 11
5. Healthcare customers
6. IVES support
7. "Vaulting" agreements
8. EU/UK considerations
Download Agreements in Bulk
Claim your domain
Report Abuse links
System Requirements and Limitations
1. System requirements
2. Transaction limits

Send, Sign, and Manage Agreements

Recipient Options
1. Cancel an email reminder
2. Options on the e-signing page
Send Agreements
1. Send (Compose) page
  1. Overview of landmarks and features
  2. Group selector
  3. Adding files and templates
  4. Agreement name
  5. Global Message
  6. Completion Deadline
  7. Reminders
  8. Password protect the PDF
  9. Signature type
  10. Locale for the recipient
  11. Recipient signature order/flow
  12. Recipient roles
  13. Recipient authentication
  14. Private message for the recipient
  15. Recipient agreement access
  16. CC'd parties
  17. Identity check
2. Send an agreement only to yourself
3. Send an agreement to others
4. Written Signatures
5. Recipient signing order
6. Send in Bulk
Authoring fields into documents
1. In-app authoring environment
  1. Automatic field detection
  2. Drag and drop fields using the authoring environment
  3. Assign form fields to recipients
  4. The Prefill role
  5. Apply fields with a reusable field template
  6. Transfer fields to a new library template
  7. Updated authoring environment when sending agreements
2. Create forms with text tags
3. Create forms using Acrobat (AcroForms)
  1. AcroForm creation
  2. Creating accessible PDFs
4. Fields
  1. Field types
    1. Common field types
    2. E-signature fields
    3. Initials field
    4. Recipient name field
    5. Recipient email field
    6. Date of signing field
    7. Text field
    8. Date field
    9. Number field
    10. Checkbox
    11. Checkbox group
    12. Radio button
    13. Drop-down menu
    14. Link overlay
    15. Payment field
    16. Attachments
    17. Participation stamp
    18. Transaction number
    19. Image
    20. Company
    21. Title
    22. Stamp
  2. Field content appearance
  3. Field validations
  4. Masked fields values
  5. Setting show/hide conditions
  6. Calculated fields
5. Authoring FAQ
Sign Agreements
Manage Agreements
Audit Report
Reporting and Data exports
1. Overview
2. Grant users access to reporting
3. Report charts
4. Data Exports
5. Rename a report/export
6. Duplicate a report/export
7. Schedule a report/export
8. Delete a report/export
9. Check Transaction Usage

Advanced Agreement Capabilities and Workflows

Webforms
Reusable Templates (Library templates)
Transfer ownership of web forms and library templates
Power Automate Workflows
1. Overview of the Power Automate integration and included entitlements
2. Enable the Power Automate integration
3. In-Context Actions on the Manage page
4. Track Power Automate usage
5. Create a new flow (Examples)
6. Triggers used for flows
7. Importing flows from outside Acrobat Sign
8. Manage flows
9. Edit flows
10. Share flows
11. Disable or Enable flows
12. Delete flows
13. Useful Templates
  1. Administrator only
  2. Agreement archival
    1. Save your completed documents to SharePoint
    2. Save your completed documents to One Drive for Business
    3. Save your completed documents to Google Drive
    4. Save your completed documents to DropBox
    5. Save your completed documents to Box
  3. Webform agreement archival
    1. Save completed web form documents to SharePoint Library
    2. Save completed web form documents to OneDrive for Business
    3. Save completed documents to Google Drive
    4. Save completed web form documents to Box
  4. Agreement data extraction
    1. Extract form field data from your signed document and update Excel sheet
  5. Agreement notifications
    1. Send custom email notifications with your agreement contents and signed agreement
    2. Get your Adobe Acrobat Sign notifications in a Teams Channel
    3. Get your Adobe Acrobat Sign notifications in Slack
    4. Get your Adobe Acrobat Sign notifications in Webex
  6. Agreement generation
    1. Generate document from Power App form and Word template, send for signature
    2. Generate agreement from Word template in OneDrive, and get signature
    3. Generate agreement for selected Excel row, send for review and signature
Custom Send workflows
Share users and agreements
1. Share a user
2. Share agreements

Integrate with other products

Acrobat Sign Developer

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.

Note

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.

The prerelease schedule and notes are listed below.

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.

Note

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.

Releases

Alert

This article contains prerelease information. Release dates, features, and other information are subject to change without notice.

February 3, 2026 (Major release) v17.0

Adobe Acrobat Sign release v17.0

Sandbox deployment: January 6, 2026

Production deployment: February 3, 2026

GovCloud deployment: February 10, 2026

Improved Functionality

Grouped Checkboxes in Authoring and Templates – Senders can now create checkbox groups through the modern Request Signature and Library Templates, authoring environments with validation rules such as selecting exactly, at least, at most, or a range of X out of Y options. Send in Bulk, Web forms, and Custom Workflows are supported through the use of Library Templates. This enhancement ensures consistent form logic and improves data accuracy across signing workflows.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default
Review the updated documentation >

Allowed IP ranges – Expanded control over API and mobile access - Administrators can now explicitly control whether IP restrictions apply to API-based clients, including Acrobat Sign mobile applications and certified integrations.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the updated documentation >

Authentication support for modern e-Sign – Modern e-Sign now supports three authentication methods: Acrobat Sign authentication, password, and phone-based 2FA.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default

Adding Recipient Groups in Hybrid Routing for modern Request Signature – Recipient groups can now be included in hybrid routing, allowing multiple recipients or groups to act in parallel within the same routing step. Group modes support either one or all members to complete the action, providing greater flexibility for complex approval and signing workflows.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default

Copy terminal agreements sent from Request Signature—Senders can now create a new draft agreement by copying a previously completed, canceled, or expired agreement. All recipients, settings, files, and form fields are automatically prefilled. The copied agreement opens in the Compose page for quick edits before sending, reducing setup time, minimizing errors, and improving productivity for repetitive workflows such as renewals or corrections.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Review the configuration documentation >
Review the user action documentation >

Disable the Download agreement link for In-Progress Agreements – Administrators can now remove the “Download a copy” link from post-signing confirmation pages at the account or group level, preventing recipients from downloading partially signed agreements. This helps organizations meet strict legal and compliance requirements, ensuring recipients only receive the fully executed agreement once all participants have completed signing.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Review the documentation >

Resources Tab in Top Navigation – A new Resources page is available in the top navigation for admins and users, providing direct access to Acrobat Sign educational content, webinars, blogs, and product update videos. The page organizes tutorials by user level—beginner, experienced, and administrator—and links directly to additional support documentation.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default
Review the documentation>

Dynamic Participation for In-Flight Agreements – Remove Recipients – Senders can now remove recipients from agreements that are already in progress without canceling or restarting the transaction. When a recipient is removed, Acrobat Sign automatically revokes their access, updates reminders, audit trails, removes the assigned fields, and transitions the agreement seamlessly back to its active signing state. This flexibility helps organizations maintain accuracy in live routing workflows—such as when a signer becomes unavailable—while preserving legal integrity, compliance, and a complete audit history

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the documentation >

Require digital signatures for individual recipients during agreement configuration - Senders can now require digital signatures for selected recipients, ensuring stricter signing requirements where needed without impacting other recipients. The signing experience adapts automatically, enforcing required digital signature fields and exposing identity checks when supported, reducing errors and improving compliance for regulated workflows.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Review the documentation >

Digital Identity Providers as Default Authentication Methods – Administrators can now select a Digital Identity Gateway provider as the default signer authentication method for internal and external recipients in Send Settings. The configuration applies automatically to agreements, web forms, bulk sends, and workflows, ensuring consistent and compliant recipient verification. This enhancement simplifies authentication setup, enforces organizational identity policies, and improves support for government and enterprise customers that rely on Digital Identity-based authentication.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Available by default
Review the documentation >

Verified Form Fields Using Identity-Verified Data – Form authors can now create verified form fields that automatically populate with data returned by an identity provider (such as OneID) during signer authentication. These fields can be set as read-only or editable, ensuring verified identity data is accurately captured and optionally locked against edits (e.g., name, address, or account number). This strengthens identity assurance, reduces manual entry errors, and streamlines compliance for workflows that require validated signer data.

Note: This feature is not included in the Sandbox release, but is expected to be in the official release.

Available environments: Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Review the documentation >

Recipient Groups in CSV File for Send in Bulk – Senders can now define recipient groups directly within the Send in Bulk CSV file, enabling multiple recipients to act at the same routing step. Each group can be configured in ONE or ALL mode—requiring either one member or all members to complete their action before routing advances. Group definitions, validation, and audit tracking are all handled per CSV row, with errors reported through downloadable validation files.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the documentation >

Library Template – Share with Multiple Groups – The modern Create Library Template experience now supports sharing templates with multiple groups within an account, matching the functionality previously available in the classic workflow. Users can select one or more groups when creating or editing a template, ensuring consistent behavior across groups. This enhancement eliminates fallback to the classic experience, improves collaboration, and simplifies template management for multi-group organizations.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Available by default
Review the updated documentation >

File Attachments for all recipients using digital signatures – All recipients in a digitally signed workflow can now attach files (not just the first signer). A new attachment method using Paperclip annotations displays a visible paperclip icon in the document and remains compatible with multiple digital signatures. Each attachment is added before the signer’s digital signature is applied, preserving signature validity and providing a clear visual indicator of attached files. This enhancement improves legal integrity, transparency, and consistency across e-signature and digital-signature workflows.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default
Review the updated documentation>

New TSP options for Cloud Signatures - New Trust Service Providers have been added to support digital cloud signatures:
- Swisscom
  - Swisscom is available, but not yet publicly selectable. If you would like this provider added to your account, please submit a support case, and they will install it for you.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group

Experience Changes

Login Page Improvements - The Acrobat Sign login page now offers a cleaner and more consistent experience. As soon as you enter your email address, the page automatically detects your account type and sends you to the right sign-in method, removing unnecessary steps and legacy screens. This makes logging in faster, simpler, and more intuitive for everyone.
- New email format for Acrobat Sign enterprise users who log directly into the web interface - Acrobat Sign now enforces a 64-character limit to the local part of an email address (the portion before the “@” symbol) when editing an existing email, or creating a new user.
  All users with a local part over 64 characters have been evaluated and determined to be inactive or test userIDs.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the updated documentation >

Enable Management of User Details for Inactive Users – Administrators can now edit user details for inactive users directly in the Admin UI and through CSV uploads without reactivating accounts. This includes updating group assignments (for both single and multi-group configurations), managing the “User can sign documents” attribute, and performing bulk edits for compliance and record maintenance. The change streamlines enterprise user lifecycle management, reduces administrative overhead, and supports cleaner group organization and GDPR-aligned record handling.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and 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.

OEM Embed Partner – Customize Embedded Pages in OEM 2.0 – OEM partners can now customize the embedded Manage page to better align with their platform experience. Partners can hide unsupported navigation items, enable dedicated embedded views for managing Library Templates, Web Forms, and Bulk Sends, and ensure the noChrome parameter reliably hides Acrobat Sign navigation bars across sessions. The update also adds “Create New…” buttons that open the respective views for creating Web Forms, Send in Bulk transactions, and Library Templates, while preserving session context when navigating between embedded views. These enhancements improve flexibility, maintain session continuity, and reduce end-user confusion in OEM 2.0 integrations.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions - OEM Partners | Configuration scope: API

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.

In-Person Signing through the Web Application – Senders and hosts can now conduct fully in-person signing sessions directly from a web browser, without requiring the Acrobat Sign mobile app. Hosts can initiate an in-person signing session from the Manage or Send page and guide recipients as they sign on the same or a nearby device using a secure, time-limited link or QR code. This capability supports use cases where signers are present but lack email access, enabling seamless hosted signing for industries like hospitality and healthcare. The enhancement improves flexibility and eliminates mobile app dependency for organizations that rely on face-to-face signing workflows.

Audit Report Enhancements – Explicit time logging for accepting the ToU, Customer Disclosure, and name application – The Audit Report now records each consent action—Terms of Use (ToU), Consumer Disclosure (CD), and Accept— as distinct, timestamped events before document viewing or signing begins. The signer name change event now reflects the real-time timestamp when the signature is applied, ensuring audit logs accurately represent every consent step. This improvement strengthens compliance reporting and improves transparency for regulated workflows.

Resolved Issues

Issue	Description
4528600	Summary: Field validation settings do not work when a form field layer is attached to a custom workflow. Validation rules, such as regex or numeric range limits, are removed when the workflow is started, causing fields to accept invalid input.
4528600	Fix: Validation rules now apply correctly when form field layers are included in custom workflows. Fields retain their validation behavior across both classic and new authoring experiences. No action is required from users.
4528748	Summary: Admins intermittently see an “Unhandled error” when adding group membership to newly synced users (Azure sync). Some new users in the group have the groupID set as null
4528748	Fix: If a user's group is null after creation, they are placed in the account's Default group.
4529934	Summary: In Manage > Web Forms, “Download Form Field Data” keeps loading and never finishes—especially on web forms with many submissions. Teams customers without API access can’t export data (e.g., May 1–31) for reporting
4529934	Fix: Added paginated, faster CSV export in the UI. Form data downloads complete reliably for selected date ranges, without hanging.
4532186	Summary: In the new authoring experience, field color highlighting does not match the behavior of Classic Authoring. When multiple recipients are involved, all fields remain fully colored rather than dimming non-selected recipients’ fields. This makes it difficult to verify field assignments.
4532186	Fix: Restored visual clarity by dimming (20% opacity) fields that belong to non-selected recipients. This replicates the clarity of Classic Authoring while preserving the modern design system. Highlighting now helps users easily identify the currently selected recipient’s fields and reduces the risk of misassignment.
4534061	Summary: The "Download a copy" link appears on the post-sign confirmation page even when the account or group setting is configured to disable it.
4534061	Fix: A new setting has been added to explicitly suppress the Download option for all post-send pages. The post-sign page now correctly respects the download control setting, hiding the "Download a copy" link when the setting is disabled.
4536347	Summary: In Classic Experience, senders could not add a second file (or retry adding a file) when starting certain workflows, blocking multi-document workflow sends, due to an error in how the file picker handled templates shared across multiple groups.
4536347	Fix: Corrected the file picker’s handling of templates shared across multiple groups so users can add additional files or retry file selection in Classic Experience without errors.
4537504	Summary: A conditional dropdown value was missing from the signed document even though it was correctly selected during signing, due to the visibility logic evaluating against a hidden dependent field and not persisting the rendered value into the final signed PDF.
4537504	Fix: Updated conditional field rendering to correctly resolve visibility dependencies at signing time and persist the selected dropdown value into the signed document when conditions are met.
4537995	Summary: In recipient groups, changing the authentication method for external users reverted to Phone after saving, preventing Email OTP from being applied, due to a front-end state handling error that overwrote the user’s selection.
4537995	Fix: Corrected the recipient group UI logic to properly persist and reapply the selected authentication method across save actions, ensuring the chosen value is retained instead of being reset to the default.
4539214	Summary: In custom workflows, a long message label causes the message text to overlap and obscure the message template hyperlink on the Send page, due to improper layout handling of excessive label content.
4539214	Fix: Updated the Send page layout logic to correctly constrain and wrap long message labels so the message template hyperlink remains visible and accessible.
4539854	Summary: Some signers are redirected away from the signing experience when opening certain agreements, due to a malformed link field in the underlying document that lacks a required name attribute.
4539854	Fix: The signing flow now handles unnamed link fields correctly by assigning a valid name at processing time, preventing errors and allowing signers to complete agreements without redirection.
4539858	Summary: On iOS devices, approvers using the Chinese handwriting keyboard cannot complete approval because the Approve button remains disabled after entering their name, due to the signing page not detecting handwriting input events as valid text entry.
4539858	Fix: Updated the input handling logic to recognize handwriting-based text input on iOS, ensuring the Approve button enables correctly once valid characters are entered.
4540392	Summary: Admins intermittently see HTTP 400 errors and recipient groups appear missing in workflows even though the groups exist and access is correctly configured, due to request headers exceeding the platform’s header size limit when users belong to a large number of groups.
4540392	Fix: The server-side request header size limit was increased so recipient group lookups no longer fail when users have many group memberships.
4541258	Summary: Admins could only see the first 100 templates in the Production or Sandbox Sync UI, with additional templates missing from the Local and Remote lists, due to the sync page loading a limited dataset and the search function filtering only templates already loaded in the browser.
4541258	Fix: The sync UI was updated so that entering text in the search field loads all templates for the selected environment (up to 5,000), ensuring templates beyond the initial 100 are available for search and selection
4541739	Summary: Replaced recipients were blocked from digitally signing and saw “The agreement cannot be digitally signed since it is not in the digital sign phase,” due to the workflow failing to transition future replaced signers into the digital signing phase when digital signature fields were present.
4541739	Fix: The signing workflow was updated to correctly transition replaced or delegated recipients into the digital signing phase when digital signature fields exist, allowing them to sign and complete the agreement.
4541849	Summary: Single-line auto-font-size text fields prefilled with multibyte characters were truncated in signed PDFs, causing part of the text to be cut off due to incorrect text sizing during PDF rendering.
4541849	Fix: Corrected text measurement and auto-font-size behavior for multibyte characters so the full value fits within the field without truncation.
4542574	Summary: Editing a library template allowed required dropdown fields to include unpaired values, causing the Click to sign button to remain unavailable during signing when those values were selected, due to missing validation that ensured dropdown display values and export values remained correctly paired.
4542574	Fix: Template editing now enforces validation on dropdown fields so only properly paired values can be saved, preventing unpaired entries and ensuring required dropdown selections do not block signing.
4542942	Summary: In webforms, required fields disabled by conditional logic continued to display the required asterisk, misleading signers into thinking input was still required, due to the UI not updating required indicators when fields were disabled. A separate mobile signature alignment issue was identified but addressed under a different scope.
4542942	Fix: The webform UI now hides the required asterisk when a field is disabled by conditional logic, ensuring required indicators accurately reflect whether signer input is expected.
4543157	Summary: In the Manage page’s In Progress view, the Recipients column continued to show the delegator’s name after a signing role was delegated, even though a different signer was actively signing, due to the UI not updating the displayed recipient to reflect the current delegatee.
4543157	Fix: The Manage page logic was updated so the Recipients column now displays the active delegatee’s name when a signing role is delegated, ensuring the In Progress view accurately reflects who is currently signing.
4543253	Summary: In the Classic Workflow Experience, witness-assigned fields (signature, name, date) disappeared after saving an agreement in Draft state, even though the fields existed on the backend, due to the draft rendering logic failing to restore witness fields when progress was saved.
4543253	Fix: The draft rendering logic was corrected to preserve and display all witness-assigned fields after saving progress, ensuring agreements opened in Draft state retain the same field visibility as during authoring and signing.
4543513	Summary: Users were blocked from sending agreements in the Sign Web UI with the error “Locale is either invalid or missing,” due to locale validation incorrectly enforcing API-level locale rules in the web interface when the sending group’s locale differed from the user’s inherited primary group locale.
4543513	Fix: Locale validation was corrected so the Sign Web UI properly resolves and accepts valid group and user locale combinations, preventing API-only locale restrictions from blocking agreement sending in the web experience.
4543592	Summary: Some Audit Reports showed “Recipient authenticated with Adobe Acrobat Sign” after “Document e-signed” and “Agreement completed,” due to events being stored with second-level timestamps, causing authentication and signing actions occurring in the same second to appear out of order.
4543592	Fix: Audit event logging was updated to store and display timestamps with millisecond precision, ensuring authentication, signing, and completion events are sequenced correctly in the Audit Report.
4543617	Summary: Creating a template from an agreement launches the Classic experience instead of the New experience, despite the New experience being the default, due to the action still being routed to the legacy authoring flow.
4543617	Fix: The “create template from agreement” action was updated to open in the New experience, aligning the CTA behavior with the default UX and avoiding unexpected context switches for users.
4544564	Summary: Hidden fields added or updated via the API (visible:false) rendered as visible in the Modern eSign experience. The signing UI ignored the field visibility flag, so recipients could see fields that should stay hidden.
4544564	Fix: Updated the Modern eSign UI to filter out fields where visible is false across rendering and navigation logic, so hidden fields never display and do not affect page behavior.
4544571	Summary: The WhatsApp delivery option was missing from Send Settings even though WhatsApp was enabled for the account and available during agreement sending, causing inconsistent behavior and confusion for administrators.
4544571	Fix: The WhatsApp delivery option was restored in Send Settings wherever the feature is available, ensuring consistent visibility and configuration between admin settings and the send agreement experience.
4545381	Summary: The Roboto font was missing from the New Request Signature Experience, even though it was available in the Classic Experience, due to the new authoring experience not including all legacy-supported fonts.
4545381	Fix: Roboto was added to the font list in the New Request Signature Experience, restoring font parity with the Classic Experience and allowing consistent formatting when authoring agreements.
4545484	Summary: Some administrators were unable to access or create recipient groups from Admin > Address Book due to a backend request failure, resulting in a 400 error when loading recipient group data. The issue blocked initial setup of recipient groups for affected admins.
4545484	Fix: The backend request handling was corrected so recipient group search and creation no longer fails with a 400 error. Admins can now reliably access and manage recipient groups regardless of network or location.
4545547	Summary: Agreements created from AutoCAD PDFs failed to send when a digital signature field was added, showing a generic send error, due to the system not correctly handling page rotation when validating digital signature field placement.
4545547	Fix: Digital signature field coordinates are now adjusted to account for rotated pages, ensuring fields are validated against the correct page boundaries so AutoCAD-generated PDFs can be sent successfully with digital signatures.
4545894	Summary: When a recipient group is used and no signature field is manually placed, the auto-generated signature block shows the email address text at a very small size. The text becomes progressively smaller as more recipients are added to the group.
4545894	Fix: The auto-generated signature block now correctly renders the email address at a normal, readable size, regardless of how many recipients are included in the recipient group.
4546085	Summary: When using Add Myself in the New Request Signature experience, email addresses containing an apostrophe are displayed incorrectly. The malformed address prevents the agreement from being sent unless the email is manually re-entered or Classic Send is used.
4546085	Fix: Email addresses with apostrophes are now correctly decoded and displayed when Add Myself is selected in the New Request Signature experience, allowing agreements to be sent without manual correction.
4546110	Summary: In the New Template authoring experience, adding a Hyperlink field assigned to a specific participant causes the template save to fail. The same field works when assigned to all participants or when using the Classic experience.
4546110	Fix: Hyperlink fields now support placeholder participant assignments in the New Template experience, allowing templates to save correctly when the field is assigned to a specific participant.
4546257	Summary: In the Sandbox environment, agreements sent through a custom application API incorrectly show a Back button on the authoring page due to Sandbox loading settings from an Adobe-managed application with seamless authoring enabled, unlike Swagger or Production.
4546257	Fix: Sandbox behavior was aligned with Production and Swagger by ensuring the authoring page respects the intended application settings, preventing the Back button from appearing for agreements sent via custom application APIs.
4546547	Summary: Web forms failed to update the counter signer and returned a miscellaneous error due to older user records missing a required internal flag, which caused a null value to be processed during counter signer replacement.
4546547	Fix: The counter signer update logic was hardened with null-safe handling so web forms can successfully replace counter signers even when older user records lack the expected internal flag.
4546553	Summary: Users assigned to multiple groups could create templates in a group where template creation is disabled when the New Create Template experience is enabled. This allowed bypassing group-level restrictions.
4546553	Fix: Template creation now enforces group-level permissions consistently across the new and classic experiences. Users can no longer create templates in groups where template creation is disabled, even if they belong to other groups with that permission enabled.
4547744	Summary: Group Admins could assign Account Admin rights to users through the new User Management page. This exceeded their permission scope and created a compliance risk by allowing elevation of privileges beyond the Group Admin role.
4547744	Fix: The role selection control is no longer available to Group Admins. Only existing Account Admins can assign or revoke Account Admin rights, ensuring role changes align with permission boundaries.
4547796	Summary: Some senders using the Polish UI occasionally receive a confirmation email with incorrect "cannot provide a digital signature" text, even though the agreement sends and signs normally.
4547796	Fix: Corrected Polish translations for sender confirmation emails so the message shows "sent for signature" instead of the incorrect "cannot provide a digital signature" text.
4548315	Summary: When the sender is included as a CC recipient in the new Send Workflow, no validation error is shown and CC email notifications are not sent to any recipients listed after the sender in the CC list. This differs from Classic Workflow behavior and can cause CC recipients to miss notifications.
4548315	Fix: Updated the new Send Workflow logic so that all CC recipients, excluding the sender, receive CC email notifications regardless of their position in the CC list, aligning behavior with expected outcomes.
4548583	Summary: PDF/A could not be enabled for a group if the user’s default group had written signatures enabled, even when written signatures were disabled for the group being edited. This blocked valid PDF/A configuration for non default groups.
4548583	Fix: Updated the validation to check written signature settings on the group being modified, not the user’s default group, allowing PDF/A to be enabled correctly where permitted.
4549337	Summary: SMS notifications for cancelled agreements were suppressed when the Email Agreement Cancelled setting was disabled. This prevented customers who disable email notifications from sending required SMS cancellation alerts.
4549337	Fix: Decoupled SMS and WhatsApp cancellation notifications from the email setting by introducing a dedicated notification control, allowing SMS delivery for cancelled agreements even when email notifications are disabled.
4549472	Summary: In Acrobat Sign for Government, users could not create reusable templates using the new Create Template experience. After uploading a document, the workflow stalled on a blank screen, blocking template creation.
4549472	Fix: Restored the missing authoring dependency required by the new Create Template experience in Gov environments, allowing the authoring screen to load correctly and templates to be created successfully.
4549862	Summary: When the landing page is set to the New Request Signature experience, the configured login warning message does not display after sign-in. This prevents organizations from showing critical maintenance or disruption notices when users land directly on the Send page.
4549862	Fix: Restored support for displaying the login warning message in the New Request Signature experience. When users land on the Send page after login, the configured warning message now appears as a notification, matching prior behavior and customer expectations.
4550175	Summary: Pressing Enter after entering a phone number for phone authentication in a workflow submits the form prematurely and triggers a system error, interrupting the workflow flow due to the form being submitted instead of waiting for explicit confirmation.
4550175	Fix: Updated the recipient dialog to prevent form submission on Enter for phone authentication fields, ensuring users remain on the dialog and must click Continue, eliminating the unintended workflow interruption.
4550302	Summary: German signature requested and reminder emails used inconsistent forms of address, switching between informal “Du” and formal “Sie” within the same message, causing confusing and unprofessional wording.
4550302	Fix: Updated the German email translations to use a single, consistent form of address throughout the template, ensuring uniform and predictable language in all signature requested and reminder emails.
4550556	Summary: Agreements containing large architectural plan PDFs failed to send when digital signature fields were added, returning an error during authoring due to page rotation and size handling in digital signature placement.
4550556	Fix: Updated digital signature field processing to correctly handle rotated, large-format pages, allowing agreements with architectural plans to send successfully with digital signatures applied.
4550579	Summary: When an agreement was completed by removing the last remaining recipients during an in-revision state, the system did not generate the AGREEMENT_WORKFLOW_COMPLETED event, so no webhook notification was sent, breaking workflows that rely on this event to detect completion.
4550579	Fix: Updated event handling so agreements completed via recipient removal in revision now generate the appropriate completion events, ensuring AGREEMENT_WORKFLOW_COMPLETED webhooks are triggered as expected.
4550998	Summary: Prefilled checkboxes appeared checked in authoring but were unchecked for signers because checkbox values were stored as non-empty text strings instead of explicit YES/NO states, causing the signing experience to treat them as unchecked.
4550998	Fix: Updated checkbox value handling so any non-empty prefilled value is interpreted as checked and empty or missing values as unchecked, ensuring checkbox states remain consistent for signers.

In Release 16.1, Acrobat Sign updated its PDF processing technology to an Adobe-owned solution. This change strengthens platform reliability, scalability, and long-term supportability by reducing reliance on external dependencies. As part of an internal infrastructure update, it was not mentioned in the public 16.1 release notes.

Following the update, a limited set of templates, web forms, and custom workflows associated with specific documents experienced compatibility issues. Affected customers were temporarily supported through an alternate configuration and will be fully transitioned back to the Adobe PDF experience in the first half of 2026.

Customers who believe they were affected and require additional information should contact Acrobat Sign Support.

The following issues related to this change are resolved in the 17.0 release.

Issue	Description
4534178 / 4550340	Summary: PDFs using Helvetica 12 render differently in Sandbox than in Production because Helvetica isn't a supported embedded font in the newer PDF processing path, which substitutes ArialMT as an equivalent. This results in visual differences that affect field alignment during Sandbox testing.
4534178 / 4550340	Fix: Standardized font handling by embedding supported font equivalents and explicitly mapping Helvetica to ArialMT, ensuring consistent and predictable font rendering across environments.
4535543	Summary: Web Forms that include conditional, cloned drop-down fields capture the selected values, but the downloaded signed PDF renders those drop-down selections as blank because the signing-to-PDF merge path does not correctly resolve and apply values for certain malformed or conditionally driven drop-down widgets in the modern signing experience.
4535543	Fix: Updated drop-down field handling during PDF merge so cloned and conditional choice fields render the selected value correctly in the signed PDF.
4535735	Summary: PDF forms containing text fields set to Auto font size render the field text at a tiny size during authoring, signing, and in the final signed PDF.
4535735	Fix: Adjusted Auto font sizing and appearance generation for text fields so prefilled and signer-entered values render at a readable size across authoring, signing, and the signed PDF. Corrected drop-down appearance generation so selected values render in the signed PDF rather than appearing blank.
4535894 / 4547919 / 4550657	Summary: In some agreements, multiline text fields configured with automatic font sizing did not always resize text correctly when signers entered a large amount of content. As a result, portions of the entered text could appear cut off in the signed PDF, even though the full text was visible during signing.
4535894 / 4547919 / 4550657	Fix: The text layout and font-sizing logic for multiline fields has been corrected to ensure that entered content automatically resizes to fit within the field boundaries without truncation.
4536430	Summary: Calling GET /agreements/{agreementId}/documents/{documentId} fails with INVALID_DOCUMENT_ID ("The Document ID specified is invalid"), even though the same document can be downloaded successfully from the Acrobat Sign web experience due to a malformed format during the processing step
4536430	Fix: Hardened the document fetch and processing flow so agreements with PDF structure edge cases no longer fail document retrieval via API.
4537178	Summary: After a FORM_FILLER delegates an agreement, the delegated recipient can't open the agreement to sign. The "Review and Sign" page loads indefinitely. In the impacted agreements, both the original delegator and the delegated recipient show as "Next to Sign," which leaves the agreement in an inconsistent state.
4537178	Fix: Improved the post-delegation processing and state reconciliation so delegation no longer leaves multiple participants in "Next to Sign," and so the signing view does not hang if background document artifacts (page images, doc data) fail or lag.
4537632 / 4543510	Summary: Text entered into data fields configured with the Font size set to 'Auto' appears truncated in the signed PDF.
4537632 / 4543510	Fix: The auto-font sizing logic has been corrected to consistently reflow and scale text, ensuring that all entered content fits within the field boundaries across all supported PDFs.
4544067	Summary: In some signed agreements created from specific source documents, customers encounter an invalid certificate warning in Adobe Acrobat because hidden, malformed form field annotations remain in the PDF after signing, causing the document to fail certification validation despite the signing process completing successfully.
4544067	Fix: Acrobat Sign removes invalid and orphaned annotations during document processing, ensuring signed PDFs validate correctly and display a valid certificate in Acrobat.
4543958	Summary: Some hyperlinks created in Acrobat stop working when they rely on named destinations rather than page numbers because the PDF processing logic did not correctly resolve named destinations to their final page locations during signing, causing links to break in the signed document even though they worked in the original file.
4543958	Fix: Acrobat Sign now correctly resolves named destinations to their actual page locations during PDF processing, ensuring all hyperlinks function as expected after signing.
4543709	Summary: When agreements sent from Salesforce include an image form field, some signed PDFs grow unexpectedly large after signing (often exceeding Salesforce's 12 MB attachment limit), because the PDF processing path can embed uploaded images using inefficient compression, which inflates the final file and prevents Salesforce from saving it back to the Agreement record.
4543709	Fix: Acrobat Sign has updated image handling during PDF generation, so uploaded images (including image and stamp content) are encoded efficiently, keeping signed files much closer to the expected size.
4543678	Summary: For some library templates, signers can complete all required fields, but the downloaded signed PDF may display some of those fields as blank, even though the data is correctly captured and remains available through Acrobat Sign reports and APIs.
4543678	Fix: Acrobat Sign updates how these templates are processed, ensuring signed PDFs reliably render all completed required field values (while avoiding the side effects seen when using the older PDF processing path).
4538033	Summary: The CourierNewPSMT font is ignored during authoring and signing, resulting in fields rendering with an unexpected font due to legacy font handling, where fonts were substituted rather than embedded.
4538033	Fix: Updated font handling to correctly support Courier and other supported fonts for new agreements, ensuring the selected font is preserved during authoring, signing, and in the completed document.
4538082	Summary: Multiline text fields auto-resize incorrectly, causing text to shrink excessively or truncate in completed agreements due to changes in the PDF processing behavior that altered minimum font scaling and line-wrapping logic for auto-sized multiline fields.
4538082	Fix: Adjusted auto-sizing logic for multiline text fields to improve font scaling and line wrapping so entered text remains readable and better aligned with legacy behavior.
4538599	Summary: Some completed agreements show the default drop-down value instead of the signer's selected value because certain special characters in drop-down options caused the chosen value to render incorrectly in the finalized PDF, even though the correct selection was captured during signing.
4538599	Fix: Updated PDF rendering to correctly preserve and display selected drop-down values that include special characters in completed agreements.
4539217 / 4539223	Summary: For certain fillable PDFs that contain prefilled values and digital signature fields, senders may see missing or altered field values when previewing or sending the document, which can block sending or signing because the document structure causes prefilled data and read-only signature fields to be interpreted inconsistently during document processing.
4539217 / 4539223	Fix: Improved document processing to correctly preserve prefilled field values and handle read-only digital signature fields, ensuring agreements preview correctly and can be sent and signed without losing prefilled data.
4539226	Summary: In some agreements created from templates that use text tags for checkbox fields, recipients successfully select checkboxes during signing, but those selections don't appear in the sender's view or the final signed PDF because the checkbox field names are parsed inconsistently, causing the signed values to be stored under a different key than the rendered form field.
4539226	Fix: Updated checkbox value mapping to correctly resolve checkbox fields created from text tags with directive-based names, ensuring selected values render consistently for all parties and in the final signed PDF.
4539432	Summary: Some PDFs could not be sent for signature and were immediately cancelled with a document processing error caused by malformed or orphaned PDF annotations triggering a null pointer error during Acrobat Sign's PDF repair and form-field normalization logic.
4539432	Fix: Improved PDF repair and annotation-handling logic so malformed or orphaned annotations no longer cause agreement creation to fail, allowing affected documents to be sent and signed successfully.
4541859	Summary: Multiline text fields using the Auto font size setting sometimes truncate content in the signed PDF for read-only (locked) multiline fields due to incorrect auto-font scaling during rendering.
4541859	Fix: Corrected auto-font scaling logic for locked multiline text fields so all entered text renders entirely within the field.
4542835	Summary: Customers observed that some required fields (including dropdowns, text fields, and checkboxes) appeared blank in the downloaded signed PDF, even though all fields were completed during signing
4542835	Fix: The PDF rendering logic was corrected to ensure all captured field values, including dropdowns, text fields, and checkboxes, are reliably written into the signed PDF so that the visual document matches the stored agreement data.
4543678	Summary: Some signed agreements were missing required field values in the finalized PDF because certain library templates imported and updated via API did not correctly render mandatory field data during PDF generation.
4543678	Fix: Updated PDF generation logic to ensure all required fields defined in library templates, including those created or modified via API, are consistently rendered in the signed PDF while preserving full field values.
4543709	Summary: Some Salesforce-sent agreements that include image-based form fields can cause the final signed PDF to grow significantly beyond the original file size, exceeding Salesforce's 12 MB limit and preventing the signed document from being written back to the Salesforce Agreement record, even though the signing process itself completes successfully.
4543709	Fix: Optimized image handling during PDF generation to apply appropriate image compression, ensuring signed documents with image, stamp, or image-based signature fields don't inflate in size and remain within Salesforce file size limits.
4543958	Summary: Hyperlinks authored in Acrobat using named destinations stop working in signed PDFs while page-number links still work due to a regression in the PDF processing path where named destinations weren't being resolved to explicit page targets during post-processing.
4543958	Fix: Resolved named destinations to their explicit page destinations during PDF generation, restoring hyperlink functionality for both "Use Named Destination" and "Use Page Number" links in signed PDFs.
4544067	Summary: Some signed agreements display an invalid digital certificate with a "Widget annotation deleted" validation error, resulting from malformed or orphaned widget annotations remaining in the PDF after signing, which invalidates the certification chain.
4544067	Fix: Updated PDF post-processing to detect and remove corrupted or orphaned widget annotations during field cleanup, ensuring only valid annotations remain and signed PDFs consistently display a valid digital certificate.