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
    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. Required fields
      8. Attaching documents
      9. Field flattening
      10. Modify Agreements
      11. Agreement name
      12. Languages
      13. Private messages
      14. Allowed signature types
      15. Reminders
      16. Signed document password protection
      17. Send Agreement Notification through
      18. Signer identification options
        1. Overview
        2. Signing password
        3. One-Time Password via Email
        4. Acrobat Sign authentication
        5. Phone authentication
        6. Cloud-based digital signature
        7. Knowledge-based authentication
        8. Government ID
        9. Signer Identity reports
      19. Content Protection
      20. Enable Notarize transactions
      21. Document Expiration
      22. Preview, position signatures, and add fields
      23. Signing order
      24. Liquid mode
      25. Custom workflow controls
      26. Upload options for the e-sign page
      27. 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

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 page overview
    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. In-line Images
        3. Stamp Images
      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. Edit a data export
      3. Refresh the data export content
      4. 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

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. 

 

[Important] The next Adobe Acrobat Sign release is scheduled for November 12, 2024

Note:

The Sandbox deployment for the November 2024 release has been delayed until October 28, 2024.

This will be a major release, including feature improvements for users and administrators, as well as resolutions to customer-reported issues.  

Customers with a Sandbox entitlement will have access to the new features four weeks prior to launch. Prerelease documentation for the release content will also be available at that time.

The release schedule and prerelease notes can be reviewed here >

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

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


[Important] January 2025 Change to the Adobe Acrobat Sign Network Infrastructure

First Reported: September 2024

Current 

Bookmark this notice

To improve Adobe Acrobat Sign service security and robustness, we will roll out network changes beginning the week of January 13, 2025. These changes will route traffic into Acrobat Sign application servers through the Akamai content network. 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

In most cases, this change will not affect customer integrations, as the Acrobat Sign API and API domain names will not change. However, the underlying IP addresses for the Acrobat Sign API endpoints will shift.

Integrations written to explicitly allow-list the previously documented Acrobat Sign API ingress addresses will need to remove those legacy allow-listings by January 13, 2025. 

  • Ingress vs. Egress Access to Acrobat Sign

    Acrobat Sign provides ingress endpoints for API requests to Acrobat Sign and egress endpoints for webhook callbacks to customer applications and email delivery. 
    Only the ingress traffic is affected by this change. There are no changes to egress traffic.

  • Why is Acrobat Sign making these Changes?

    The use of the Akamai content network 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?

    In most cases, no, but it depends on how your application is written.

    Typically, applications depend only on the Acrobat Sign service domain names (e.g., "api.na1.adobesign.com"), and these names will continue to work. Less commonly, an application will take the additional step of allow-listing the specific IP address that this name resolves to.

    Such allow-listing is more commonly seen when developing a webhook endpoint to verify that the webhook request is coming from a valid Acrobat Sign server. Webhook IP addresses are not affected by this change.

    Less commonly, an application initiating a request to an Acrobat Sign endpoint will validate the IP address against an allow-list. Such validation logic must be removed, or the application will fail.

    As a standard best practice, the application should perform server certificate validation of the Acrobat Sign endpoint when initiating the TLS connection. This provides strong assurance that the request is going to a valid Acrobat Sign endpoint. Most HTTP/S frameworks and libraries perform server certificate validation by default.

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

    Acrobat Sign will no longer publish or support a list of server ingress IP addresses as such usage isn't compatible with the Akamai network.  The server egress IP addresses, used by webhooks and email relays, will continue as documented on the System Requirements for Acrobat Sign page.

  • 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?

    Yes.
    Acrobat Sign will no longer publish or support a list of server ingress IP addresses as such usage isn't compatible with the Akamai network. The respective network filters, for example on firewalls, must be removed by January 13, 2025.

    If these legacy IP network restrictions are not removed before this change goes into effect, connectivity to Acrobat Sign will stop working.

    Note:

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


