User Guide Cancel

Technical notifications

Search
Adobe Sign

Adobe Sign

Open app

 

Adobe Acrobat Sign Guide

What's New

  1. Pre-Release Notes
  2. Release Notes
  3. Important Notifications

Get Started

  1. Quick start guide for administrators
  2. Quick start guide for users
  3. For Developers
  4. Video tutorial library
  5. FAQ

Administer

  1. Admin Console Overview
  2. User Management
    1. Adding users
      1. Add a User
      2. Add Users in Bulk
      3. Add Users from your Directory
      4. Add Users from MS Azure Active Directory
    2. Create function-focused users
      1. Technical accounts - API driven
      2. Service accounts - Manually driven
    3. Check for users with provisioning errors
    4. Change Name/Email Address
    5. Edit a user's group membership
    6. Edit a user's group membership through the group interface
    7. Promote a user to an admin role
    8. User Identity Types and SSO
    9. Switch User Identity
    10. Authenticate Users with MS Azure
    11. Authenticate Users with Google Federation
    12. Product Profiles
    13. Login Experience 
  3. Account/Group Settings
    1. Settings Overview
    2. Global Settings
      1. Account tier and ID
      2. New Recipient Experience
      3. Self Signing Workflows
      4. Send in Bulk
      5. Web Forms
      6. Custom Send Workflows
      7. Power Automate Workflows
      8. Library Documents
      9. Collect form data with agreements
      10. Limited Document Visibility
      11. Attach a PDF copy of the signed agreement 
      12. Include a link in the email
      13. Include an image in the email
      14. Files attached to email will be named as
      15. Attach audit reports to documents
      16. Merge multiple documents into one
      17. Download individual documents
      18. Upload a signed document
      19. Delegation for users in my account
      20. Allow external recipients to delegate
      21. Authority to sign
      22. Authority to send
      23. Power to add Electronic Seals
      24. Set a default time zone
      25. Set a default date format
      26. Users in Multiple Groups (UMG)
        1. Upgrade to use UMG
      27. Group Administrator Permissions
      28. Replace recipient
      29. Audit Report
        1. Overview
        2. Allow unauthenticated access on the transaction verification page
        3. Include reminders
        4. Include view events
        5. Include agreement page/attachment count
      30. Transaction Footer
      31. In Product Messaging and Guidance
      32. Accessible PDFs
      33. New authoring experience
      34. Healthcare customer
    3. Account Setup
      1. Add logo
      2. Customize company Hostname/URL    
      3. Add company name
      4. Post agreement URL redirect
    4. Signature Preferences
      1. Well formatted signatures
      2. Allow recipients to sign by
      3. Signers can change their name
      4. Allow recipients to use their saved signature
      5. Custom Terms of Use and Consumer Disclosure
      6. Navigate recipients through form fields
      7. Restart agreement workflow
      8. Decline to sign
      9. Allow Stamps workflows
      10. Require signers to provide their Title or Company
      11. Allow signers to print and place a written signature
      12. Show messages when e-signing
      13. Require signers to use a mobile device to create their signature
      14. Request IP address from signers
      15. Exclude company name and title from participation stamps
      16. Apply Adaptive Signature Draw scaling
    5. Digital Signatures
      1. Overview
      2. Download and sign with Acrobat
      3. Sign with Cloud Signatures
      4. Include metadata for Identity Providers
      5. Restricted Cloud Signatures Providers
    6. Electronic Seals
    7. Digital Identity
      1. Digital Identity Gateway
      2. Identity Check policy
    8. Report Settings
      1. New report experience
      2. Classic report settings
    9. Security Settings
      1. Single Sign-on settings
      2. Remember-me settings
      3. Login password policy
      4. Login password strength
      5. Web session duration
      6. PDF encryption type
      7. API
      8. User and group info access
      9. Allowed IP Ranges
      10. Account Sharing
      11. Account sharing permissions
      12. Agreement sharing controls
      13. Signer identity verification
      14. Agreement signing password
      15. Document password strength
      16. Block signers by Geolocation
      17. Phone Authentication
      18. Knowledge-Based Authentication (KBA)
      19. Allow page extraction
      20. Document link expiration
      21. Upload a client certificate for webhooks/callbacks
      22. Timestamp
    10. Send Settings
      1. Show Send page after login
      2. Require recipient name when sending
      3. Lock name values for known users
      4. Allowed recipient roles
      5. Allow e-Witnesses
      6. Recipient groups
      7. CCs
      8. Recipient Agreement Access
      9. Required fields
      10. Attaching documents
      11. Field flattening
      12. Modify Agreements
      13. Agreement name
      14. Languages
      15. Private messages
      16. Allowed signature types
      17. Reminders
      18. Signed document password protection
      19. Send Agreement Notification through
      20. Signer identification options
        1. Overview
        2. Signing password
        3. Knowledge-based authentication
        4. Phone authentication
        5. WhatsApp authentication
        6. One-Time Password via Email
        7. Acrobat Sign authentication
        8. Cloud-based digital signature
        9. Government ID
        10. Signer Identity reports
      21. Content Protection
      22. Enable Notarize transactions
      23. Document Expiration
      24. Preview, position signatures, and add fields
      25. Signing order
      26. Liquid mode
      27. Custom workflow controls
      28. Upload options for the e-sign page
      29. Post-sign confirmation URL redirect
    11. Message Templates
    12. Bio-Pharma Settings
      1. Overview
      2. Enforce identity authentication
      3. Signing reasons
    13. Workflow Integration
    14. Notarization Settings
    15. Payments Integration
    16. Signer Messaging
    17. SAML Settings
      1. SAML Configuration
      2. Install Microsoft Active Directory Federation Service
      3. Install Okta
      4. Install OneLogin
      5. Install Oracle Identity Federation
    18. Data Governance
    19. Time Stamp Settings
    20. External Archive
    21. Account Languages
    22. Email Settings
      1. Email header/footer images
      2. Permit individual user email footers
      3. Customize the Signature Requested email
      4. Customize the To and CC fields
      5. Enable Linkless Notifications
      6. Customize email templates
    23. Migrating from echosign.com to adobesign.com
    24. Configure Options for Recipients
  4. Guidance for regulatory requirements
    1. Accessibility
      1. Accessibility Compliance
      2. Create accessible forms with Acrobat desktop
      3. Create accessible AcroForms
    2. HIPAA
    3. GDPR
      1. GDPR Overview
      2. Redact a user
      3. Redact a user's agreements    
    4. 21 CFR part 11 and EudraLex Annex 11
      1. 21 CRF part 11 validation pack
      2. 21 CFR and EudraLex Annex 11 handbook
      3. Analysis of shared responsibilities
    5. Healthcare customers
    6. IVES support
    7. "Vaulting" agreements
    8. EU/UK considerations
      1. EU/UK Cross-border transactions and eIDAS
      2. HMLR requirements for deeds signed electronically
      3. The impact of Brexit on e-signature laws in the UK
  5. Download Agreements in Bulk
  6. Claim your domain 
  7. Report Abuse links
  8. System Requirements and Limitations
    1. System requirements
    2. Transaction limits

