What's New
Get Started
- Quick start guide for administrators
- Quick start guide for users
- For Developers
- Video tutorial library
- FAQ
- Enterprise Trial
Administer
- Admin Console Overview
- User Management
- Add, edit, and review active users
- Admin Console SSO
- Create function-focused users
- Review users who haven't completed verification
- 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
- Group management
- 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
- PDF/A workflows
- Healthcare customer
- New request signature experience
- New custom workflow experience
- New create template experience
- Account Setup / Branding Settings
- 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
- Enable classic Reporting
- 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
- Agreement creation experiences
- Require recipient name when sending
- Lock name values for known users
- Allowed recipient roles
- Allow e-Witnesses
- In-person signing config
- Recipient groups
- CCs
- Required fields
- Attaching documents
- Field flattening
- Modify Agreements
- Remove recipients from in-flight agreements
- Agreement name
- Languages
- Private messages
- Allowed signature types
- Reminders
- Signed document password protection
- Send Agreement Notification through
- Signer identification options
- Populate form fields with identity-verified data
- Content Protection
- Enable Notarize transactions
- Document Expiration
- Preview, position signatures, and add fields
- Signing order
- Enable hybrid signature flows
- Add myself
- Send only to internal recipients
- Download agreement link
- Form field borders
- Liquid mode
- Custom workflow controls
- Upload options for the e-sign page
- Post-sign confirmation URL redirect
- Restrict access to shared agreements
- Show Send page after login
- 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
User profile and configurable features
- Address Book
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
- Compose in-person agreement
- Recipient signing order
- Hybrid recipient workflow
- Send in Bulk
- Send (Compose) page
- Authoring fields into documents
- In-app authoring environment
- Automatic field detection
- Drag and drop fields using the authoring environment
- Assign form fields to recipients
- The Prefill role
- Apply fields with a reusable field template
- Transfer fields to a new library template
- Updated authoring environment when sending agreements
- 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
- Checkbox group
- 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
- Verified forms
- Field types
- Authoring FAQ
- In-app authoring environment
- Sign Agreements
- Manage Agreements
- Manage page overview
- Copy an Agreement
- 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
- Bulk actions
- Hide multiple agreements
- Digitally sign multiple agreements
- Audit Report
- Reporting and Data exports
Advanced Agreement Capabilities and Workflows
- Webforms
- Reusable Templates (Library templates)
- Manage Shared 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
- Integration keys
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).
The new pages will be published when the release is published, and links will properly resolve to their production URLs.
Sandbox availability
Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.
- The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
- Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
- The Sandbox environment uses the same status page and outage procedures as the regular Production environment.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Adobe Acrobat Sign release v17.1.2
Sandbox deployment: June 16, 2026
Production deployment: July 21, 2026
GovCloud deployment: July 23, 2026
Improved Functionality
- Preserve Existing Digital Signatures in Uploaded PDFs – Admins can enable Acrobat Sign to preserve existing digital signatures in uploaded PDF files, allowing pre-signed documents to move through supported agreement workflows without flattening the original signature. This helps organizations use documents that were digitally signed before upload while protecting the document from changes that would invalidate the preserved signature.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Review the configuration for preserving digital signatures >
Review the process for sending a PDF with an existing digital signature >
- Inline Document Editing During Authoring – Edit document text directly in the authoring experience
Senders can edit document text directly in the authoring environment without downloading and re-uploading the file. The Edit Document option preserves existing fields and agreement configuration, reducing disruption during pre-send updates. Editing is available only while the agreement is in a draft state and is not available after the agreement is sent.
In-line document editing is to be released on a rolling schedule, as referenced in the technical notification.
This feature is enabled by default for all users in supported accounts, allowing senders to edit documents that are sent through Request Signature. Account and group admins can disable document editing through the Send Settings.
In-line document editing is not available in Acrobat Sign for Government or for accounts using the legacy user management system.
Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions VIP and VIPMP customer accounts | Configuration scope: Account and Group; Enabled by default
Enable or disable in-line document editing >
How to edit text during field authoring >
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.
- Customer-managed encryption keys for agreement files – Eligible Acrobat Sign customers can configure an AWS KMS customer-managed key to protect supported agreement files at rest. After the feature is enabled for an account, supported agreement files are encrypted using the customer-managed key, giving organizations more control over key management while preserving supported Acrobat Sign agreement workflows.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account only
Resolved Issues
| Issue | Description |
|---|---|
| 4487069 | Summary: Undelivered notification on the Manage page could disappear while users scrolled through agreements because the agreement list reused row components and didn’t refresh the notification state for each agreement. |
| Fix: The Manage page now refreshes the undelivered notification state when agreement rows are reused, so the notification remains visible while users scroll. | |
| 4541319 | Summary: Embedded hyperlinks in reusable template previews could become inactive because PDF processing removed the embedded link data during template conversion, while exposed URL links remained clickable. |
| Fix: PDF processing was updated to preserve embedded hyperlink data during reusable template conversion, so embedded and exposed URL links remain clickable in template preview. | |
| 4555107 | Summary: Combined document API downloads could omit the audit report even when attachAuditReport=true was used because some requests were incorrectly handled as unauthenticated when API action ID generation failed. |
| Fix: The combined document API now preserves the requested audit report attachment when API action ID generation is unavailable, so downloads include the audit report when attachAuditReport=true is used. | |
| 4555473 | Summary: Safari users could be returned to the login page after signing in because newer Safari privacy handling prevented Adobe Acrobat Sign session cookies from being retained correctly during the Adobe identity sign-in flow. |
| Fix: Session cookie compatibility handling was updated for newer Safari and macOS versions, so Acrobat Sign keeps users signed in after login. | |
| 4555620 | Summary: Large file uploads could be rejected when sending from a group with a higher max upload size because transient document upload validation did not load the selected group’s upload-size setting. |
| Fix: Transient document uploads now pass the selected group ID so Acrobat Sign applies the group’s max upload size when validating uploaded files. | |
| 4560927 | Summary: Completed agreement recipients could receive unexpected completion emails when the sender requested a new link from an expired agreement email because the URL renewal flow misclassified the sender confirmation email as a signer notification template. |
| Fix: The URL renewal flow now sends the requested access link only to the user who requested it and no longer sends completion emails to other agreement participants. | |
| 4561378 | Summary: When users created a copy of an agreement and opened authoring, Acrobat Sign could send an incorrect deadline update email because the copied agreement’s automatically applied deadline was treated as a sender-updated expiration before the agreement was sent. |
| Fix: The copy workflow now blocks the initial deadline update email before the copied agreement is sent, while preserving deadline update notifications for later sender changes. | |
| 4562055 | Summary: In the new sending experience, account-level custom workflows could revert the Send from group value to the sender’s primary group because the selected group wasn’t preserved when the workflow page refreshed and recreated the draft agreement. |
| Fix: The custom workflow send flow now preserves the selected group during page refresh and draft agreement creation, so users can send from a non-primary group in the new experience. | |
| 4562242 | Summary: Prefill field values could disappear after an agreement was restarted by a later recipient because the restart workflow used the restarted document as the source instead of the prefilled document that retained the original field defaults. |
| Fix: The restart workflow now uses the prefilled document as the base for the restarted agreement, so original prefill values are preserved when the agreement is sent back for signing. | |
| 4562338 | Summary: Swagger API authentication could stop on a blank redirect page and fail to generate a bearer token because the OAuth redirect page rejected valid Acrobat document-domain URLs during redirect validation. |
| Fix: Swagger OAuth redirect validation was updated to allow supported Acrobat document domains, so authentication returns users to Swagger and loads the generated bearer token. | |
| 4565965 | Summary: Documents with multiple digital signatures could fail validation in strict PDF signature validators because Acrobat Sign temporarily wrote an internal signing workflow value into a signature field where the PDF specification requires a signature dictionary. |
| Fix: The PDF merge process now skips signature fields when applying form values, preventing internal workflow values from being written into signature fields and preserving valid multi-signature document structure. | |
| 4567496 / 4567841 | Summary: Stamp signatures could render smaller than the configured size when signature reason settings were enabled because the signature reason layout logic incorrectly reserved space next to stamp fields. |
| Fix: Stamp rendering was updated so signature reason layout adjustments don’t resize stamp fields, preserving the configured stamp size. | |
| 4568666 | Summary: Webhook notifications could be missed for some agreements with witness participants because participant lookup logic did not safely handle witness records during webhook payload generation. |
| Fix: Webhook payload generation now safely handles witness participants, so webhook notifications continue to generate and send for affected agreements. | |
| 4568798 | Summary: Copied agreements could include recipients that had been removed through Modify Agreement because the copy workflow did not fully exclude deleted recipients when rebuilding the recipient list and routing groups. |
| Fix: The copy workflow now filters out recipients removed through Modify Agreement and rebuilds routing groups using only active recipients. | |
| 4569478 | Summary: Checkbox selections could disappear in completed agreements when an interactive PDF contained an invisible checkbox field layered over a visible checkbox field, because the invisible field was still rendered during final PDF processing. |
| Fix: PDF processing now skips invisible checkbox fields when rendering the completed agreement, so visible checkbox selections remain displayed in the final signed document. | |
| 4569490 | Summary: Some Adobe Acrobat Sign notification emails could be flagged as spam because the email preheader markup included hidden or low-contrast styling patterns that some mail filters treat as suspicious. |
| Fix: Notification email markup was updated to remove the hidden and low-contrast styling patterns, reducing false-positive spam detection while preserving normal email preview behavior. | |
| 4569491 | Summary: The Assign Users to Group flow could fail with an unhandled error when user-status validation encountered an incomplete group membership record. |
| Fix: User-status validation now skips incomplete group membership records instead of stopping the assignment workflow, allowing Assign Users to Group to open successfully. | |
| 4569747 | Summary: Agreements created through the REST API in authoring status could show all checkbox fields as selected because checkbox merge-field values were not correctly interpreted when loading the agreement for authoring. |
| Fix: Checkbox merge-field handling was updated so authoring correctly honors checked and unchecked values from the API payload, displaying only the intended checkbox selections. | |
| 4570171 | Summary: Adobe Acrobat Sign could fail to process some otherwise valid PDFs when the document contained a malformed link destination, because document processing stopped instead of ignoring the broken link. |
| Fix: Document processing now validates link destinations before reading them and skips malformed links, so affected PDFs can be processed and sent successfully. | |
| 4571060 | Summary: Conditional fields linked to dropdown selections could fail when the dropdown used export values that differed from the displayed option labels because Acrobat Sign compared the condition against the wrong dropdown value. |
| Fix: Dropdown condition handling was updated to map displayed option labels to their corresponding export values, so conditional fields appear and retain their values correctly when the signer selects the matching dropdown option. | |
| 4571362 | Summary: Completion emails could fail to send when all SMS delivery attempts for an agreement had bounced because the exhausted SMS delivery event caused audit report generation to fail during completion processing. |
| Fix: Completion processing now handles exhausted SMS delivery events without interrupting audit report generation, so sender and signer completion emails are sent after the agreement is signed. | |
| 4571642 | Summary: Signer names provided through the API could be missing from the agreement response and remain editable during signing when signer name editing was disabled, because the sender-provided name was not preserved for recipients without a profile name. |
| Fix: Recipient name handling now preserves sender-provided names when signer name editing is disabled, so the name is returned in the agreement response and appears prefilled and locked on the signing page. | |
| 4571797 | Summary: Some failed or skipped bulk-signing agreements could not be previewed from Manage because the agreement preview used an intermediate portfolio document instead of reverting to the original agreement document. |
| Fix: Bulk-signing processing now reverts failed or skipped agreements to the previous document version, so the agreements can be opened and previewed from Manage. | |
| 4572223 | Summary: Workflow-created agreements could be automatically canceled during document processing when thumbnail generation completed only partially, causing finalization to fail when the system tried to use a missing page thumbnail. |
| Fix: Document finalization was made more resilient so missing or incomplete thumbnail data is handled gracefully, preventing affected workflow agreements from being automatically canceled. | |
| 4572763 | Summary: In-person signing agreements created through the API could fail to open when the host participant was missing the required authentication setting, and the API documentation did not clearly describe the required in-person signer and host configuration. |
| Fix: The API documentation was updated to describe the required IN_PERSON_SIGNER and HOST roles, matching participation set labels, and host authentication settings needed to create in-person signing agreements successfully through the API. | |
| 4575098 | Summary: Checkbox fields populated through merge data could appear selected in Modern Authoring even when the provided value was "0" because Acrobat Sign interpreted both "0" and "1" string values as checked. |
| Fix: Checkbox merge-field handling was updated so Modern Authoring correctly treats "0" as unchecked and "1" as checked, matching Classic Authoring behavior. | |
| 4578199 | Summary: Audit reports could fail to download for some agreements because an audit event was not handled correctly during audit report generation, causing Adobe Acrobat Sign to return a miscellaneous error. |
| Fix: Audit report generation now handles the affected audit event correctly, so audit reports can be generated and downloaded without the miscellaneous error. | |
| 4578567 | Summary: Safari users in the Adobe Acrobat Sign Sandbox could be redirected back to the login page after signing in because the browser session was not retained correctly after authentication. |
| Fix: Session handling was updated so Acrobat Sign preserves the authenticated Safari session after login. Users may need to clear the existing browser session once after the release. |
Adobe Acrobat Sign release v17.2
Sandbox deployment: August 4, 2026
Production deployment: September 8, 2026
GovCloud deployment: September 15, 2026
Improved Functionality
- Pause and resume agreements after authentication failures - Administrators can now allow agreements to pause when a recipient exceeds the permitted authentication attempts, rather than canceling immediately. Senders can update the recipient’s authentication method and resume the same agreement without requiring completed recipients to sign again.
- Administrators can configure a pause period from 1 to 30 days.
- If the agreement is not resumed before the pause period ends, it is canceled automatically.
- The feature is disabled by default.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Share AI-generated agreement summaries with recipients - Acrobat Sign can generate an AI summary of an agreement during authoring. Senders can review the summary and choose whether to make it available to recipients, based on account or group settings.
Recipients who receive the summary can review it in the signing experience before completing the agreement. After sending, the sender can use Modify Agreement to change whether the existing summary is included.
AI-generated summaries are for informational purposes only. Recipients should review the complete agreement before signing.
The feature is available after the account accepts the applicable Adobe AI terms.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Digital Identity Gateway support for Send in Bulk - Senders can now require Digital Identity Gateway authentication for recipients in Send in Bulk transactions. DIG can be selected in the authoring interface or assigned to individual recipients through the Send in Bulk CSV.
The CSV also supports per-recipient email-matching options, including approved alternate email addresses. Each generated agreement uses the existing DIG authentication and audit process.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Add files from Google Drive - Users can now add supported files directly from Google Drive in the current Request Signatures, Custom Workflow, Send in Bulk, and Create a Library Template experiences.
After authenticating with Google, users can browse and select files through the Google Drive file picker. Native Google Docs are converted to PDF before being added to Acrobat Sign.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Customer-managed encryption keys for agreement files - Eligible Acrobat Sign customers can now use a customer-managed key in AWS Key Management Service to encrypt supported agreement files at rest. Account administrators configure the key and AWS access credentials at the account level.
Access to encrypted files depends on the customer-managed key and credentials remaining available.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account only
- Group-level custom timestamp configuration - Custom timestamp providers can now be configured at the group level. This allows groups within the same account to use different approved timestamp providers for their digital signature workflows.
Groups without an explicit configuration inherit the account-level setting.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Include CC notification events in audit reports - Account and group administrators can now include CC notification events in agreement Audit Reports. When enabled, the Audit Report records initial and completion notifications sent to general and recipient-specific CC addresses.
Administrators can separately include completion notification events for automatic CC addresses. Both settings are disabled by default.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Configure password strength requirements for Government accounts
Acrobat Sign for Government admins can now configure the password strength requirements to adjust the minimum length and character composition rules. This allows organizations to align password policies with their internal security standards and compliance requirements.
Available environments: Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- Improved accessibility for uploaded PDFs - Administrators can enable automatic accessibility tagging for supported uploaded PDFs.
Acrobat Sign adds structural tags that improve screen-reader and keyboard navigation and preserves those tags in the completed agreement.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Sort and export reporting chart data - Reporting users can now sort supported Agreement and Transaction report charts by activity and export the aggregated chart data to CSV. The exported file respects the report’s active filters and time interval.
The enhancement is available for charts showing agreements or transactions by sender, group, or workflow.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
- New Trust Service Providers - Acrobat Sign regularly adds support for new trust service providers. The following TSPs are newly available in this release:
- Swisscom ZertES CH
- Swisscom eIDAS EU
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
Experience Changes
- Improved library template experience - The library template creation and authoring experience has been streamlined with fewer upfront choices, clearer first-use guidance, a dedicated save action, and improved validation and error messages.
Template-management actions are also easier to access after creation.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Improved form field detection - Automatic form field detection in Acrobat Sign has been updated to improve the accuracy of detected fields and reduce incorrect field placement during authoring.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default
- Improved user-list exports for large accounts - Acrobat Sign now processes large user-list exports asynchronously, improving reliability for accounts with extensive user populations.
Administrators continue to start exports from the existing Users page.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Enabled by default
- Default settings updated for new small business accounts - Several existing sending features are now enabled by default for new VIP, VIPMP, and ETLA accounts under $100K.
These default setting updates make commonly used sender capabilities available without requiring an administrator to enable each setting first. Depending on account configuration, new accounts may now have access to document expiration, additional recipient roles, additional recipient authentication methods, SMS and WhatsApp delivery, private recipient messages, and multi-signer web forms by default.
These changes apply only to new accounts in the targeted commercial customer segments. They do not apply to Acrobat Sign for Government.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Enabled by default
- Modern Request Signature becomes default – Retire Classic Compose, remove switch controls, standardize signing experience
All accounts are now transitioned to the modern Request Signature experience, replacing the classic Compose interface. Switch links and admin controls to revert to the classic experience are removed for commercial accounts, while GovCloud accounts are also transitioned with temporary retention of admin controls. This change standardizes the sending experience across environments and simplifies user onboarding ahead of full Classic retirement.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Not configurable
- Modern Create Template becomes default – Promote new authoring experience, expand rollout, maintain admin controls
The modern Create Template experience is now the default for all accounts, including those that share assets across multiple groups. This update expands the rollout of the new authoring interface, ensuring all users benefit from ongoing enhancements, while retaining admin controls to revert to the classic experience if needed.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Easier access to Acrobat Sign trials for existing Adobe users - Users whose email address is already associated with an Adobe organization can now start an Acrobat Sign trial without being blocked by their existing Adobe account.
This makes it easier for current Adobe customers to evaluate Acrobat Sign alongside their existing products.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Improved recipient removal for in-progress agreements - The recipient-removal experience now supports additional form-field configurations in sequential agreements, reducing cases where a sender must cancel and recreate an agreement.
The existing recipient-removal workflow and administrator controls are unchanged.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Standard, Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Account and Group
- Power Automate Embed retirement notice - Users with access to Power Automate Embed now see an in-product notice about its upcoming retirement and a link to transition guidance. The feature remains available in release 17.2, and this update does not disable or remove existing workflows.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group
Integration Updates
- Increased file-size support for Salesforce transactions - The Acrobat Sign for Salesforce integration now supports larger transaction payloads, improving reliability for agreements with large documents, multiple signers, or signed PDFs saved as separate Salesforce attachments.
Existing Salesforce workflows and settings remain unchanged.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration
- Control recipient names in Salesforce agreements - Acrobat Sign for Salesforce now allows senders to provide a recipient’s name and prevent the recipient from changing it during signing.
The enhancement improves consistency between Salesforce records and completed agreements.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration
- SAP SuccessFactors integration compatibility update - The Acrobat Sign integration with SAP SuccessFactors has been updated to remain compatible with changes to the SAP SuccessFactors platform.
Existing agreement workflows remain unchanged.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration
- Improved offer tracking in SAP SuccessFactors - The Acrobat Sign integration with SAP SuccessFactors now provides Expired and Approval offer statuses, giving recruiters clearer visibility into offer progress.
A new Actor field in the Job Application entity identifies the candidate or approver responsible for the next action. This helps recruiters determine where an offer is waiting without contacting an SAP administrator.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Integration
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.
Release errata
There are no items that have slipped from this release as of this time.
Resolved Issues
| Issue | Description |
|---|---|
| 4550652 | Summary: Users viewing a shared Send in Bulk transaction could select Download Completed Agreements, but the download failed with a permissions error because the action is supported only for the original sender. Fix: The Manage page now hides Download Completed Agreements from users viewing a shared bulk send. The action remains available to the original sender. |
| 4559237 | Summary: When a recipient used a cloud signature, the signer's name could remain set to the sender's incorrect value rather than updating from the signing certificate, due to a saved signature from an earlier signing session. Fix: Cloud signature processing has been updated so the signer name is populated from the selected signing certificate, even when the recipient has a previously saved signature. |
| 4561749 | Summary: Descriptions on second-row Home page banner cards could appear clipped because updated text-sizing standards were applied to a layout that had not been adjusted for the new dimensions. Fix: The banner card layout has been updated to accommodate the revised text sizing, ensuring descriptions are not cut off. |
| 4561980 | Summary: Text entered through Fill & Sign could appear missing, enlarged, or misaligned in the completed PDF due to differences in how substituted fonts and text spacing were processed during document rendering. Fix: PDF rendering has been updated to preserve the intended font sizing, spacing, and placement, ensuring entered data appears correctly in the completed document. |
| 4561987 | Summary: Individual documents downloaded from a completed agreement can become significantly larger than their originals due to excessive data added during the generation of accessible versions of signed PDFs. The increased size could also cause agreement emails to exceed delivery limits. Fix: Accessible PDF processing has been optimized to prevent unnecessary file-size growth when agreements contain multiple documents. Individual downloaded documents now retain a size more consistent with their original content. |
| 4562483 | Summary: Some existing library templates failed to open in the modern template experience and displayed a “Something went wrong” error because the template contained field data without the recipient assignment information expected during loading. Fix: Template loading has been updated to handle incomplete recipient assignment data correctly, allowing affected templates and their form fields to open in the modern template experience |
| 4567869 | Summary: Agreements containing PDFs with incorrectly formatted font data could remain stuck on a loading screen and fail to complete due to an endless processing loop during document rendering. Fix: PDF processing has been updated to detect and safely handle malformed font-width data, preventing the rendering process from stalling and allowing affected agreements to be sent and signed. |
| 4568289 | Summary: Agreement senders who replaced themselves as recipients could not hide the completed agreement because a permissions check treated the original sender as a replaced participant. Fix: Permission validation has been updated so the original sender can hide the agreement even after replacing themselves as a recipient, without changing visibility permissions for other users. |
| 4569692 | Summary: Email addresses in a recipient group could appear extremely small in the signature block because the full group address list was used to calculate the field’s text size. Fix: Signature block rendering has been updated to recalculate the email field after a group member opens or signs the agreement, so the active signer’s address displays at a readable size in the signing experience and completed PDF. |
| 4571461 | Summary: Landscape-oriented documents used in web forms could contain unexpected blank areas and misplaced fields due to incorrect page-coordinate calculations during document processing. Fix: Document processing has been updated to calculate field placement and covered areas correctly on rotated and landscape pages, preventing blank spaces and misaligned fields in generated agreements. |
| 4574423 | Summary: Radio button groups with the same field name in merged reusable templates were not kept in sync because selecting an option cleared the corresponding selection in the other group. Fix: Radio button behavior has been updated so matching options in fields with the same name are selected together across merged templates, while different options remain unchanged. |
| 4574867 | Summary: Custom signing date formats created in Acrobat Web reverted to the default date format because the selected display format was not preserved when form fields were removed and recreated during agreement processing. Fix: Agreement processing has been updated to preserve custom date display formats when form fields are recreated, ensuring the signing experience uses the format selected in the original template. |
| 4575022 | Summary: Signers using phone authentication could not delegate an agreement from the modern signing experience because the delegation dialog did not collect the new recipient’s phone number. Fix: The delegation dialog now displays and validates a phone number field for phone-authenticated agreements, uses the supported country-code list, and passes the number to the delegated recipient’s authentication request. |
| 4575850 | Summary: Text in large, locked multiline fields could appear smaller in the signing experience and completed agreement because the field’s existing appearance was replaced by an unnecessary font-size recalculation. Fix: Multiline field rendering has been updated to preserve the existing text appearance when the content already fits, preventing the font from shrinking unnecessarily. |
| 4576211 | Summary: Senders received two completion emails when their address was also configured to receive an extra copy because both the sender and automatic-copy notification paths were triggered for the same recipient. Fix: Completion email processing has been updated to evaluate the sender and automatic-copy rules together, preventing duplicate messages while preserving cases where separate notifications are expected. |
| 4576609 | Summary: Senders using a custom workflow could lose access to group-shared templates after returning from authoring and previewing again because the second validation path did not recognize templates shared with the sender’s group. Fix: Template access validation has been aligned across the preview and send paths so users can continue using templates shared directly with them or with their group throughout the custom workflow. |
| 4576624 | Summary: Signature fields in agreements with an in-person signer and additional participants could become reassigned or overlap after the sender returned from authoring because participant identifiers changed when the draft agreement was rebuilt. Fix: Draft agreement processing has been updated to remap each field to the corresponding participant after returning from authoring, preserving the correct assignments across supported routing and recipient-role combinations. |
| 4576876 | Summary: Required signature fields hidden by conditional logic still counted as incomplete due to an error in how the signing experience recalculated required fields, preventing signers from completing the agreement. Fix: Required-field processing has been updated so hidden signature fields no longer count as incomplete, allowing signers to complete agreements when conditional rules remove those fields from view. |
| 4576961 | Summary: Agreement senders who were also signers did not receive the completed agreement email because the notification workflow excluded the sender from the signer notification path. Fix: Completion email processing has been updated, so senders who also sign the agreement receive the completed notification when their notification settings allow it. |
| 4577135 | Summary: Replacing a web form recipient updated the email address but retained the original recipient’s name due to incomplete synchronization of the replacement details. The incorrect name could appear to the signer and in the audit report. Fix: Web form recipient replacement has been updated to apply the new recipient’s name consistently across the agreement, signing experience, and audit data. |
| 4577475 | Summary: Agreements created from templates could display a transaction footer after the setting was disabled because the template retained the footer state from when it was originally created. Fix: Transaction footer processing has been updated to evaluate the current setting when the agreement is generated, rather than relying on the value stored with the template. |
| 4577531 |
Summary: Some document names in the transaction footer were truncated because specific character spacing caused the final words to wrap beyond the visible footer area. Fix: The transaction footer now uses a narrower font for document names, allowing more text to fit without wrapping or being cut off. |
| 4578623 / 4579255 |
Summary: Some AcroForm PDF fields appeared twice in authoring because document processing added a second overlapping field for certain existing form fields. Fix: PDF form-field processing has been updated to prevent duplicate overlapping fields from being added, so each field appears once in authoring, and signers are prompted only once. |
| 4580019 | Summary: The Download, Print, and Search buttons in the agreement-viewing experience lacked accessible names, preventing screen readers from identifying their purpose. Fix: Accessible names have been added to the Download, Print, and Search buttons so assistive technologies can announce each action correctly. |
| 4581229 | Summary: Changes to the security setting that prevent Acrobat Sign from being embedded in third-party websites were missing from the Settings Activity Report because the setting was not categorized for administrative reporting. Fix: The setting has been added to the Security Settings reporting category, so account- and group-level changes are recorded in the Settings Activity Report. |
| 4582044 | Summary: Cloned checkbox fields could move or overlap after signing because they were rotated unnecessarily during the processing of certain PDF page configurations. Fix: Cloned checkbox processing has been updated to preserve the original field orientation and position, preventing the fields from shifting after participants sign. |
| 4582268 | Summary: Webhook API requests made directly to the webhooks endpoint may receive the default API throttling limits rather than the webhook-specific limits because the base endpoint was not included in the webhook policy mapping. Fix: Webhook throttling has been updated so requests to both the base endpoint and individual webhook endpoints consistently use the intended webhook-specific rate limits. |
| 4582742 | Summary: Updating a participant set could fail with a “more than one participant” error after a previous replacement because the API counted an already replaced recipient when evaluating the active participant set. Fix: Participant-set updates now exclude previously replaced recipients when determining how many active participants are being changed, allowing the recipient email to be updated successfully. |