[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


[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.
 


[New] Customers with a Sandbox environment will be able to access the experiences the first week of December 2024

First Reported: November 2024

Current 

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.


[New] The webhookNotificationApplicableUsers parameter is to be removed from the Webhook payload in the March 2025 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 when the March 2025 release is deployed.

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.

 


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

First Reported: September 2024

Current 

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.


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

First Reported: August 2024

Current 

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.


The new Request Signature environment will be promoted to be the default experience in the September 2024 release.
Switch links between Classic and New environments will be removed in the  November 2024 release.

Note:

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

First Reported: March 2024 - Updated June 2024

Current 

Bookmark this notice

The new and improved Request Signature environment will be the default experience for all accounts to create a new agreement starting with the September 17, 2024, release.

Links will remain available for users to switch between the new and classic environments, and administrators will continue to have the option to reset the default to the classic experience through their admin menu.

The classic environment will be entirely removed from the user experience by March 2025.

Note:

The new in-application Authoring experience is only available as part of the new Request Signature experience.
Customers who are using new Authoring with classic Request Signature will default to the new Request Signature experience after the September 17 release, and the setting for new authoring will be removed from the admin menu.

As part of the November 2024 release, all accounts will have their default sending environment set to the new Request Signature experience.

The option to enable the switch links for users to switch between the environments will also be disabled.

Note:

Administrators will continue to have the option to enable the switch links in the admin menu.


The classic Compose page will be retired and removed from the interface in the March 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

Current 

Bookmark this notice

In the March 2025 release, the classic Compose interface will be removed entirely from the Acrobat Sign interface, completing the promotion of the new Request Signature experience.

All commercial accounts that have not configured the new Request Signature service as their default experience will have the Request Signature environment enabled as the only environment for configuring new agreements.

The option to configure the experience, including the switch links between environments, will be removed from the admin menus.


The classic Send in Bulk environment will be retired in March 2025.
Adobe Acrobat Sign's new Send in Bulk environment became the default experience for all accounts on April 9, 2024.

First Reported: March 2024

Current 

Bookmark this notice

The new and improved Send in Bulk environment became the default environment for all accounts as of the April 9, 2024, release.

Links will remain available for users to switch between the new and classic environments, and administrators will continue to have the option to reset the default to the classic experience through their admin menu.

The classic environment will be entirely removed from the user experience by March 2025.
 


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


Past Notifications


New IP addresses have been added to the Acrobat Sign European data center (EU2) allow list for Webhooks and Callbacks.
These IP ranges must be added before the end of September 2024 to avoid impacting service.

First Reported: August 2024

Removed From Current List: November 2024

Bookmark this notice

Action Required

Customers who maintain network security practices that explicitly list inbound IP addresses must update the IP ranges for the Acrobat Sign service by the end of September 2024.
The complete list of IP ranges is published on the system requirements page.

To ensure the continued seamless function of your callbacks and webhook notifications, the IP ranges below must be added to the allow list for all customer accounts in the EU2 data center.

The added IP ranges are:

  • 4.207.3.96/28
  • 4.207.4.160/28
  • 4.208.75.176/28
  • 4.208.75.80/28
  • 4.208.79.192/28
  • 4.208.79.208/28
  • 4.245.45.176/28
  • 4.245.45.192/28
  • 4.245.45.208/28
  • 4.245.45.224/28
  • 4.245.45.240/28
  • 4.245.46.128/28
  • 4.245.85.80/28
  • 20.23.101.224/28
  • 20.31.209.192/28
  • 20.31.209.240/28
  • 20.31.210.16/28
  • 20.31.210.48/28
  • 20.105.66.176/28
  • 20.166.106.144/28
  • 20.166.107.112/28
  • 20.166.107.240/28
  • 20.166.107.32/28
  • 40.127.244.64/28
     


Adobe Acrobat Sign Templates: W-9 and I-9 (2024) templates added to the Acrobat Sign library

First Reported: August 2024

Removed From Current List: November 2024

Bookmark this notice

The new IRS I-9 and W-9 forms, entitled I-9 (Employment Eligibility Verification) Exp 5/31/27 and W-9 (Request for Taxpayer Identification Number) Rev 3/24, respectively, are scheduled to be added to the Acrobat Sign library.

ACTION REQUIRED

The new library templates have new libraryDocumentIds. If you use either existing template’s libraryDocumentId in your applications, you'll need to update it.

The 2023 versions are scheduled to be removed from the system with the November 12, 2024 release.

Any application/API using the legacy (ver 2023) templates must be updated before November 8, 2024 to ensure no disruption to successful service.

To find the libraryDocumentId in an API-enabled account:

  1. Log in as an Account Admin
  2. Click on the Account tab > Adobe Sign API > API Information > click the link: REST API Methods Documentation
  3. In the GET /libraryDocuments section, click the OAUTH ACCESS-TOKEN button 
    • Enable the library_read:self scope
  4. Click the Try it out! button
  5. In the Response Body, locate the new I-9 ( Employment Eligibility Verification) Exp 5/31/27 or W-9 (Request for Taxpayer Identification Number) Rev 3/24 form template (not ver. 2023) to see the libraryDocumentId value.  
Obtain the docID


Improved Request Signature page for embedded applications 

First Reported: November 2023

Removed From Current List: November 2024

Bookmark this notice

Acrobat Sign has developed a version of the new Request Signature page as a  Single Page Application (SPA) for customers that have built their own custom integrations and applications. Instead of using browser cookies for the user session, this new solution uses session access tokens to access the Acrobat Sign workflows and pages.

The SPA solution overcomes a problem where browser cookies stored in an iFrame are viewed as third-party cookies, and the trend for browsers is to disable third-party cookies by default.

Customers with embedded solutions and want to take advantage of the SPA-built Request Signature page should contact support to enable the feature.

 


Upgraded search for automatic email address completion

First Reported: September 2024

Removed From Current List: November 2024

Bookmark this notice

The autocompletion feature that generates a list of email addresses when entering a recipient into any email field has traditionally only matched strings from the beginning of the address.

The API that drives that autocomplete functionality has been updated to support "tokenizing" the email, allowing for each token to match individually to the searched for string.

Example of a part of an email typed into a recipient field showing the address match in the middle of the string.

Note:

Tokenizing is the process where the email address is broken into smaller strings (tokens) based on common delimiters. Characters treated as delimiters (other than whitespace) are: ~ ` ! @ # $ % ^ & * ( ) - + = { } [ ] | \ . , : ; " ' < > ? /


Changes to the Adobe Acrobat Sign Enterprise Support Workflow for legacy customers who haven't migrated to the Admin Console

First Reported: July 2024

Removed From Current List: November 2024

Bookmark this notice

This notification applies only to Acrobat Sign commercial enterprise administrators who have yet to migrate their users to an Adobe VIP, VIP Custom, or ETLA console.

  • If your Acrobat Sign contract expires before September 17, 2024, you may disregard this notification.
  • Customer accounts in the Government Cloud environment are not impacted.

Starting September 17, 2024, you'll see a new workflow to contact Adobe Acrobat Sign Support. Here is a high-level overview of the workflow:

  1. Log in to your Acrobat Sign account as an administrator.
  2. Select the "Contact Support" option under the question mark in the upper right of the window.
  3. You will be redirected to a new page with three channels to contact Support. Please select one of the three channels to get help with your issue:
    • Web form: For priority 2 and lower issues, you may submit a support request through the web form and expect a response in one business day.
    • Phone: For priority one critical issues, please call us so we can serve you immediately.
    • Chat: Get in touch with our experts in real-time. 

If you have an unresolved ticket with Support beyond September 17, 2024, your ticket history and conversation will be moved to a new system by the assigned support agent, who will confirm the move before and after. Future communications between you and Support regarding the unresolved issue will happen on the new system.

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

 Adobe

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