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
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
- 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
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.
Documentation
Documentation for release notifications and new/updated content is typically published as follows:
- 6-8 weeks before the production release (typically four weeks before the Sandbox launch), a summary of the expected features and updates is published on this prerelease page.
- If features are added or removed from the release after this point, they are noted in the Errata section at the bottom of the page.
- Resolved issues are not published at this time.
- If features are added or removed from the release after this point, they are noted in the Errata section at the bottom of the page.
- 2-4 weeks before the production release (typically in alignment with the Sandbox launch), this prerelease page is updated with links to complete documentation of all new features and updated content.
- Links to the prerelease support documentation are provided on this page as needed. Prerelease documentation is in US English only.
- The first draft of the Resolved issues section is added. Resolved issues will likely change and be updated throughout the next four weeks.
- Links to the prerelease support documentation are provided on this page as needed. Prerelease documentation is in US English only.
- Launch day, the official release notes are updated to reflect the newly published features and updates with links to the production support documentation. This prerelease page is updated to remove the launched content and showcase the next release.
- The documentation is published after the release is complete, and functionality is verified in the live system. This takes a variable amount of time, depending on the amount and complexity of the new content. The official publication should not be expected before 7pm Pacific time and may be significantly later.
- The complete list of Resolved issues is updated in the US English version of the release notes. Localized versions may have out-of-sync data due to localization.
- Government Cloud updates typically happen one or more weeks after the production release. Due to the nature of the government environment, some features may need additional evaluation before enabling them.
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: January 14, 2025
Production deployment: February 11, 2025
GovCloud deployment: February 18, 2025
Improved Functionality
- Improved user interface for Custom Send Workflows - The Custom Workflow Designer has been updated to provide a better sender experience that aligns with the Request Signature look and feel.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Group, Account
Review the updated documentation >
Experience Changes
- Agreement expiration may be delayed up to 12 hours - Starting with this release, the automatic expiration of an agreement will take place during non-peak hours for the environment that is managing the agreement. In practice, any agreement that expires during the peak traffic times of any given Acrobat Sign environment will be queued to execute once the environment enters the non-peak time window.
- Workday: Digital Signature support for the Aadhaar Identity Provider - Customers using the Workday integration can now use the Aadhaar Identity Provider as a method to authenticate their recipients.
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.
- A new accountId attribute is being added to all event notification payloads.
- OEM Embed 2.0 partners will now be able to set up a webhook for their channel and listen in to all the asset notifications from each of their individual customer accounts.
- New Settings APIs
- POST /accounts/{accountId|me}/settings/search – Takes the identified account (accountId) and a list of setting names and returns the list of setting names with their values for the account specified. Only account-level values are returned.
- Available to non-admin users.
- PUT /accounts/{accountId|me}/settings - Applies a provided list of setting names and their values to the identified account (accountId).
- POST /accounts/{accountId|me}/settings/search – Takes the identified account (accountId) and a list of setting names and returns the list of setting names with their values for the account specified. Only account-level values are returned.
- New Logo APIs
- POST /accounts/{accountId|me}/logo - Uploads the CoBrandingLogo file.
- GET /accounts/{accountId|me}/logo - Returns the image data of the CoBrandingLogo image file in the same format that it was uploaded.
- Available to non-admin users
- DELETE /accounts/{accountId|me}/logo – Clears the CoBrandingLogo image for the account.
- Signing Reason APIs
- GET /accounts/{accountId|me}/signingReasons - Returns a list of signing reasons for the identified account (accountId).
- Available to non-admin users.
- POST /accounts/{accountId|me}/signingReasons - Creates a new signing reason for the identified account (accountId).
- GET /accounts/{accountId|me}/signingReasons/{signingReasonId} - Retrieves the text of the identified signing reason (signingReasonId) from the identified account (accountId). account's identified signing reason.
- Available to non-admin users
- PUT /accounts/{accountId|me}/signingReasons/{signingReasonId} - Updates the identified signing reason (signingReasonId) from the identified account (accountId).
- DELETE /accounts/{accountId|me}/signingReasons/{signingReasonId} - Removes the identified signing reason (signingReasonId) from the identified account (accountId).
- GET /accounts/{accountId|me}/signingReasons - Returns a list of signing reasons for the identified account (accountId).
- Updated swagger pages to indicate me as a shorthand for the accountId.
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.
- Recipient Agreement Access - Senders have the option to configure a recipient's settings and flag the recipient as "Private". When enabled, this option treats the recipient as if they do not have a registered userID and tracks the recipient's activities using a "single-use recipient" (just like any recipient without a registered Acrobat Sign user). In effect, this means that the agreement is not published to the user's Manage page (because it's not linked to the recipient's registered UserID). This is ideal for accounts or groups that send private internal agreements that should not be on the Manage page if the user (or the group the user is in) is shared with some other user or group. Offer letters for example.
Resolved Issues
Issue | Description |
---|---|
4479949 | Summary: An OIDC API calls to an IDP contain the "charset=UTF-8" parameter in the "Content-type:application/x-www-form-urlencoded" header. This generates an error instead of a valid response. |
Fix: The charset was removed as no charset should be specified. | |
4490523 | Summary: A button to print the PDF is not available on the Read Agreement view. |
Fix: A print button has been added to the Read Agreement view. | |
4494248 | Summary: Incorrect Agreement Expiration Times in the agreement due to the client not passing timezone information. |
Fix: The client has been updated to be timezone-aware. | |
4494297 | Summary: When a user delegates an agreement on behalf of another user (using advanced account sharing), the audit report may not show the event of the delegation based on configured settings that omit or include data. |
Fix: The function that omits data has been improved to account for situations where events take place that suppress some content, but retain the event. | |
4495537 | Summary: Recipients get cancellation emails as CC'd participants when an agreement is sent via Workflow and subsequently canceled without the request to notify all parties when custom email templates are used. |
Fix: The CSS for the CEMT templates has been updated to manage cancelation scenarios like non-custom templates do. | |
4495963 | Summary: If delegation is disallowed for users in the account, the options to enable signing or e-sealing for a user profile is locked. |
Fix: Dependency of delegation is removed in the UI and the setting can be updated | |
4496084 / 4510358 | Summary: The correct selected radio button is not being set when the radio button is specified with an options list |
Fix: When the option list is present in a radio button, we now get the selected radio button index from the list of options. | |
4497823 | Summary: User message (“Invalid agreement id”) for a non-participating user session in the browser for GET /SigningUrls for a valid agreement. |
Fix: Rephrase the user notification (“Invalid agreement ID”) to a meaningful message. | |
4498914 / 4501065 | Summary: Users are not able to sign the document when the authentication type is Acrobat sign with bio pharma settings enabled due to an incorrect delimiter. |
Fix: The delimited being used has been corrected. | |
4499847 | Summary: The Digital settings are not honoring the UI settings, showing more providers than have been selected due to duplicate entries in the providers' list. |
Fix: Cleanup code has been added to ensure duplicates are cleared before fetching the setting value, and before updating the setting value. | |
4500637 | Summary: The creation data of a pdf is represented with a long value that is the milliseconds of Date, rather than using PDF date string format. |
Fix: In the case that the Creation Date is represented by a CosNumeric, convert it to an ASDate by getting the CosNumeric as a String and then converting it to a long and then to Date object. | |
4500649 | Summary: Auto-adjustment for font size is not functioning due to a bug in an upstream library |
Fix: The library has been updated. | |
4501417 | Summary: When using the modern Send experience, applying only an e-seal field to a template generates and error, and the field isn't placed. |
Fix: The error code functions have ebene updated to identify the e-seal as a valid placement without a designated recipient and will allow the placement of the field. | |
4501939 | Summary: "Unexpected error" or "permission error" when the signer is making payment via Braintree due to unsupported configuration with AVS. |
Fix: Some code has been added to ignore AVS where possible. Customers are cautioned that AVS configuration is incompatible with Acrobat Sign. | |
4502497 | Summary: Initial field not set to Required by default in New Authoring layout |
Fix: The default has been edited to be required. | |
4502759 | Summary: Duplicated Japanese honorifics for Signers in Audit Report |
Fix: We now use the user list string in all cases in createSignatureRequestedAuditEvent(). This will be accompanied by a string change where the honorific character is removed from all audit event strings used in the function. | |
4503010 | Summary: Action GET /agreements/ID fails with 500 - Miscellaneous server error for a few agreements after September 17 due to an origin check. |
Fix: The origin check has been removed. | |
4503107 | Summary: When a sharee with SEND and SIGN permissions switches to the sharer's account and initiates a workflow where the sharer is the first signer, the user is redirected to the POST_SIGN page instead of the ESIGN page. |
Fix: The in-place check has been updated to ensure that sharee has SIGN permissions for the group from which the agreement was sent are being used. | |
4503112 | Summary: Auto-Cancellation of agreement - error AUTO_AUTHOR_FAIL due to an iText error. |
Fix: iText has been removed where unrequited, resolving the error. | |
4503640 | Summary: Form filler is unable to submit the document. Server error is seen after user clicks on 'Submit' on XFA documents |
Fix: The library that evaluates PDFs for XFA has been improved to properly identify and remove XFA. | |
4504309 | Summary: Unable to send Draft folder agreements via Advanced Account Sharing due to missing endpoint in the filter. |
Fix: Added the URL /account/requestSignatures/authoring in allowListedEndPointsBasedOnSendPermissions in filter.xml | |
4504567 | Summary: Radio button values are being changed when agreements are generated via bulk send |
Fix: Replaced the hashmap with linkedhashmap to maintain order of insertion when creating SiB child agreements | |
4504631 | Summary: Processing workflow error Error message: Unhandled Error due to unsupported characters in an iText file |
Fix: iText has been updated. | |
4504822 | Summary: User Search is cleared if User list is taking too large, and a search is requested before a previous search is completed (such as the initial loading of users when the page is opened) |
Fix: When data is received, we check if the requestID matches the most recent request. If it does, we process the response, if it doesn’t, we ignore it. | |
4504831 / 4507199 | Summary: Signed agreement provides an invalid PDF 1kb in size due to a malformed PDFFont object that does not specify the required subtype of the font object. |
Fix: The PDF-generating library has been updated to better manage malformed objects and provide a more graceful result. | |
4506230 | Summary: Automatic Field recognition not working in Sandbox due to the annotation either being wrong or absent where we are looking for it. |
Fix: We now seaarch each page and each annotation on that page to find the annotation of the form field to ensure we get the correct page. | |
4506959 | Summary: Post-Sign Landing Page is showing HTML encoded characters |
Fix: Fixed source template. | |
4509503 | Summary: Users are unable to sign documents through the Acrobat Sign application iOS due to a datafield being empty and throwing a null pointer exception |
Fix: A null pointer check has been added to gracefully manage the circumstance. | |
4509713 | Summary: Setting "Allow all users to share library documents with multiple groups" is being auto enabled when trying to enable "Allow administrator to share library documents with multiple groups" from Global settings due to an incorrect value being passed. |
Fix: The correct value is now being used. | |
4510812 | Summary: Aadhaar authentication in Workday is preventing signatures. |
Fix: Aadhaar authentication support has bene added to Workday. | |
4512044 | Summary: Modern esign throws error if the field name has a special character |
Fix: Field name parsing has been improved to gracefully manage special characters in field names. |
Sandbox deployment: February 18, 2025
Production deployment: March 18, 2025
GovCloud deployment: March 20, 2025
Improved Functionality
- Send in Bulk download increased to 1.5 GB - Customers that use the option to Download Completed Agreements generated through the Send in Bulk process can now download up to 1.5 GB of data per download request.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Pro, Acrobat Sign Solutions | Configuration scope: Group, Account
The April 2025 release is a major release containing features, updates, and fixes for customer-reported issues.
- Sandbox release: March 25, 2025
- Production release: April 22, 2025
- GovCloud release: April 24, 2025