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
- 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
- Authoring FAQ
- Sign Agreements
- Manage Agreements
- Manage page overview
- Delegate agreements
- Replace Recipients
- Limit Document Visibility
- Cancel an Agreement
- Create new reminders
- Review reminders
- Cancel a reminder
- Access Power Automate flows
- More Actions...
- How search works
- View an agreement
- Create a template from an agreement
- Hide/Unhide agreements from view
- Upload a signed agreement
- Modify a sent agreement's files and fields
- Edit a recipient's authentication method
- Add or modify an expiration date
- Add a Note to the agreement
- Share an individual agreement
- Unshare an agreement
- Download an individual agreement
- Download the individual files of an agreement
- Download the Audit Report of an agreement
- Download the field content of an agreement
- Audit Report
- Reporting and Data exports
- Overview
- Grant users access to reporting
- Report charts
- Data Exports
- Rename a report/export
- Duplicate a report/export
- Schedule a report/export
- Delete a report/export
- Check Transaction Usage
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Transfer ownership of web forms and library templates
- Power Automate Workflows
- Overview of the Power Automate integration and included entitlements
- Enable the Power Automate integration
- In-Context Actions on the Manage page
- Track Power Automate usage
- Create a new flow (Examples)
- Triggers used for flows
- Importing flows from outside Acrobat Sign
- Manage flows
- Edit flows
- Share flows
- Disable or Enable flows
- Delete flows
- Useful Templates
- Administrator only
- Agreement archival
- Webform agreement archival
- Save completed web form documents to SharePoint Library
- Save completed web form documents to OneDrive for Business
- Save completed documents to Google Drive
- Save completed web form documents to Box
- Agreement data extraction
- Agreement notifications
- Send custom email notifications with your agreement contents and signed agreement
- Get your Adobe Acrobat Sign notifications in a Teams Channel
- Get your Adobe Acrobat Sign notifications in Slack
- Get your Adobe Acrobat Sign notifications in Webex
- Agreement generation
- Generate document from Power App form and Word template, send for signature
- Generate agreement from Word template in OneDrive, and get signature
- Generate agreement for selected Excel row, send for review and signature
- Custom Send workflows
- Share users and agreements
Integrate with other products
- Acrobat Sign integrations overview
- Acrobat Sign for Salesforce
- Acrobat Sign for Microsoft
- Other Integrations
- Partner managed integrations
- How to obtain an integration key
Acrobat Sign Developer
- REST APIs
- Webhooks
- Sandbox
Support and Troubleshooting
Adobe Acrobat Sign release schedule and prerelease documentation
Adobe Acrobat Sign rolls out at least three updates per year, categorized as major or minor releases. Additional minor updates may be introduced as needed to address system or customer issues.
- Major Releases bring significant updates, new features, and multiple enhancements.
- Minor Releases focus on smaller improvements and user experience tweaks. These occur between major updates, typically one to two times per cycle.
To prevent disruptions, new features are disabled by default and must be manually enabled by an account or group admin.
For Health and Life Sciences customers requiring compliance validation, Acrobat Sign partners with a third-party vendor to provide a validation package for every major release containing features to minimize your risk factor.
This Prerelease Notes page is regularly updated as new information becomes available, so its content is relatively dynamic.
While this page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.
For the most accurate and up-to-date information, we recommend referring only to the US English page.
Adobe Acrobat Sign follows a structured schedule for publishing release notes and documentation updates:
8 Weeks Before Production Release
- The prerelease page publishes a summary of expected features and updates, typically four weeks before the Sandbox launch.
- Any feature changes after this point are noted in the Errata section.
- Resolved issues are not included at this stage.
4 Weeks Before Production Release (Sandbox Launch)
- The prerelease page is updated with detailed documentation on new and updated features.
- Links to prerelease support documentation (available in US English only) are added as needed.
- The initial Resolved issues section is published, with ongoing updates over the next four weeks.
Launch Day
- The official release notes are updated with final feature details and links to production support documentation.
- The prerelease page is refreshed to highlight the next release cycle.
- Documentation is published after release verification in the live system, typically after 7 pm PT, though complex updates may take longer.
- The final Resolved issues list is added to the US English release notes, with localized versions updated later.
Government Cloud Release
- The Government Cloud environment typically updates between two days and several weeks after the production release, as some features may require additional evaluation before deployment.
Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).
When the release is published, the new pages will also be published, and links will properly resolve to their production URLs.
Sandbox availability
Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.
- The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
- Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
- The Sandbox environment uses the same status page and outage procedures as the regular Production environment.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Sandbox deployment: February 18, 2025
Production deployment: March 18, 2025
GovCloud deployment: March 20, 2025
Experience Changes
- New e-sign environment for OEM Partners - The new e-signing environment has been enabled for the Acrobat Sign OEM partners. This environment provides a superior signing environment for the recipients and includes the option to define a field layer that mobile customers can switch to, significantly improving the field-filling process.
Release errata - Elements added
Below are items that have been added to this release since the initial publishing of the pre-release notes.
- New e-sign environment for OEM Partners - The new e-signing environment has been enabled for the Acrobat Sign OEM partners. This environment provides a superior signing environment for the recipients and includes the option to define a field layer that mobile customers can switch to, significantly improving the field-filling process.
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.
- Send in Bulk: Bulk download - Senders can now easily download completed child agreements from a Send in Bulk transaction directly from the Manage page. The downloaded ZIP file includes only completed agreements, named based on their transaction ID. In-progress, canceled, declined, or expired agreements are excluded.
Each request supports up to 100 MB of data, providing a convenient way to access finalized documents in one step.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Group, Account
Review the updated documentation >
Resolved Issues
Issue | Description |
---|---|
4501733 | Summary: Setting a custom email display value for a group does not apply to reminder and cancelation emails. |
Fix: Reminder and Cancellation email templates updated to properly reflect the Display Email value. | |
4502251 | Summary: Acrobat Sign authentication fails when the sending account is HIPAA enabled, and the sender and recipient have userIDs on different Acrobat Sign shards resulting in an Invalid access token error. |
Fix: The Acrobat Sign authentication method has been improved to properly manage recipients with userIDs on different shards. | |
4504338 | Summary: An unprocessed error is triggered when the first person signs an agreement, but the second recipient is delegated twice. |
Fix: The delegation code has been rebuilt to ensure proper authority to the agreement is passed when chain delegating. | |
4504648 | Summary: Checkboxes added through the API and that are enabled by default may retain their "checked" status on the final agreement even if unchecked during the signature process. |
Fix: The inheritance of the checkbox value has been updated to ensure that the new values after a recipient is done are properly stored and reflected in the resulting PDF. | |
4506085 | Summary: Error when copying large templates from sandbox to Production. Template created without fields due to timeouts in the process. |
Fix: The time threshold has been extended for synching actions. | |
4507500 | Summary: Acrobat (DC Web) users cannot upload attachments when applying a signature due to a missing path in the upload function. |
Fix: The path to allow Acrobat users access to the upload functionality has been included. | |
4508102 | Summary: The process of deleting pages from a combined agreement document can fail because an internal service can throw an exception when deleting page related objects such as bookmarks, structure, destinations which causes the entire operation of deleting a page from a PDF to fail. |
Fix: The internal service has been improved to better manage bookmarks, and the like to properly format the PDF to the Acrobat Sign expected standard. | |
4508673 | Summary: When a signing reason is required, and a signature field is assigned to a non-signer role (e.g., Approver), if modern eSign is enabled, the user is redirected to the modern eSign page and is not given the option to enter the signing reason. |
Fix: A check has been added for a requirement for signing reasons, and if present, the recipient defaults to the classic esign page. | |
4508674 | Summary: Signed agreements with badly formatted destinations cannot be downloaded. |
Fix: The internal library has been patched to better manage poorly formatted bookmarks and destinations. | |
4508934 | Summary: In the Salesforce integration, the File Name is trimmed after "." in the Signed Pdf Email Notification |
Fix: The string trimming function has been improved to identify strings after a period that are not extensions. | |
4509274 | Summary: In the MS Teams environment, if the sender is the first (or only) signer, the agreement is not opened in a new tab after sending due to an empty value being passed in API redirection. |
Fix: Improved the APi redirection by passing the correct values when triggering the signature process, and opening the new tab. | |
4509485 | Summary: Deleting pages from a combined agreement document can fail because an internal service can throw an exception when deleting page-related objects such as bookmarks, structure, and destinations, causing the entire operation to fail. Users can be unable to download their agreement PDF with an error message: "The document is not yet available or will have no pages to view." |
Fix: The internal service has been updated to wrap the deleting process in testing to better manage malformed PDFs. | |
4509562 | Summary: Large agreements could present an issue where only the first several pages of the agreement would print to the PDF when opening the agreement on the Manage page due to an older sdk bundle. |
Fix: The sdk bundle has been updated, resolving the issue. | |
4509684 | Summary: When calling GET /agreements/{agreementId}/documents/{documentId}) from the REST API, an error is triggered: "The server cannot send the response in a format requested in the Accept header" due to an incorrect content-type. |
Fix: The content-type value has been corrected. | |
4509712 | Summary: Only 100 groups are shown when trying to share templates with multiple groups. |
Fix: The number of groups fetched from the API has been increased to 1000 | |
4509989 | Summary: If we have a Name field beside the Signature field on the Web form eSign page, after applying the signature, the Name field does not have the signer's name and it's not visible. |
Fix: An additional function was added to check the name value in the Name field and compare it to the existing value. If it has changed the field is populated with the new value. | |
4510498 | Summary: Suppressing email notifications to recipients fails for Written signature agreements due to a lack of configurable settings to control it. |
Fix: A new setting has bene added to explicitly manage this type of email distribution. | |
4511386 | Summary: When a signer with a digital signature selects the option to download and sign, the participation counter increments before the signature is applied. |
Fix: The logic that updates the system has been improved to better reflect the current status of the agreement. | |
4511390 | Summary: Group administrators don't have the authority to fully establish a share with their group users. |
Fix: The sharing function for group admins has been updated to correct the issue. | |
4511902 | Summary: The custom date tag is not working with the New experience when the display format includes quote marks (due to encoding). |
Fix: Acrobat now decodes the value before saving it. | |
4517094 | Summary: The link to the Terms of Use is failing due to the page being moved to a new source URL. |
Fix: Updated the code to properly fetch the current URL. |
Adobe Acrobat Sign release v16.0
Sandbox deployment: March 25, 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 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.
On the deployment day:
The feature is enabled by default for all Acrobat Standard and Acrobat Pro accounts. There is no interface for configuring it.
Acrobat Sign Solutions accounts will have the option to enable new experience at the account and group level. By default, the option will be disabled.
Available environments: Sandbox, Commercial, Government | Available tiers of service: See above. | Configuration scope: Enterprise only; 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
- 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
- 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
- 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
- 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
- Improve recipient data security by configuring recipients with restricted access - The Restricted Access to Agreements feature enhances privacy by preventing agreements from being attached to a recipient's Acrobat Sign userID (if they have one). When enabled, the Recipient Agreement Access option appears in the Recipient Settings section on the Compose page. Administrators can configure this setting to enable it by default and make it editable by senders.
When a recipient is marked as restricted, they are treated as if they do not have an active Acrobat Sign user account. As a consequence, the agreement does not appear on their Manage page. This prevents accidental data leakage due to group-level sharing relationships.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- 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 Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Revisit Recipient Configuration from the Authoring Page - Senders 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).
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
- 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
- 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)
- Isle of Man (+44)
- Guernsey (+44)
- Jersey (+44)
Available environments: Commercial | Available tiers of service: 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 their first assigned System Administrator provisioned with an Acrobat Sign account 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 Customer Onboarding - Acrobat Sign now streamlines authentication through the Adobe Identity Management System (IMS) by automatically selecting the correct user profile. Users no longer need to choose a profile manually. Adobe IMS:
- Identifies the request as coming from an Acrobat Sign source.
- Selects the profile with the Acrobat Sign entitlement.
- Redirects the user directly to the target URL.
This improvement simplifies login, reducing friction and improving the overall user experience.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions - VIP licensed organizations | Configuration scope: Enabled by default; Not configurable
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.
- 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)
- 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
- Technical block restricting access to Acrobat Sign from IP addresses originating in mainland China - Adobe is implementing a technical block that restricts access to and use of Acrobat Sign from IP addresses located in mainland China. All users (senders, signers, approvers, viewers, administrators, and other supported roles) attempting to access Acrobat Sign via web, mobile app, or API integrations from an IP address located in mainland China will encounter an "access denied" error and will be unable to use Acrobat Sign.
Users accessing Acrobat Sign from permitted locations outside mainland China will not be impacted.
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
The May 2025 release is a minor release containing updates, and fixes for customer-reported issues.
- Sandbox release: April 22, 2025
- Production release: May 20, 2025
- GovCloud release: May 22, 2025
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