Останнє оновлення:
7 жовт. 2025 р.
Примітка.
This document highlights the new features, experience changes, and resolved issues in the customer-facing application for the most recent release.
Developer-centric updates to the API and Webhooks are documented in the Acrobat Sign developer guide.
Not all features/changes are guaranteed to be enabled on the date of the release.
Adobe Acrobat Sign Release 16.2
Production deployment: October 7, 2025
GovCloud deployment: October 14, 2025
Improved Functionality
- Request Signature introduces several UX improvements designed to reduce clicks and improve efficiency - These updates address customer feedback, making the new Request Signature experience faster, more discoverable, and better aligned with the classic workflow.
- All signature types are expanded by default in Authoring
- Prefill role is always visible in Authoring
- Inline add-recipient buttons replace hidden menus
- Automatic new recipient row when adding an address
- Copy/paste support for multiple recipient addresses
- Admin controls to configure the user experience when composing new agreements. Choose between a guided process or expose all sections upfront.
Review the configuration document here >
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- API support for checkbox groups, allowing senders to define multi-select options within a form - Checkbox groups let senders specify how many options recipients must select, bringing new flexibility for agreements that require structured multi-choice input.
Note that the option for multi-select checkboxes is available for API created agreements only.- Define multi-select checkbox groups.
- Configure rules for exact, minimum, maximum, or ranged selections.
- Validation is enforced during signing in the classic eSign experience.
- Recipient selections are preserved in signed agreements and downloadable form data.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API
Review the updated Checkboxes documentation >
- User Invitation to their Acrobat Sign organization - Invite teammates directly from the Acrobat Sign interface with admin-controlled workflows for faster team adoption. Depending on configuration, invited users may be auto-provisioned, routed through Just-In-Time (JIT) provisioning, or require admin approval. This streamlined flow reduces friction for SMB and mid-market teams, accelerates adoption of shared workflows, and gives admins better visibility into real license demand.
- New Invite button on Home and Manage pages for end users
- Invited users receive a welcome email and are added seamlessly to the organization
- Invitations respect existing auto-provisioning rules
- Admins can review pending requests in the Access requests section
- If auto-provisioning is disabled, requests are routed to admins for approval
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions VIP licensed only | Configuration scope: Account
Review the configuration for inviting teammates and automatically entitling them >
- Reorganized Users page - The Users page has been reorganized to better manage users in their various states, and to provide better visibility for newly invited teammates. This helps isolate users who are having trouble activating their accounts and accelerates onboarding for the larger team.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions VIP licensed only | Configuration scope: Account
Review the new Invite Teammate interface and configuration for automatic license assignment >
- Allowed IP ranges for access to Acrobat Sign have been extended to Groups and APIs - More flexibility has been provided for IP restriction controls when securing access to Acrobat Sign. IP restrictions can now be configured at the group level by Group Admins. In addition, restrictions now apply to API access: if an account or group specifies an allowed set of IP addresses, both the Acrobat Sign UI and APIs can only be accessed from those addresses.
- IP restrictions now apply to both UI and API access.
- Group Admins can configure IP restrictions for their groups.
- Users in multiple groups are evaluated against their default group’s IP policy.
- Integrations and partner applications are allowed by default and not restricted by IP blocking.
- Admins can work with Adobe Support to block applications at the group or account level. If access is blocked, the application must use allowlisted IP addresses to connect to Acrobat Sign.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Review the updated documentation >
- Quality of life updates for ETLA-licensed customers - The recent updates released for VIP licensed customers are being extended to ETLA licensed customers:
- Streamlined admin setup from the Home Page - Acrobat Sign introduces a new Account management section to help account admins quickly access key configuration tools. Add users, organize groups, connect integrations, and migrate templates directly from the Home Page—no digging required.
- Add users to the Admin Console from Acrobat Sign – Admins can now add users directly from the Users page in Acrobat Sign, automatically updating the Adobe Admin Console.
- Admin Console Role assignment now available through Acrobat Sign - To streamline setup, Acrobat Sign now allows account admins to assign key Admin Console roles—Product and Support Admin—without leaving the product interface.
- Easier access to the suite of third-party integrations - A new Integrations page has been added to the admin menu, providing direct, intuitive links to the setup files for the individual integrations.
- Easier HIPAA onboarding through in-product guidance - Organizations subject to HIPAA can now begin the enablement process within Acrobat Sign via a new self-service workflow through the Get Started admin menu. The system sends an automated request to Support and tracks progress based on the BAA signature and system configuration.
- Fast-track your template migration to Acrobat Sign with automated template conversion - The new template migration feature helps account admins quickly bring their templates into Acrobat Sign. Upload a template ZIP file, convert it automatically, and review results in the authoring environment—no technical expertise needed.
- Acrobat Sign Smart Assistant Chatbot - The new Smart Assistant gives you in-app answers to common questions like how to add users, check usage, or update settings. Ask your question in plain language and get step-by-step guidance, relevant HelpX articles, or links to support pages.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
- Remove Certification and Locking Signatures from Digitally Signed Agreements - Organizations that need to pass third-party signature validation services can now request Adobe support to configure their account or group settings to skip the application of Adobe’s Certificate and prevent locking signatures on digitally signed agreements. When enabled, agreements only contain the recipient's digital signatures, reducing rejection rates in strict regional validation tools.
- Account admins can request Adobe support to exclude Adobe Certification and Locking signatures at the account and/or group levels.
- Agreements contain only recipient digital signatures, improving acceptance by third-party validators.
- Audit Report records when certification is skipped, including a SHA-256 document fingerprint
- Applies across all export touchpoints: email attachments, Manage page downloads, API, and webhook payloads
- Resolves compliance gaps raised by customers requiring validation under regional trust schemes- Description
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Review the documentation for removing the Adobe Certificate >
- Access to the modern Send in Bulk features for Acrobat Sign for Government accounts - Send in Bulk has been updated to access the modern functionality for the Acrobat Sign for Government environment.
Available environments: Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Review the Send in Bulk overview >
- PDF/A improved to support PDF/A-3B conformance and convert all uploaded files to the selected PDF/A standard - Admins can now enable conversion and normalization of uploaded files—including PDFs, Microsoft Office formats, and raster images—into PDF/A-2b or PDF/A-3b. Existing PDF/A files are validated, repaired if needed, or normalized to the configured target level.
- Admins can configure PDF/A workflows at the account or group level.
- Supported conformance levels: PDF/A-2b (default) and PDF/A-3b.
- Non-PDF and non-compliant PDF documents are automatically converted to PDF/A.
- Damaged PDF/A files repaired or normalized to the target level.
- Attachments allowed per PDF/A rules: PDF/A-2b (only PDF/A), PDF/A-3b (any file).
- Agreements revalidated for PDF/A compliance at signing completion.
- Audit Reports are optionally generated in PDF/A format and include PDF/A validation/conversion results with conformance level.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Review the updated documentation here >
- "Authentication Method Updated" events in Audit Reports - Changes to recipient authentication methods can now be included in the Audit Report as discrete events. When a sender (or authorized delegate) updates a recipient’s authentication method—such as switching from SMS OTP to Email OTP—the update is captured and recorded in the agreement’s audit report, activity log, and API events list.
- A new event, Authentication Method Updated, appears in the audit report, showing:
- The recipient impacted
- The user who made the change
- The original authentication method
- The new authentication method
- The timestamp of the change
- Events are also exposed through the GET /agreements/{agreementId}/events API.
- Activity logs display the event with recipient, initiator, and timestamp details.
- A new event, Authentication Method Updated, appears in the audit report, showing:
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
Review the updated Audit Log document >
Experience Changes
- Rebranding the notary service in Acrobat Sign from Notarize to Proof – The internal strings referring to Notarize Inc in the Acrobat Sign interface have been updated to the new branding: Proof
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
- IPv6 access for Acrobat Sign for Government- Organizations that use IPv6 on the Acrobat Sign for Government service now have access to the Acrobat Sign IPv6 addresses:
- 2001:489a:3102:4::160/124 (IPv6)
- 2001:489a:3102:4::150/124 (IPv6)
Available environments: Government | Available tiers of service: Acrobat Sign for Government | Configuration scope: Network
- The modern Recipient experience for e-signing is now the default environment for all accounts - All accounts have been updated to use the modern e-signing environment. Admin controls remain in the Admin menu to enable the classic environment if needed.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- The modern Request Signature experience is now the default environment for all accounts - All accounts have been updated to use the modern Request Signature environment. Admin controls remain in the Admin menu to enable the classic environment if needed.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account or Group
- The modern Create Template experience is now the default environment for all enterprise accounts - All accounts have been updated to use the modern Create Library Template environment. Admin controls remain in the Admin menu to enable the classic environment if needed.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
- The modern Custom Workflow Designer experience is now the default environment for all accounts - All accounts have been updated to use the modern Workflow Designer environment. Admin controls remain in the Admin menu to enable the classic environment if needed, and switch links remain for users to shift between the classic and modern experiences (if enabled)
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account or Group
REST API/Webhook Updates
API and webhook updates for this release can be found in the Acrobat Sign API documentation.
- API polling threshold for GET API endpoints regarding status retrieval or listing purposes- A new polling threshold now limits how frequently client applications can poll specific GET /agreement endpoints.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API
- Super Group Admin role for OEM Partners - A new Super Group Admin role is available on the OEM 2.0 platform. This role lets partners grant their customers limited administrative capabilities to create and manage groups without exposing full Account Admin privileges.
- The Partner’s customer can create and manage their own groups.
- The creator of a group automatically becomes its Group Admin.
- Account Admins control which group settings are exposed.
- Group Admins see only relevant settings, such as Message Templates, Email Settings, Send Settings, and Sharing Status.
- The feature requires UMG (Users in Multiple Groups) to be enabled.
- Account Admins remain the only role with access to account-level settings and the ability to assign the Super Group Admin role.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group
Resolved Issues
| Issue | Description |
|---|---|
| 4505635 | Summary: The agreement_retention scope is unavailable in the GovCloud API. |
| Fix: The scope has been configured to work in the GovCloud environment with the Okta integration. | |
| 4515686 | Summary: Webform owners cannot replace the counter signer on existing webforms in specific validation circumstances. Attempting to update the counter signer email returns an error: "You cannot add or remove your email address in the current state of the agreement." |
| Fix: The validation is updated so that the correct sender or countersigner email is recognized. Webform owners can now replace the countersigner as expected. Users do not need to take any action. | |
| 4519727 | Summary: The modern format for phone numbers in Benin isn't recognized (10 character length) |
| Fix: Acrobat Sign now supports the new 10-digit phone number format for Benin. Users can enter valid numbers with the +229 country code without errors. No action is required from users. | |
| 4525532 | Summary: Prefill role is not available by default in the New Authoring Experience |
| Fix: The Prefill role has been exposed by default in the recipient context list when composing agreements | |
| 4526142 | Summary: When applying a form field layer from an existing template in the new authoring experience, some fields do not copy over. |
| Fix: New checking has been added to ensure the complete template is transferred. | |
| 4527772 | Summary: Agreements with sequential routing sometimes lose the recipient name field when assigned to a participant with the Form Filler role. The field fails to display for that recipient, leaving the agreement incomplete. |
| Fix: Significant updates to the REST API have been established to ensure all fields are retained. | |
| 4527945 | Summary: Use of a form field template in an agreement that has a recipient group doesn't work - the template validation code filters out the recipient group participant and the associated fields are lost. |
| Fix: Code has been reworked to use a different member parameter instead of the email value. | |
| 4528619 | Summary: When editing a recipient group name in the new Send experience, the cursor automatically jumps to the end of the text after each change. This makes it difficult to edit the name in one go. |
| Fix: : Request tracking is updated to ensure all authentication methods load properly before sending. Agreements now process correctly once all required authentication details are provided. No action is required from users. | |
| 4531835 / 4537898/ 4541002 |
Summary: Customers encounter errors when using some third-party certificates because the updated root certificates are not trusted, causing issues with webhooks and notifications. |
| Fix: Root CAs are being updated. | |
| 4532798 | Summary: When applying a form field layer, Acrobat Sign creates a new document to capture the layer information. Due to versioning issues in these new documents, some “modify agreement” workflows fail. |
| Fix: We have shifted our approach from pulling the source information through an API to publishing an event when a form field layer template is applied and consuming it in order to populate the source information for the agreements. | |
| 4534813 | Summary: Users in multiple groups cannot use automatic field recognition when creating templates or agreements. |
| Fix: Added a new test to verify field detection in authoring V5 for a user with many groups. | |
| 4535639 | Summary: In some agreements, required image fields are missing from the signed PDF. Although the FormFields.csv shows image URLs, the images do not appear in the final agreement. |
| Fix: The order of a few functions was changed to ensure that inline image fields are processed regardless of whether the form is present, and now the images show up properly for all signers. | |
| 4535828 | Summary: The hyperlinks in the documents are getting changed when the agreement is sent. |
| Fix: When the URL is already encoded specifically with: /, which is a reserved character for URLs, decodeURI is not decoding them, so I changed it to decodeURIComponent to verify the condition before encoding. | |
| 4536354 | Summary: Large PDF documents (~150 pages) fail to load with "unsupported format or password protected" error due to insufficient frontend timeout for image availability checks. |
| Fix: Increase max_retries parameter from 7 (default) to 13, extending the timeout from ~30s to ~60s. This provides sufficient time for large document processing. | |
| 4538897 | Summary: Original IText templates with rotated page content cause the flattened signatures to be rotated out of place on the page. |
| Fix: Before flattening the signatures into the page content, the page content is wrapped with a push/pop gstate to keep the rotational matrix from affecting the added signatures. | |
| 4539304 | Summary: Swagger documentation is default to "Try it out" mode and API consumers find it difficult to browse request schema |
| Fix: The documentation now defaults to view mode instead of “Try it out,” so schemas are visible by default. Performance is improved by eliminating redundant API calls for primitive data types. | |
| 4542576 | Summary: Webhook payloads for the AGREEMENT_ACTION_COMPLETED event return different participant status values in the 16.2 Sandbox release. Previously, memberInfos entries showed “ACTIVE” or “REPLACED” even after signing. In 16.2, they show “COMPLETED.” when Dynamic Participation isn't enabled. |
| Fix: Use of new participant statuses will only be used if Dynamic Participations Feature for In-Flight Agreements is enabled. |