Send, Sign, and Manage Agreements

  1. Recipient Options
    1. Cancel an email reminder
    2. Options on the e-signing page
      1. Overview of the e-sign page
      2. Open to read the agreement without fields
      3. Decline to sign an agreement
      4. Delegate signing authority
      5. Restart the agreement
      6. Download a PDF of the agreement
      7. View the agreement history
      8. View the agreement messages
      9. Convert from an electronic to a written signature
      10. Convert from a written to an electronic signature 
      11. Navigate the form fields
      12. Clear the data from the form fields
      13. E-sign page magnification and navigation
      14. Change the language used in the agreement tools and information
      15. Review the Legal Notices
      16. Adjust Acrobat Sign Cookie Preferences
  2. Send Agreements  
    1. Send (Compose) page
      1. Overview of landmarks and features
      2. Group selector
      3. Adding files and templates
      4. Agreement name
      5. Global Message
      6. Completion Deadline
      7. Reminders
      8. Password protect the PDF
      9. Signature type
      10. Locale for the recipient
      11. Recipient signature order/flow
      12. Recipient roles
      13. Recipient authentication
      14. Private message for the recipient
      15. Recipient agreement access
      16. CC'd parties
      17. Identity check
    2. Send an agreement only to yourself
    3. Send an agreement to others
    4. Written Signatures
    5. Recipient signing order
    6. Send in Bulk
      1. Overview of the Send in Bulk feature
      2. Send in Bulk - Configure a parent template
      3. Send in Bulk - Configure the CSV file
      4. Cancel a Send in Bulk transaction
      5. Add reminders to Send in Bulk
      6. Reporting for Send in Bulk
  3. Authoring fields into documents
    1. In-app authoring environment
      1. Automatic field detection
      2. Drag and drop fields using the authoring environment
      3. Assign form fields to recipients
      4. The Prefill role
      5. Apply fields with a reusable field template
      6. Transfer fields to a new library template
      7. Updated authoring environment when sending agreements
    2. Create forms with text tags
    3. Create forms using Acrobat (AcroForms)
      1. AcroForm creation
      2. Creating accessible PDFs
    4. Fields
      1. Field types
        1. Common field types
        2. E-signature fields
        3. Initials field
        4. Recipient name field
        5. Recipient email field
        6. Date of signing field
        7. Text field
        8. Date field
        9. Number field
        10. Checkbox
        11. Radio button
        12. Drop-down menu
        13. Link overlay
        14. Payment field
        15. Attachments
        16. Participation stamp
        17. Transaction number
        18. Image
        19. Company
        20. Title
        21. Stamp
      2. Field content appearance
      3. Field validations
      4. Masked fields values
      5. Setting show/hide conditions
      6. Calculated fields 
    5. Authoring FAQ
  4. Sign Agreements
    1. Sign agreements sent to you
    2. Fill & Sign
    3. Self-signing
  5. Manage Agreements
    1. Manage page overview
    2. Delegate agreements
    3. Replace Recipients
    4. Limit Document Visibility 
    5. Cancel an Agreement 
    6. Create new reminders
    7. Review reminders
    8. Cancel a reminder
    9. Access Power Automate flows
    10. More Actions...
      1. How search works
      2. View an agreement
      3. Create a template from an agreement
      4. Hide/Unhide agreements from view
      5. Upload a signed agreement
      6. Modify a sent agreement's files and fields
      7. Edit a recipient's authentication method
      8. Add or modify an expiration date
      9. Add a Note to the agreement
      10. Share an individual agreement
      11. Unshare an agreement
      12. Download an individual agreement
      13. Download the individual files of an agreement
      14. Download the Audit Report of an agreement
      15. Download the field content of an agreement
  6. Audit Report
  7. Reporting and Data exports
    1. Overview
    2. Grant users access to reporting
    3. Report charts
      1. Create a new report
      2. Agreement Reports
      3. Transaction Reports
      4. Settings Activity Report
      5. Edit a report
    4. Data Exports 
      1. Create a new data export
      2. Web form data export
      3. Edit a data export
      4. Refresh the data export content
      5. Download the data export
    5. Rename a report/export
    6. Duplicate a report/export
    7. Schedule a report/export
    8. Delete a report/export
    9. Check Transaction Usage

