What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
Administer
- Admin Console Overview
- User Management
- Adding users
- Create function-focused users
- Check for users with provisioning errors
- Change Name/Email Address
- Edit a user's group membership
- Edit a user's group membership through the group interface
- Promote a user to an admin role
- User Identity Types and SSO
- Switch User Identity
- Authenticate Users with MS Azure
- Authenticate Users with Google Federation
- Product Profiles
- Login Experience
- Account/Group Settings
- Settings Overview
- Global Settings
- Account tier and ID
- New Recipient Experience
- Self Signing Workflows
- Send in Bulk
- Web Forms
- Custom Send Workflows
- Power Automate Workflows
- Library Documents
- Collect form data with agreements
- Limited Document Visibility
- Attach a PDF copy of the signed agreement
- Include a link in the email
- Include an image in the email
- Files attached to email will be named as
- Attach audit reports to documents
- Merge multiple documents into one
- Download individual documents
- Upload a signed document
- Delegation for users in my account
- Allow external recipients to delegate
- Authority to sign
- Authority to send
- Power to add Electronic Seals
- Set a default time zone
- Set a default date format
- Users in Multiple Groups (UMG)
- Group Administrator Permissions
- Replace recipient
- Audit Report
- Transaction Footer
- In Product Messaging and Guidance
- Accessible PDFs
- New authoring experience
- Healthcare customer
- Account Setup
- Add logo
- Customize company Hostname/URL
- Add company name
- Post agreement URL redirect
- Signature Preferences
- Well formatted signatures
- Allow recipients to sign by
- Signers can change their name
- Allow recipients to use their saved signature
- Custom Terms of Use and Consumer Disclosure
- Navigate recipients through form fields
- Restart agreement workflow
- Decline to sign
- Allow Stamps workflows
- Require signers to provide their Title or Company
- Allow signers to print and place a written signature
- Show messages when e-signing
- Require signers to use a mobile device to create their signature
- Request IP address from signers
- Exclude company name and title from participation stamps
- Apply Adaptive Signature Draw scaling
- Digital Signatures
- Electronic Seals
- Digital Identity
- Report Settings
- New report experience
- Classic report settings
- Security Settings
- Single Sign-on settings
- Remember-me settings
- Login password policy
- Login password strength
- Web session duration
- PDF encryption type
- API
- User and group info access
- Allowed IP Ranges
- Account Sharing
- Account sharing permissions
- Agreement sharing controls
- Signer identity verification
- Agreement signing password
- Document password strength
- Block signers by Geolocation
- Phone Authentication
- Knowledge-Based Authentication (KBA)
- Allow page extraction
- Document link expiration
- Upload a client certificate for webhooks/callbacks
- Timestamp
- Send Settings
- Show Send page after login
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- Recipient groups
- CCs
- Recipient Agreement Access
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Message Templates
- Bio-Pharma Settings
- Workflow Integration
- Notarization Settings
- Payments Integration
- Signer Messaging
- SAML Settings
- SAML Configuration
- Install Microsoft Active Directory Federation Service
- Install Okta
- Install OneLogin
- Install Oracle Identity Federation
- SAML Configuration
- Data Governance
- Time Stamp Settings
- External Archive
- Account Languages
- Email Settings
- Migrating from echosign.com to adobesign.com
- Configure Options for Recipients
- Guidance for regulatory requirements
- Accessibility
- HIPAA
- GDPR
- 21 CFR part 11 and EudraLex Annex 11
- Healthcare customers
- IVES support
- "Vaulting" agreements
- EU/UK considerations
- Download Agreements in Bulk
- Claim your domain
- Report Abuse links
- System Requirements and Limitations
Send, Sign, and Manage Agreements
- Recipient Options
- Cancel an email reminder
- Options on the e-signing page
- Overview of the e-sign page
- Open to read the agreement without fields
- Decline to sign an agreement
- Delegate signing authority
- Restart the agreement
- Download a PDF of the agreement
- View the agreement history
- View the agreement messages
- Convert from an electronic to a written signature
- Convert from a written to an electronic signature
- Navigate the form fields
- Clear the data from the form fields
- E-sign page magnification and navigation
- Change the language used in the agreement tools and information
- Review the Legal Notices
- Adjust Acrobat Sign Cookie Preferences
- Send Agreements
- Send (Compose) page
- Overview of landmarks and features
- Group selector
- Adding files and templates
- Agreement name
- Global Message
- Completion Deadline
- Reminders
- Password protect the PDF
- Signature type
- Locale for the recipient
- Recipient signature order/flow
- Recipient roles
- Recipient authentication
- Private message for the recipient
- Recipient agreement access
- CC'd parties
- Identity check
- Send an agreement only to yourself
- Send an agreement to others
- Written Signatures
- Recipient signing order
- Send in Bulk
- Send (Compose) page
- Authoring fields into documents
- In-app authoring environment
- Create forms with text tags
- Create forms using Acrobat (AcroForms)
- Fields
- Field types
- Common field types
- E-signature fields
- Initials field
- Recipient name field
- Recipient email field
- Date of signing field
- Text field
- Date field
- Number field
- Checkbox
- Radio button
- Drop-down menu
- Link overlay
- Payment field
- Attachments
- Participation stamp
- Transaction number
- Image
- Company
- Title
- Stamp
- Field content appearance
- Field validations
- Masked fields values
- Setting show/hide conditions
- Calculated fields
- Field types
- Authoring FAQ
- Sign Agreements
- Manage Agreements
- Manage page overview
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Transfer ownership of web forms and library templates
- Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
- Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
- Sandbox
Support and Troubleshooting
Adobe Acrobat Sign release schedule and prerelease documentation
Adobe Acrobat Sign rolls out at least three updates per year, categorized as major or minor releases. Additional minor updates may be introduced as needed to address system or customer issues.
- Major Releases bring significant updates, new features, and multiple enhancements.
- Minor Releases focus on smaller improvements and user experience tweaks. These occur between major updates, typically one to two times per cycle.
To prevent disruptions, new features are disabled by default and must be manually enabled by an account or group admin.
For Health and Life Sciences customers requiring compliance validation, Acrobat Sign partners with a third-party vendor to provide a validation package for every major release containing features to minimize your risk factor.
This Prerelease Notes page is regularly updated as new information becomes available, so its content is relatively dynamic.
While this page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.
For the most accurate and up-to-date information, we recommend referring only to the US English page.
Adobe Acrobat Sign follows a structured schedule for publishing release notes and documentation updates:
8 Weeks Before Production Release
- The prerelease page publishes a summary of expected features and updates, typically four weeks before the Sandbox launch.
- Any feature changes after this point are noted in the Errata section.
- Resolved issues are not included at this stage.
4 Weeks Before Production Release (Sandbox Launch)
- The prerelease page is updated with detailed documentation on new and updated features.
- Links to prerelease support documentation (available in US English only) are added as needed.
- The initial Resolved issues section is published, with ongoing updates over the next four weeks.
Launch Day
- The official release notes are updated with final feature details and links to production support documentation.
- The prerelease page is refreshed to highlight the next release cycle.
- Documentation is published after release verification in the live system, typically after 7 pm PT, though complex updates may take longer.
- The final Resolved issues list is added to the US English release notes, with localized versions updated later.
Government Cloud Release
- The Government Cloud environment typically updates between two days and several weeks after the production release, as some features may require additional evaluation before deployment.
Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).
When the release is published, the new pages will also be published, and links will properly resolve to their production URLs.
Sandbox availability
Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.
- The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
- Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
- The Sandbox environment uses the same status page and outage procedures as the regular Production environment.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Adobe Acrobat Sign release v16.0
Sandbox deployment: March 26, 2025
Production deployment: April 22, 2025
GovCloud deployment: April 24, 2025
Improved Functionality
- Send in Bulk: Bulk download - Senders can now download all completed child agreements from a Send in Bulk transaction directly from the Manage page. The ZIP file includes only completed agreements, named based on their transaction ID, while in-progress, canceled, declined, or expired agreements are excluded.
Each download request supports up to 100 MB of data, offering a quick and efficient way to access finalized documents in a single step.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group and Account
Review the updated Send in Bulk documentation >
- Enhanced Mobile Signing Experience - Senders can now enable and configure a mobile-optimized signing experience, giving recipients two viewing options:
- PDF View – Displays the entire agreement for review and signing.
- Field-Only View – Focuses on form fields, making completing and signing agreements on mobile devices easier.
This update streamlines the signing process, improving form completion rates and overall mobile experience.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Configure the feature documentation (enterprise only) >
Create the mobile-focused form field overlay >
E-signing environment: Desktop >
E-signing environment: Mobile >
Feature gap between new and classic Desktop environments >
Feature gap between new and classic Mobile environments >
- Checkbox and Radio Button: Show Field Border option - Checkbox and Radio Button fields now include an option to Show field border when viewing and printing the agreement. This option can be turned off when the uploaded document already contains pre-printed borders, ensuring a cleaner final document by preventing duplicate borders.
The option is enabled by default and configured at the field level.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Field-level property
Review the new Form Field Borders configuration >
- Enhanced Automatic Form Field Detection The automatic form field detection feature now places detected fields automatically, streamlining the form creation process. Users retain complete control and can edit, delete, or remove all placed fields with a single action.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default; not configurable
Configure the controls for automatic form field detection >
Review the updated Automatic Form Field Detection document >
- CC’d parties for individual recipients in Custom Workflow Designer - The Custom Workflow Designer now allows each individual recipient to have dedicated CC’d parties. When enabled, CC’d parties receive notifications simultaneously with the intended recipient, ensuring better visibility and streamlined communication. This feature is available if the account is configured to allow it.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Review the updated Workflow Designer document >
- New Option to Set Recipient Signature Type - Senders can now define the signature type for recipients when sending agreements through the modern Request Signature process. When enabled, a Signature Type drop-down appears in the Recipient settings section of the Compose page, showing the options allowed by group settings.
- The setting defaults can be configured at the group level.
- If the sender selects a signature type, the recipient must use that type.
- The sender can select multiple options for the recipient.
- The recipient can choose their preferred signature type if no selection is made.
This feature provides greater control over signature methods while maintaining flexibility when needed.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Configure the Allow recipients to sign and initial by setting >
Updated Request Signature documentation >
- Improved User Management in Acrobat Sign - The Acrobat Sign user administration view has been updated to enhance visibility into the users’ status. The improved interface provides easier access to review pending invites and clear indicators for provisioning issues. The new interface also highlights the prominent actions admins can perform for each of the status categories (Add User, Send reminder, and Contact support) to streamline the user provisioning process.
Improved User Management is being deployed in a phased manner.
The April 2025 release exposes this feature to customer accounts who manage users in the Adobe Admin Console and are under a VIP licensing contract.
ETLA-licensed accounts will see this feature become available in a future release.
Available environments: Commercial | Available tiers of service: See Note above | Configuration scope: Not configurable; Enabled by default
Review the updated user management documentation >
- New WhatsApp Delivery for One-Time Passwords - Acrobat Sign now supports WhatsApp as a delivery method for one-time passwords (OTP) to recipients' phones. This feature functions similarly to SMS delivery but leverages WhatsApp's technology and infrastructure, providing additional stability and a convenient communication option. WhatsApp OTP authentication is a premium authentication type that is available when composing new agreements.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the WhatsApp authentication configuration >
Updated Request Signature documentation >
- Revisit Recipient Configuration from the Authoring Page - Senders using the new Request Signature experience can now navigate back to the Compose page from the Authoring environment to reconfigure recipients and their properties without losing progress. This allows for adjustments to recipient order and details while ensuring that existing field assignments remain intact (e.g., Signer 1 remains Signer 1). (If a participant is removed, their related fields will also be removed.)
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default; Not configurable
- New Authoring Environment for Library Templates - The library template authoring environment now features the modern authoring experience for field placement, making creating and customizing templates easier. Enhancements include:
These updates streamline template creation and ensure a seamless experience for both senders and recipients.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Enable the new Create Template environment >
Review the new Create Template process >
- New Identity Providers (IdPs) Added to Acrobat Sign - Acrobat Sign is expanding its list of supported identity providers (IdPs) to enhance the recipient's authentication options. The following new IdPs are now available:
- OneID ID Check
- OneID ID Proof
- OneID ID Assure
- OneID Sign-Up Plus
These additions expand Acrobat Sign's compatibility with global identity verification standards, supporting seamless and secure authentication across multiple industries.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Experience Changes
- System administrators of a VIP account in the Admin Console are automatically assigned an Acrobat Sign entitlement - When an account initially purchases the Acrobat Sign service under a VIP license, they will have their users with System Administrator privileges automatically assigned an Acrobat Sign license.
- New organizations will have all existing assigned System Administrators provisioned with an Acrobat Sign administrator-level entitlement.
- Existing organizations that purchase an Acrobat Sign license will have all existing System Administrators provisioned with an account administrator-level Acrobat Sign entitlement.
The Acrobat Sign license is automatically entitled only when the Acrobat Sign services are first purchased for the organization. Entitlement does not happen for subsequently promoted System Administrators.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions under VIP licensing | Configuration scope: Not configurable; Enabled by default
- Improved Administrator Onboarding Checklist and Communications - Acrobat Sign administrators now receive enhanced support for managing account onboarding, including new tools and improved email communications.
Improved onboarding features include:- Onboarding Checklist – A new Get Started tab has been added under the Admin page, providing a short checklist of key actions for new administrators when they first take control of an account.
- Updated Welcome and Reminder Emails – The initial email notifications sent to new administrators have been revised to support the onboarding checklist, offering clearer guidance on the next steps in account setup.
- Monthly Overview Email – Administrators will receive a monthly summary detailing:
- Visibility into all user statuses and where administrators need to take action.
- Number of transactions/seats consumed since the start of the contract. Administrators no longer need to navigate to the admin console just for this information.
- A quick snapshot of the contract including the anniversary date.
- Intelligent Existing Entitlement Detection and Notification - If a user’s previous Acrobat Sign entitlement is detected, the affected user will be included in a weekly notification email sent to all account administrators. Each such user may appear in up to three notifications.
These improvements help administrators manage their accounts more efficiently and stay informed about system activity and potential issues.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions - VIP licensed organizations | Configuration scope: Enabled by default; Not configurable
- Improved User Login Experience - Acrobat Sign has streamlined the login and authentication process through the Adobe Identity Management System (IMS).
- The user's organizational profile is automatically selected during the login process to the ones entitled with the Acrobat Sign service ( Identifying the request as coming from an Acrobat Sign source)
- Users who encounter errors during login will have links in their error messages to contact their Acrobat Sign administrators for assistance.
- All users assigned an active entitlement but have not logged in to the service will be sent up to two email reminders. (This also applies to existing inactive users before the release date )
These improvements simplify login, reduce friction, and improve the overall user experience.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; Not configurable
- The Account tab renamed to Admin - The Account tab, available to Acrobat Sign account-level administrators, has been renamed to Admin. This is a cosmetic change to the tab label in the Standalone web version of the application. This update is implemented for the Commercial environment in April 2025 and the Government environment in May 2025.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not configurable; Enabled by default
Mobile application updates
- Update to template file management - The template list in the Acrobat Sign mobile app now follows a structured format, making it easier to find specific templates. The structure aligns with the web version, organizing templates into sections such as:
- My Templates
- Group Templates
- Account Templates
This update improves navigation and ensures consistency between the mobile and web experiences.
Available environments: iOS mobile application | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default
- Improved Accessibility in Acrobat Sign Mobile Apps - The Acrobat Sign mobile applications now offer enhanced accessibility features, ensuring better compliance with accessibility standards. Updates include:
- Improved color contrast for better visibility.
- Keyboard shortcut support for easier navigation.
- Enhanced screen reader compatibility for a more inclusive user experience.
These improvements make the mobile app more accessible to all users, providing a smoother and more user-friendly experience.
Available environments: iOS mobile application | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default
Integration Updates
- Updated Acrobat Sign Connectors for Microsoft Power Automate - The Acrobat Sign connectors for Power Automate now support an improved agreement-sending process that allows documents to be loaded into the Compose page for editing recipient information and then sending the agreement to the Authoring environment for further field placement.
Additionally, the Acrobat Sign connectors now support two advanced authentication methods:
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Workday integration: Digital signatures with Aadhaar e-Sign - The Workday integration now fully supports the optional Aadhaar e-Sign service available in India, an online electronic signature service that facilitates digitally signing agreements based on OTP authentication and e-KYC verification.
Available environments: Commercial | 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.
- GDPR Compliance: Delete User Info via API - Partners can now use the API to delete user information when removing a user's data in compliance with GDPR requirements. This enhancement streamlines data management and ensures regulatory compliance.
Available environments: Commercial | Available tiers of service: OEM Partners | Configuration scope: API
- New Webhook Field: eventDateTimezoneOffset - Adobe Acrobat Sign introduces eventDateTimezoneOffset, a new field in the webhook payload for the AGREEMENT_ACTION_COMPLETED subscribed event.
This field captures the recipient's timezone offset when they update the agreement, providing better visibility into the local signing time.- eventDateTimezoneOffset records the recipient's timezone offset in minutes relative to UTC (e.g., eventDateTimezoneOffset : "UTC-300")
- The existing eventDate field remains unchanged and continues to store the action's UTC timestamp. The timezone offset does not modify the eventDate value.
This update enhances the tracking of signing activities across different time zones.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API
- Migration of Acrobat Sign Developer Documentation - Acrobat Sign developer documentation is moving from opensource.adobe.com/acrobat-sign to developer.adobe.com/acrobat-sign. This migration ensures better integration with Adobe's developer resources, providing a more streamlined and centralized experience for developers.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API
Release errata - Elements added
Below are items that have been added to this release since the initial publishing of the pre-release notes.
- The Account tab renamed to Admin - The Account tab, available to Acrobat Sign account-level administrators, has been renamed to Admin. This is a cosmetic change to the tab label in the Standalone web version of the application. This update is implemented for the Commercial environment in April 2025 and the Government environment in May 2025.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not configurable; Enabled by default
- Improved Administrator Onboarding Checklist and Communications - Acrobat Sign administrators now receive enhanced support for managing account onboarding, including new tools and improved email communications.
Improved onboarding features include:- Onboarding Checklist – A new Get Started tab has been added under the Admin page, providing a short checklist of key actions for new administrators when they first take control of an account.
- Updated Welcome and Reminder Emails – The initial email notifications sent to new administrators have been revised to support the onboarding checklist, offering clearer guidance on the next steps in account setup.
- Monthly Overview Email – Administrators will receive a monthly summary detailing:
- The number of active users in the system.
- The number of transactions used in the previous calendar month.
- Proactive Entitlement Conflict Email – If a user entitlement error is detected, the affected user will be included in a weekly notification email to the account administrator. Each entitlement error may appear in up to three notifications.
These improvements help administrators manage their accounts more efficiently and stay informed about system activity and potential issues.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions - VIP licensed organizations | Configuration scope: Enabled by default; Not configurable
- Expanded Country support for Phone Authentication – Phone Authentication and agreement delivery via SMS now support these additional Countries and Country Phone codes:
- Isle of Man (+44)
- Guernsey (+44)
- Jersey (+44)
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Workday integration: Digital signatures with Aadhaar e-Sign - The Workday integration now fully supports the optional Aadhaar e-Sign service available in India, an online electronic signature service that facilitates digitally signing agreements based on OTP authentication and e-KYC verification.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- CC’d parties for individual recipients in Custom Workflow Designer - The Custom Workflow Designer now allows each individual recipient to have dedicated CC’d parties. When enabled, CC’d parties receive notifications simultaneously with the intended recipient, ensuring better visibility and streamlined communication. This feature is available if the account is configured to allow it.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Migration of Acrobat Sign Developer Documentation - Acrobat Sign developer documentation is moving from opensource.adobe.com/acrobat-sign to developer.adobe.com/acrobat-sign. This migration ensures better integration with Adobe's developer resources, providing a more streamlined and centralized experience for developers.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | 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.
- Improve recipient data security by configuring recipients with restricted access - The Restricted Access to Agreements feature enhances privacy by preventing agreements from:
- Being viewed or downloaded by the recipient before they complete their action on the agreement (Signing, approving, etc.)
- Being shared through a user or group share.
- (Optionally) being automatically delegated if auto-delegation is configured.
When enabled, the Recipient Agreement Access option appears in the Recipient Settings section on the Compose page. By default, the setting is enabled for all recipients. Administrators can configure this setting to make it editable by senders.
- Expanded Country support for Phone Authentication – Phone Authentication and agreement delivery via SMS now support these additional Countries and Country Phone codes:
- Falkland Islands (Malvinas) (+500)
Resolved Issues
Issue | Description |
---|---|
4490799 | Summary: Default Country Code can't be changed with New Experience Send page |
Fix: The code was improved to ensure inherited group properties are pushed through all processes to complete agreement creation. | |
4501927 | Summary: Discrepancy in PDF Handling Between Classic and New Authoring modes post release |
Fix: Improved the code to better access and use all field properties in the transformations of PDF files. | |
4503970 | Summary: Inappropriate completion message when the 1st recipient is the Sender. |
Fix: Updated the message to be role-aware so it shows the correct message. | |
4505208 | Summary: [RequestSignature] CC field does not display Auto-complete options from the address book. |
Fix: Addressbook functionality added to the CC field. | |
4507982 | Summary: When multiple groups share with a user through advanced account sharing, a performance issue may happen when trying to access a Template under the Manage tab, Templates filter. |
Fix: Refactored several functions to optimize for multiple group searching. | |
4508227 | Summary: An unhandled error occurs when signing agreements originated through new authoring experience with payment fields. |
Fix: Updated the endpoint to manage the field with less ambiguity,. | |
4508929 | Summary: Error triggered for Custom Work Designer field labels that are under 100 characters due to special characters being encoded. |
Fix: Special characters are decoded while validating the character limit. | |
4509141 | Summary: An uni9nformative error triggers when sending an agreement with a witness, and the group is configured to require an authentication method, but the witness is configured for no authentication. |
Fix: The configuration process now includes an error message indicating when two-factor authentication for all recipients is configured and a witness is used. | |
4509366 | Summary: FedRAMP customer name update failed with special characters due to the characters not being replaced with their HTML entity numbers. |
Fix: Updated the process to properly manage special characters in the FedRAMP environment. | |
4509680 | Summary: Add countries Isle of Man, Guernsey, and Jersey for the country code +44. |
Fix: Added the COUNTRY_CODE constants for Isle of Man, Guernsey, and Jersey | |
4510255 | Summary: Attempting to create a user that already exists in another group appears to create the user in the group with no useful. |
Fix: The error has been improved to indicate the user has been moved to the new group (not created). | |
4510309 | Summary: When a signature block is added through API with inputType other than BLOCK, The signature process is routed to the classic experience due to the BLOCK not being identified properly. |
Fix: Improved the condition to return additional information to properly identify the BLOCK object. | |
4510652 | Summary: Digitally signed form fields need to be flattened prior to modifying the PDF for the next signer |
Fix: Digital signature form fields that have been signed are invalidated when submitted by a written agreement workflow. | |
4511819 | Summary: The signature's blue line appears in the PDF document for unsigned signature fields. |
Fix: Unsigned signature fields are skipped while rendering signature fields into the PDF document. | |
4511965 | Summary: Digital Identity Gateway login hint isn't working due to applied ID checking when fetching the ID criteria. |
Fix: Removed the email and name matching check while fetching auth criteria for DIG_ID. | |
4513228 | Summary: Missing field value in pdf document when the field name contains extra space due to the field name being trimmed on the backend. |
Fix: Trimming the field name on the front end to keep the field name consistent. | |
4513358 | Summary: File processing issue in Adobe Sign Sandbox instances die to form fields with no references to pages. In such cases the page is null, and a null pointer is thrown. |
Fix: Added a null check for this event to properly manage it. | |
4513464 | Summary: Admin encounters multiple errors while interacting with templates via advanced account sharing because the API is evaluated under the session user's permissions (e.g., Editor_User) instead of the switched user's permissions (e.g., Creator_User). |
Fix: Added the x-on-behalf-of-user header to the API request to ensure the request is evaluated under the switched user's (Creator_User) permissions. | |
4513575 | Summary: Form field data is not resizing for multi-line fields. |
Fix: Updated code with to allow auto sizing. | |
4513914 | Summary: When number of ACTIVE users in account is equal to MAX_ACTIVE_USERS value, then changing a password is not allowed because of a MaxActiveUsers check. |
Fix: Improved the function to properly ignore this check when the user is ACTIVE. | |
4514839 | Summary: User cannot sign with multiple digital signatures on an agreement if the first field signed is not the first signature field at the top of the document. |
Fix: Added method to iterate over all fields and extract valid ticket that is further used for X-JWT-Assertion header. | |
4515343 | Summary: Font size of multiline input field is changing on the e-sign page. Font size is multiplied by zoom factor, so the size of input varies depending on it - specifically, it is adjusting dimensions of a page. |
Fix: The method for getting the font size of multiline field is returning font size in px, without multiplying it by a zoom factor. | |
4516641 | Summary: It is possible for the annotation of a form field to not be attached to a page. |
Fix: A null check has been added to the annotation list of the page. | |
4517113 | Summary: Document problem email received when sending agreement via API through a developer account due to null pointer errors when checking form fields. |
Fix: We are now checking if the list of form fields is null before asking if the list is empty. | |
4517156 | Summary: When there are existing form fields on a set of input PDF's, form field generators are not allowed to run to produce additional form fields. |
Fix: When there is a list of form field generators to process, we will add that task to the list of tasks to run after the ReadPDFTask |
- The modern Request Signature environment has become the default experience when creating a new agreement. All existing accounts have been switched to the modern environment -
- Users can no longer access links to switch between the new and classic environments.
- Administrators still have the option to enable the classic experience through the admin menu.
- Customers using the Notarize integration will not be affected by this change.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Sandbox deployment: April 22, 2025
Production deployment: May 20, 2025
GovCloud deployment: May 22, 2025
Improved Functionality
- Expanded Country support for Phone Authentication – Phone Authentication and agreement delivery via SMS now support these additional Countries and Country Phone codes:
- Falkland Islands (Malvinas) (+500)
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Experience Changes
- The modern Request Signature environment has become the only experience when creating a new agreement. All existing Commercial accounts have been switched to the modern environment -
- Administrators no longer have the option to enable the classic experience through the admin menu.
- Customers using the Notarize integration will not be affected by this change.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default; Not configurable
REST API/Webhook Updates
The below updates are presented in the prerelease notes for disclosure purposes. Full documentation for API and Webhook updates can be found in the Acrobat Sign developer documentation when the version update is delivered to the production servers.
- GET /agreements API Now Served from a Microservice - The GET /agreements endpoint is migrating from the Acrobat Sign core application to a dedicated microservice. As part of this transition, search requests will retrieve data from the search service (secondary storage) instead of the primary database. This change enhances service stability and prevents atypical API calls from affecting the Acrobat Sign experience.
- The maximum page size for the GET /agreements call is now 500 agreements per request. Historically, the search service did not fetch more than 100 agreements per page. If more agreements are required, multiple queries with a narrower scope may be necessary.
- Since searches now occur in secondary storage, minor additional latency may be observed when calling the GET /agreements endpoint.
Release errata
There are no items that have slipped from this release as of this time.
The July 2025 release is a major release containing features, updates, and fixes for customer-reported issues.
- Sandbox release: June 24, 2025
- Production release: July 22, 2025
- GovCloud release: July 24, 2025
The September 2025 release is a minor release containing updates, and fixes for customer-reported issues.
- Sandbox release: August 19, 2025
- Production release: September 16, 2025
- GovCloud release: September 18, 2025
The October 2025 release is a major release containing features, updates, and fixes for customer-reported issues.
- Sandbox release: September 15, 2025
- Production release: October 7, 2025
- GovCloud release: October 9, 2025