Advanced Agreement Capabilities and Workflows

  1. Webforms 
    1. Create a web form
    2. Edit a web form
    3. Disable/Enable a web form
    4. Hide/Unhide a web form
    5. Find the URL or script code 
    6. Prefill web form fields with URL parameters
    7. Save a web form to complete later
    8. Resize a web form
  2. Reusable Templates (Library templates) 
    1. US Government forms in the Acrobat Sign library
    2. Create a library template
    3. Change a library template's name
    4. Change a library template's type
    5. Change a library template's permission level
    6. Copy, edit, and save a shared template
    7. Download the aggregate field data for a library template
  3. Transfer ownership of web forms and library templates
  4. Power Automate Workflows 
    1. Overview of the Power Automate integration and included entitlements
    2. Enable the Power Automate integration
    3. In-Context Actions on the Manage page
    4. Track Power Automate usage
    5. Create a new flow (Examples)
    6. Triggers used for flows
    7. Importing flows from outside Acrobat Sign
    8. Manage flows
    9. Edit flows
    10. Share flows
    11. Disable or Enable flows
    12. Delete flows
    13. Useful Templates
      1. Administrator only
        1. Save all completed documents to SharePoint
        2. Save all completed documents to OneDrive for Business
        3. Save all completed documents to Google Drive
        4. Save all completed documents to DropBox
        5. Save all completed documents to Box
      2. Agreement archival
        1. Save your completed documents to SharePoint
        2. Save your completed documents to One Drive for Business
        3. Save your completed documents to Google Drive
        4. Save your completed documents to DropBox
        5. Save your completed documents to Box
      3. Webform agreement archival
        1. Save completed web form documents to SharePoint Library
        2. Save completed web form documents to OneDrive for Business
        3. Save completed   documents to Google Drive
        4. Save completed web form documents to Box
      4. Agreement data extraction
        1. Extract form field data from your signed document and update Excel sheet
      5. Agreement notifications
        1. Send custom email notifications with your agreement contents and signed agreement
        2. Get your Adobe Acrobat Sign notifications in a Teams Channel
        3. Get your Adobe Acrobat Sign notifications in Slack
        4. Get your Adobe Acrobat Sign notifications in Webex
      6. Agreement generation
        1. Generate document from Power App form and Word template, send for signature
        2. Generate agreement from Word template in OneDrive, and get signature
        3. Generate agreement for selected Excel row, send for review and signature
  5. Custom Send workflows
    1. Custom Send Workflow Overview
    2. Creating a new Send Workflow
    3. Edit a Send Workflow
    4. Activate or Deactivate a Send Workflow
    5. Send an agreement with a Send Workflow
  6. Share users and agreements
    1. Share a user
    2. Share agreements

Integrate with other products

  1.  Acrobat Sign integrations overview 
  2. Acrobat Sign for Salesforce
  3. Acrobat Sign for Microsoft
    1. Acrobat Sign for Microsoft 365
    2. Acrobat Sign for Outlook
    3. Acrobat Sign for Word/PowerPoint
    4. Acrobat Sign for Teams
    5. Acrobat Sign for Microsoft PowerApps and Power Automate
    6. Acrobat Sign Connector for Microsoft Search
    7. Acrobat Sign for Microsoft Dynamics 
    8. Acrobat Sign for Microsoft SharePoint 
  4. Other Integrations
    1. Acrobat Sign for ServiceNow
    2. Acrobat Sign for HR ServiceNow
    3. Acrobat Sign for SAP SuccessFactors
    4. Acrobat Sign for Workday
    5. Acrobat Sign for NetSuite
    6. Acrobat Sign for VeevaVault
    7. Acrobat Sign for Coupa BSM Suite
  5. Partner managed integrations
  6. How to obtain an integration key

Acrobat Sign Developer

  1. REST APIs 
    1. Methods documentation
    2. SDK/Developer Guide
    3. API FAQ    
  2. Webhooks 
    1. Webhook overview
    2. Configure a new webhook
    3. View or edit a webhook
    4. Deactivate or reactivate a webhook
    5. Delete a webhook
    6. Two-way SSL certificates
    7. Webhooks in the API
  3. Sandbox
    1. Sandbox overview
    2. Link your Production and Sandbox
    3. Sandbox asset types

Support and Troubleshooting

  1. Customer Support Resources 
  2. Enterprise Customer Success Resources 

The Adobe Acrobat Sign Technical Notifications are ordered below, with the current update at the top, and rolling back in time as you scroll down the page. 

Tip:

The Technical Notifications page is updated regularly with new information, making its content highly dynamic. While localized versions are available, the translation process may cause slight differences from the authoritative US English version. Always refer first to the US English page for the most accurate and up-to-date information.

[Important] The next Adobe Acrobat Sign release is scheduled for April 22, 2025

This major release will introduce feature enhancements for users and administrators and resolutions to customer-reported issues.

Customers with a Sandbox entitlement will gain access to the new features four weeks before launch, along with prerelease documentation outlining the release content.

The release schedule and prerelease notes can be reviewed here >

Feature Release: Adobe Acrobat Sign – March 17th Release Completed

The release was completed to all shards with no downtime to any services.


[Important - Updated] Changes to the Adobe Acrobat Sign Network Infrastructure have been scheduled for February 24- March 11, 2025 deployment

First Reported: September 2024 - Updated February 2025

Current 

Bookmark this notice

To improve Adobe Acrobat Sign service security and robustness, we will start to roll out network changes to include a web application firewall (WAF) in February 2025. These changes will route traffic into Acrobat Sign application servers through the WAF service. This routing will be invisible to most customers. Usage will not interfere with access to Acrobat Sign from any Adobe clients or integrations.

Action Required

None.
This change will not affect customer integrations, as the Acrobat Sign API and API domain names will not change. This solution is backward compatible with the published IP ranges.
Customers who have updated their security devices don't need to revert or make any other changes.

The current update schedule is:

  • Production Sandbox updates February 24, 2025.
  • Production shards: IN1, JP1, AU1, and SG1 will update March 3, 2025.
  • Production shards: NA2, NA3, and EU2 will update March 6, 2025.
  • Production shards: NA1, NA4, and EU1 will update March 11, 2025.

  • Ingress and Egress Access to Acrobat Sign

    Acrobat Sign is no longer retiring the list of server ingress IP addresses as previously announced. 
    The server ingress and egress IP addresses, as documented on the System Requirements for Acrobat Sign page, will remain viable.

  • Why is Acrobat Sign making these Changes?

    The use of a WAF improves Acrobat Sign's protection against harmful traffic and helps us better address security, robustness, and compliance requirements.

  • I have a custom integration into Acrobat Sign. Will my application be affected?

    No, we don't expect any integrations to be negatively impacted.

  • Are there new IP address lists that can be substituted?

    No.
    The information on the System Requirements for Acrobat Sign page remains accurate.

  • My organization has implemented network filtering using Acrobat Sign's published domain list for traffic from our corporate network. Are we affected?

    No.
    The network changes described here do not impact Acrobat Sign's domain list, as documented on the System Requirements for Acrobat Sign page. Domain-level filtering is unaffected.

  • My organization employs IP address validation for email delivery from Acrobat Sign servers. Are we affected?

    No.
    The IP ranges for outbound mail relays, as listed on the System Requirements for Acrobat Sign page, are not changing.

  • My organization has configured our Acrobat Sign account to restrict access to our own IP addresses. Are we affected?

    No.
    Acrobat Sign can be configured to validate incoming traffic against customer-chosen IP addresses, as described on the Restrict access to your account using IP address ranges page. Such usage will not be affected by this change.

  • My organization has implemented network filtering using Acrobat Sign's published list of ingress IP addresses. Are we affected?

    No.

    The new WAF configuration is backward compatible with the existing network architecture, so no additional tuning of your security devices should be required.

    Note:

    Note that this refers to IP-level filtering for the environment hosting your application. Domain-level filtering is not affected.

  • I'm using the Salesforce integration with explicitly configured IP allow-listing. Do I need to do anything?

    No. 

    The WAF installation requires no changes for existing Salesforce installations at this time.
    The existing configuration/process, as described in the help documentation, remains the same, and administrators should follow all IP allow-listing steps.

ISV and Embed Partners should contact their Success Manager for any further questions.


[Important] Disablement of the SOAP API for Adobe Acrobat Sign Embedded Partners has been scheduled for March 1, 2025

First Reported: June 2018 - Updated May 2024

Current

Bookmark this notice

Action Required

All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.

Access to the SOAP API will be removed for all embed partners starting March 1, 2025.
To ensure continued function, all embed partners using the Adobe Acrobat Sign SOAP API must migrate to the latest REST API V6 before March 1, 2025.  

Please review the REST v6 and migration documentation for reference:

For any queries, please contact your designated Adobe Acrobat Sign PSM.
 


[Important] Disablement of the SOAP API from Adobe Acrobat Sign accounts is scheduled to start in February 2024

First Reported: June 2018 - Updated May 2024

Current

Bookmark this notice

Action Required

All integrations and applications using the Adobe Acrobat Sign SOAP API must be migrated to the latest REST API V6 before the disablement date to ensure continued function.

Initially announced in June 2018, the effort to sunset the Acrobat Sign SOAP API will be completed in 2024.

Customer use of the SOAP API is scheduled to be disabled through a rolling process starting in February 2024. All customers and partners using the SOAP API must migrate to REST v6 API or risk a disruption in their service.

Please review the REST v6 and migration documentation:

Access to the SOAP API will be removed per the following schedule:

Account type

SOAP API Disablement Date
  • Free
  • Trial
  • Developer

February 1, 2024 (Completed)
  • Enterprise
  • Business

April 1, 2024 (Completed)
  • Integration Only Partners

The scheduled date has been moved up to July 1, 2024, replacing the previous date of December 1, 2024.
  • Embedded Partners

March 1, 2025


[Updated] The webhookNotificationApplicableUsers parameter is to be removed from the Webhook payload. 
Sandbox is to be updated in the March 2025 release.
Production is to be updated in the April release.

First Reported: September 2024 - Updated February 2025

Current 

Bookmark this notice

The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads.
The Sandbox environment will be updated in the March 2025 release.
The Production environments will be updated in the April release.

The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload. 

 

[Updated] The new Request Signature environment will be promoted to be the default experience and the switch links between Classic and Modern environments will be removed in the April 2025 release.

Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

This update only applies to the Send (Request e-signatures) page. Structured Self-signing workflows are not yet included.

First Reported: March 2024 - Updated January 2025

Current 

Bookmark this notice

Starting with the April 2025 release, the modern Request Signature environment will become the default experience when creating a new agreement.

  • Users will no longer be able to switch between the new and classic environments, as switch links will be disabled.
  • Administrators will still have the option to enable the classic experience and restore switch links through the admin menu.
  • Customers using the Notarize integration will not be affected by this change.


[Updated] The classic Compose page will be retired and removed from the commercial interface in the July 2025 release.

Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

First Reported: June 2024 - Updated January 2025

Current 

Bookmark this notice

Final Transition to the New Request Signature Experience

With the July 2025 release, the classic Compose interface will be fully removed from availability, finalizing the transition to the new Request Signature experience.

  • All commercial accounts that have not yet set the new Request Signature environment as their default will be automatically switched to it as the only option for configuring new agreements.
  • The ability to configure the experience or switch between environments will be removed from admin menus.
  • Customers using the Notarize integration will not be affected by this change.


[Updated] The modern Send in Bulk environment will become the default experience for all commercial accounts in April 2025.
Switch links will remain available.

First Reported: March 2024 - Updated February 2025

Current 

Bookmark this notice
Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

As of the April 2025 release, the modern Request Signature environment will become the default experience when creating a new agreement.

  • Users will still be able to switch between the modern and classic environments using switch links on the page.
  • Administrators will still have the option to enable the classic experience and restore switch links through the admin menu.

 


[Updated] The classic Send in Bulk environment will be removed from service in July 2025.

First Reported: March 2024 - Updated February 2025

Current 

Bookmark this notice
Note:

This update only applies to the Commercial version of the Acrobat Sign service. Government Cloud accounts are not impacted.

Final Transition to the New Request Signature Experience

With the July 2025 release, the classic Send in Bulk interface will be fully removed from availability, finalizing the transition to the modern Send in Bulk experience.

  • All commercial accounts that have not yet set the modern Send in Bulk environment as their default will be automatically switched to it as the only option for configuring new bulk transactions.
  • Switch links to access the classic experience will no longer be available.
  • The ability to configure the experience will be removed from administrator menus.


[Updated] Option to enable a mobile-friendly view of agreement fields for mobile recipients using a web browser.
To be added to Sandbox on December 11, 2024; Production on March 4, 2025

First Reported: November 2024 - Updated: January 2025

Current 

Bookmark this notice

Senders can provide an additional view of agreements for mobile recipients that lists only the field within the agreement available to the recipient.

Senders can arrange the field list as they like, and group fields into logical sections to help the signers move through the field input with a minimum of scrolling.

Recipients have the option to view the mobile-friendly fields list or the original PDF view with the fields placed within the document content.

This feature is scheduled to be released:

  • To be deployed on the Sandbox environment on December 11, 2024
  • To be deployed on the Production environment on March 4, 2025


[New] REST API GET /agreements Optimizations

First Reported: March 2025

Current 

Bookmark this notice

Adobe has optimized the implementation of the GET /agreements API to reduce the response time of the API calls. Internal testing indicates a reduction in response time up to an order of magnitude.

This optimization reduces the maximum number of agreements returned in a single call by lowering the maximum page size (the number of agreement records posted to the page). This maximum size is currently 500. (Adobe reserves the right to adjust this value in future releases.) Clients can request the number of agreements to be returned in a single call but will get back as many agreements as the service can provide. The actual number of agreements returned and a link to the next page of agreements are returned along with the agreements themselves.

There may be a small delay between creating an agreement and returning it in the GET /agreements API. In practice, this delay is rarely noticeable, and a subsequent call to the API would return the new agreement.

Available environments: Commercial, Government | Available tiers of service: Acrobat Sign Services, Government | Configuration scope: Enabled by default; Not configurable


[New] New Webhook limits for Developer tier accounts

First Reported: March 2025

Current 

Bookmark this notice

Starting in April 2025, Acrobat Sign will implement stricter limits on the number of webhooks created in Developer-tier accounts.

These limits have been purposefully chosen to ensure the reliability of the webhooks infrastructure and better aligned for testing workflows.

What is changing

Previous limit

New Limit

Description

Number of active webhooks created per channel

10

1

1 webhook is allowed for the channel per webhook subscription event.

Number of active webhooks created for an account

100

2

2 account level webhooks are allowed per webhook subscription event.

Number of active webhooks created per group

100

2

2 group level webhooks are allowed per group per webhook subscription event.

Number of active webhooks created per agreement resource

50

1

1 webhook is allowed per agreement per webhook subscription event.

Number of active webhooks created per user

100

1

1 webhook is allowed per user per webhook subscription event.

Available environments: Commercial | Available tiers of service: Developer | Configuration scope: Enabled by default; Not configurable


[New] Adobe Acrobat Sign: Improved user onboarding.

First Reported: March 2025

Current 

Bookmark this notice
  • Improved User Login Experience - Acrobat Sign has streamlined the login and authentication process through the Adobe Identity Management System (IMS).
    • The user's organizational profile is automatically selected during the login process to the ones entitled with the Acrobat Sign service ( Identifying the request as coming from an Acrobat Sign source)
    • Users who encounter errors during login will have links in their error messages to contact their Acrobat Sign administrators for assistance.
    • All users assigned an active entitlement but have not logged in to the service will be sent up to two email reminders. (This also applies to existing inactive users before the release date )

These improvements simplify login, reduce friction, and improve the overall user experience.

Available environments: Commercial | Available tiers of service: Acrobat Sign Solutions - VIP licensed organizations | Configuration scope: Enabled by default; Not configurable
 


[New] Adobe Acrobat Sign Webhook service available for status event subscriptions.

First Reported: March 2025

Current 

Bookmark this notice

Acrobat Sign customers can now subscribe to the Acrobat Sign Webhook service to receive proactive notifications about outages, disruptions, and maintenance events via the Adobe Status Portal.

Manage and add subscriptions here: Adobe Status Subscription Help.

Note that the Adobe Acrobat Sign service is listed under the Document Cloud heading:

The webhook subscription page with Acrobat Sign highlighted.


[New] Updated Create Template Experience Coming in April 2025

First Reported: February 2025

Current 

Bookmark this notice

With the April 2025 release, most accounts will transition to a new Create Template authoring experience, introducing an updated UI for creating reusable templates.

  • Administrators can configure accounts to continue using the classic experience at the Account or Group level.
  • Users will not have the option to switch back to the classic authoring experience from the UI.
Note:

Accounts that have enabled sharing templates across multiple groups are excluded from this update.


[New] The Account tab will be renamed to Admin starting with the April 2025 release

First Reported: February 2025

Current 

Bookmark this notice

The Account tab, available to Acrobat Sign account-level administrators, will be renamed Admin.

  • This update applies exclusively to the Acrobat Sign Standalone environment (Acrobat Sign Solutions and Acrobat Sign for Government).
  • The update will be implemented for the Commercial environment in April 2025 and the Government environment in May 2025.

Note that this change is purely cosmetic—there are no functional modifications, only updates to the tab labels.

Note:

The Group label for group-level admins will not change.


The webhookNotificationApplicableUsers parameter is to be removed from the Webhook payload. 
Sandbox is to be updated in the March 2025 release.
Production is to be updated in the April release.

First Reported: September 2024

Current 

Bookmark this notice

The Webhook 2.0 infrastructure has been rolled out to all customers, and with that completed, signer notifications have been deprecated. As a result, the webhookNotificationApplicableUsers parameter of the webhook payload no longer provides any useful data and will be removed from all webhook payloads.
The Sandbox environment will be updated in the March 2025 release.
The Production environments will be updated in the April release.

The sending userID and email can be found using the initiatingUserId and initiatingUserEmail parameters in the notification payload. 


Deprecation of the Adobe Acrobat Sign REST API v1-v4.
End of support and removal of legacy REST API versions on December 1, 2025.

First Reported: September 2024

Current 

Bookmark this notice

Action Required

All customers using the API must update their APIs to utilize the version 6 endpoints as soon as possible to ensure uninterrupted availability. 

Versions 1 through 4 of the Acrobat Sign REST API have been deprecated and will be removed from service on December 1, 2025.

Updating APIs can involve considerable effort, so all customers are strongly encouraged to scope and budget their update as soon as possible so that support can be fully engaged to resolve any questions or problems that arise before the December 2025 cutoff date.

While REST API v1-4 are deprecated, they will continue to function, and your applications will continue to work until December 1, 2025, when the REST API v1-4 will be removed.

After December 1, 2025, applications built on the REST API v1-4 will cease functioning.

 


Classic reporting to be removed from service in the first half of 2025

First Reported: September 2022 - Updated March 2024

Current 

Bookmark this notice

Classic reporting will be completely removed from the Acrobat Sign interface in the first half of 2025. This includes the switch link that allows changing between environments. Once removed, customers will not be able to return to the classic environment to review classic reports, and scheduled reports will stop executing.

The modern reporting environment will remain as the only reporting solution.

All customers are strongly encouraged to recreate all of their existing reports in the new environment as soon as possible.


External source drives to be removed from support in the new Request Signature experience

First Reported: May 2024

Current 

Bookmark this notice

The option to use an external drive for uploading files will be limited to OneDrive only in the new Request Signature experience.

It's recommended that customers who use other options for file upload use the vendor-specific application to provide a networked drive that can be accessed through the native file picker on the user's local system.


Additional Resources


Adobe Acrobat Sign SSL Certificate updates in January, 2025

First Reported: December 2024

Removed from Current list: February 2025

Bookmark this notice

Adobe Acrobat Sign will rotate the Adobe Acrobat Sign SSL Certificate on January 22, 2025.

In addition, a new SSL certificate is being deployed to support the WAF network changes being made in January 2025. This new certificate directly impacts access to the Acrobat Sign service and must be installed before the WAF goes online.

Action Required

  • Every customer account that explicitly secures network activity must include the new WAF SSL certificate in its list of stored certificates.
  • If you have custom-built integrations with Acrobat Sign using either the SOAP or REST APIs and if any of these integrations have ‘pinned’ the existing public key, no other action is required.
  • If you are using Acrobat Sign’s SSL certificates for SSO, or if you’re pinning the certificate itself (or using other methods), you can find the new Acrobat Sign SSL certificates in the Adobe Acrobat Sign System Requirements.
    • If your SSO configuration supports multiple public certs/chains, you can add the new certificates now and remove the old public cert/chain from your configuration after the January switch.
    • If your SSO does not support multiple public certs/chains, you will need to sync your SSL switch with Acrobat Sign on January 22, 2025.  

The new SSL certificates will be active on January 22, 2025.


Customers with a Sandbox environment will be able to access the new Recipient experiences the first week of December 2024

First Reported: November 2024

Removed from Current list: February 2025

Bookmark this notice

The new recipient experience contains signing improvements for both desktop and mobile web browsers. This new experience is being rolled out over the first months of 2025 but will be available in the Sandbox environment in the first week of December 2024.


The Accept-Charset header will be removed from Webhook and Callback notifications in the November 2024 release

First Reported: August 2024

Removed from Current list: January 2025

Bookmark this notice

The legacy Accept-Charset header will be removed from all Webhook and Callback notifications with the November 2024 release.

All customers that rely on this header for any reason should refactor their code to account for it's absence.


Adobe Acrobat Sign Cookie Partitioning to be enabled in the November 2024 release.
Available in the Sandbox now.

First Reported: September 2024

Removed from Current list: January 2025

Bookmark this notice

Acrobat Sign will enable cookie partitioning in the Production environment with the November 2024 release.

The Sandbox will enable cookie partitioning after the September 17, 2024, release to allow customers to test the changes.

Developers and customers using cookies for any reason should be aware of this and test their applications in the Sandbox before November 2024 to ensure a smooth transition.


Custom Workflow Designer places a 100-character limit on labels for all new and existing workflow templates

First Reported: November 2024

Removed from Current list: January 2025

Bookmark this notice

With the November 2024 release, the editable labels in the Custom Workflow Designer have been limited to 100 characters. This limit is evaluated when the workflow is created or updated.

Preexisting workflows that have labels over 100 characters can still be sent successfully, but if the workflow is updated, the label must be reduced to 100 characters or less before it can be saved. Offending labels are outlined in red for easy discovery.

New workflows will warn about the label limit before they are saved.

Action Required

It is recommended that admins with control over custom workflows open and review each workflow to ensure that they don't have errors on their template.

Archived Notifications

Listed by the date when the notice was removed from the current notice list, most recent to oldest.

Archive of Technical Notifications 2023 - 2024

Archive of Technical Notifications 2021 - 2022

Archive of Technical Notifications 2019 - 2020

Archive of Technical Notifications 2017 - 2018

Archive of Technical Notifications 2015 - 2016

Get help faster and easier

New user?

Quick links

View all your plans Manage your plans
View quick links
Hide quick links

Legal Notices    |    Online Privacy Policy