User Guide Cancel

Migrating from echosign.com to adobesign.com

 

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. Add a User
    2. Add Users in Bulk
    3. Add Users from your Directory
    4. Add Users from MS Azure Active Directory
    5. Create function-focused users
      1. Technical accounts - API driven
      2. Service accounts - Manually driven
    6. Check for users with provisioning errors
    7. Change Name/Email Address
    8. Edit a user's group membership
    9. Edit a user's group membership through the group interface
    10. Promote a user to an admin role
    11. User Identity Types and SSO
    12. Switch User Identity
    13. Authenticate Users with MS Azure
    14. Authenticate Users with Google Federation
    15. Product Profiles
    16. Login Experience 
  3. Account/Group Settings
    1. Settings Overview
    2. Global Settings
      1. Account tier and ID
      2. Self Signing Workflows
      3. Send in Bulk
      4. Web Forms
      5. Custom Send Workflows
      6. Power Automate Workflows
      7. Library Documents
      8. Collect form data with agreements
      9. Limited Document Visibility
      10. Attach a PDF copy of the signed agreement 
      11. Include a link in the email
      12. Include an image in the email
      13. Files attached to email will be named as
      14. Attach audit reports to documents
      15. Merge multiple documents into one
      16. Upload a signed document
      17. Delegation for users in my account
      18. Allow external recipients to delegate
      19. Authority to sign
      20. Authority to send
      21. Power to add Electronic Seals
      22. Set a default time zone
      23. Set a default date format
      24. Users in Multiple Groups (UMG)
        1. Upgrade to use UMG
      25. Group Administrator Permissions
      26. Replace recipient
      27. 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
      28. In Product Messaging and Guidance
      29. Accessible PDFs
      30. New authoring experience
      31. Healthcare customer
    3. Account Setup
      1. Add logo
      2. Customize company Hostname/URL    
      3. Add company name
    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. Decline to sign
      8. Allow Stamps workflows
      9. Require signers to provide their Title or Company
      10. Allow signers to print and place a written signature
      11. Show messages when e-signing
      12. Require signers to use a mobile device to create their signature
      13. Request IP address from signers
      14. 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. Recipient groups
      6. Required fields
      7. Attaching documents
      8. Field flattening
      9. Modify Agreements
      10. Agreement name
      11. Languages
      12. Private messages
      13. Allowed signature types
      14. Reminders
      15. Signed document password protection
      16. 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
      17. Content Protection
      18. Enable Notarize transactions
      19. Document Expiration
      20. Preview, position signatures, and add fields
      21. Signing order
      22. Liquid mode
      23. Custom workflow controls
      24. Upload options for the e-sign page
      25. 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. Custom email templates
      6. Enable Linkless Notifications
    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. eOriginal vaulting for chattel paper
    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 

Send, Sign, and Manage Agreements

  1. 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 - manual recipients
      3. Send in Bulk - CSV upload
      4. Cancel a Send in Bulk transaction
      5. Add reminders to Send in Bulk
      6. Reporting for Send in Bulk
  2. 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 
  1. Authoring FAQ
  2. Sign Agreements
    1. Sign agreements sent to you
    2. Fill & Sign
    3. Self-signing
  3. 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. 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
  4. Audit Report
  5. 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. Track Power Automate usage
    4. Create a new flow (Examples)
    5. Triggers used for flows
    6. Importing flows from outside Acrobat Sign
    7. Manage flows
    8. Edit flows
    9. Share flows
    10. Disable or Enable flows
    11. Delete flows
    12. 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 

Overview of what's happening

Adobe Acrobat Sign has deployed a new domain: adobesign.com.

Customers can identify their domain by logging in to Acrobat Sign and checking the URL:

  • If your URL reads adobesign.com, your account is already on the new domain.
  • If your URL shows echosign.com, then your account must be migrated.
Alert:

If your URL reads documents.adobe.com, your domain is not changing. However, customers will need to explicitly allow email from adobesign@adobesign.com

Echosign URL


Actions to review/take

To ensure continuity of service, customers should prepare for the domain migration by reviewing the below list of actions and addressing the issues that are germane for their account.

All impacted accounts will have the ability to switch to the new domain once their account has successfully resolved any concerns/tasks that the below list prompts.

Caution:

Changing your SAML configuration requires that you opt-in to the new domain immediately after saving the new IdP settings in Acrobat Sign.

SSO to the account will be broken until the domain switch is completed.

If you are a SAML using customer, be sure to set your SAML Mode settings in Acrobat Sign to SAML Allowed

  • Verify that you know your native Acrobat Sign password
    • This is a precaution to avoid being accidentally locked out of your account after you change the IdP

Admins that have users leveraging the Acrobat Sign for iOS mobile app should alert their users to upgrade their app version to 3.22 or later.

The Acrobat Sign for Android app is not impacted by the domain change.

Note:

Updating custom email templates must be done by your success manager or the support team.

As the templates can be updated at any time prior to changing to the new domain., it is recommended that you request this update as early as possible.

If your account uses any custom email templates, the template must be updated to allow for a reference to adobesign@adobesign.com as the email alias for users to add to their safe list..

  • To do this, the fixed string echosign@echosign.com is changed to the variable $!from@$!active_domain
    • This allows the address to dynamically change when the account is switched between domains

Customers that actively restrict email should explicitly allow email from adobesign@adobesign.com

  • If you have an existing rule to allow echosign@echosign.com, then add this new rule also
    • Do not remove the echosign@echosign.com rule at this time

Failure to do so could result in inbound (email) agreement notifications being filtered out to spam/junk folders.

Customers with restrictive network security should explicitly allow traffic from the new domain's production endpoints.

If your current network permissions are configured to allow echosign.com traffic through, the adobesign.com endpoints should be added as well.

  • Do not remove the echosign.com endpoints at this time
  • Only add adobesignforsalesforce.com if your account employs the Adobe Acrobat Sign for Salesforce integration
  • Customers that have accounts on the Demo environment should add the adobesign Demo endpoints as well
Environment 'echosign' domain 'adobesign' domain equivalent
Production echosign.com adobesign.com
echocdn.com adobesigncdn.com
echosignforsalesforce.com adobesignforsalesforce.com
-- documentcloud.adobe.com
Demo echosigndemo.com adobesigndemo.com
echocdndemo.com adobesigncdndemo.com
echosignforsalesforcedemo.com adobesignforsalesforcedemo.com
Note:

An expanded list of Adobe Acrobat Sign endpoints can be found here, but only those listed above are relevant to this domain migration.

No edits to IP ranges are required.

Accounts that leverage the API service should review their code to ensure that it also supports the adobesign.com domain.

Note:

Refresh tokens (used to get new access tokens) are not tied to the domain, so they are not impacted by the domain change.

Customers/Partners/Integrators may have code that has a hardcoded check for the URI returned. This may be done as a security measure to prevent an exploit which attempts to redirect the domain incorrectly.

  • Contact the owner of any third party integration to determine if this situation exists
  • Contact your internal stakeholders for custom integrations that were built in-house
Caution:

Changing your SAML configuration requires that you opt-in to the new domain immediately after saving the new IdP settings in Acrobat Sign.

SSO to the account will be broken until the domain switch is completed.

  1. Set your SAML Mode settings in Acrobat Sign to SAML Allowed

    • Verify that you know your native Acrobat Sign password
      • This is a precaution to avoid being accidentally locked out of your account after you change the IdP
    SAML Mode

  2. Create a new client with your IdP (MSADFS, Okta, etc)

    • Build your new client using the Acrobat Sign SAML Service Provider Information for the new domain (See the caution below)
    • It is recommended that you retain the old client until you are confident that SSO is working as expected in the new domain
    Caution:

    When migrating to a new domain, the Acrobat Sign Service Provider content on the Acrobat Sign SAML page will show the existing domain configuration.

    You need to manually edit the three URLs to reflect the new domain you are migrating to.

    • eg: If you are migrating to adobesign.com, your existing URLs will reflect echosign.com; manually change them to adobesign.com when you configure your new client

    Do not edit the:

    • Entity ID/SAML Audience
    • SP Certificate

    Manually edit the:

    • Assertion Consumer URL
    • Single Logout (SLO) URL
    • Single Sign-On (Login) URL


  3. Update the Identity Provider configurations using the values from the newly created IdP client

  4. Log in to Acrobat Sign as an account-level admin and navigate to Account > Account Settings > Account Setup

    • Click the Update now button
      • You will be logged out automatically and will have to authenticate to the new domain
      • If you have a bookmark to log in, edit the URL to use adobesign.com instead of echosign.com
    Update the domain

    Note:

    Bookmarks to the old domain (echosign.com) can prompt multiple Cookie enablement requests when the login process shifts the user to the new domain (adobesign.com). 

    Users can mitigate this by updating their bookmarks.

  5. Test your SSO connection

Adobe Acrobat Sign for Salesforce customers must relink the OAuth connection between Acrobat Sign and Salesforce (as soon as possible) after the domain has been changed.

Changing the domain breaks the trusted connection between Acrobat Sign and Salesforce. Until the OAuth link is reconnected:

  • Users will not be able to send agreements from Salesforce
    • Attempts to send will prompt an error and save the agreement as a Draft   
  • Updates will not be pushed back into Salesforce
    • Upon reconnection, the agreements can be updated and resynced with the Acrobat Sign service

Review/Update Remote Site Settings

Organizations that have configured Remote Site Settings for Acrobat Sign must also update the remote site URL to reflect adobesign.com (in place of echosign.com).

  1. Navigate to Setup > Settings > Security > Remote Site Settings

  2. Review the Remote Site URLs for the remote sites configured.

    Find any sites that use echosign.com as the domain in the URL:

    Update the remote site URL

  3. Click the Edit action for the remote site using the echosign.com domain

  4. Edit the Remote Site URL and change echosign.com to adobesign.com

    Update the remote site URL

    Caution:

    Do not change the other elements of the URL.

  5. Click Save to save the new configuration

Repeat steps 3-5 for all remote sites that use echosign.com as the domain for the URL.

Note that it is possible for the site URL to contain the string "echosign" in a location of the string that is not the domain. Do NOT edit these values:

Not an echosign.com domain

Existing web forms will continue to work as expected after changing the domain.

When a web form is created, it is identified by a unique webformId (wid).

Changing the domain changes the URL of the web form, but not the webformId.

Example:

The echosign.com webform URL:

  • https://caseyjonez.na1.echosign.com/public/esignWidget?wid=CBFi_MHTdBzgM82U*

The same web form after the domain change:

  • https://caseyjonez.na1.adobesign.com/public/esignWidget?wid=CBFi_MHTdBzgM82U*

Because Acrobat Sign continues to accept inbound traffic on the echosign.com domain, the URL resolves and the correct webformId is delivered.

Note:

It is recommended that customers update their content to use the URLs with the new domain when possible.

Note:

All accounts are strongly encouraged to "opt-in" to the new domain as early as possible to allow time for troubleshooting if problems arise.

Accounts can switch back to the legacy domain if problems do occur. 


How to change the domain

When you are satisfied that your account is ready to migrate:

  1. Log in to Acrobat Sign as an account-level administrator

  2. Navigate to Account > Account Settings > Account Setup

  3. Click the Update now button

    Update the domain

  4. A check list of the important actions is presented in an overlay.

    Review each point and check them off when you are confident the concern is properly addressed for your account.

    Verify checklist

  5. Click OK when all of the boxes are checked, and then click Save:

    • You will be logged out automatically, and will have to authenticate to the new domain
    • If you have a bookmark to log in, edit the URL to use adobesign.com instead of echosign.com
    Note:

    Bookmarks to the old domain (echosign.com) can prompt multiple Cookie enablement requests when the login process shifts the user to the new domain (adobesign.com). 

    It is recommended that users be notified to update their bookmarks to target the new login domain.


Revert back to the legacy domain

If you have to revert back to the legacy domain for any reason, the process is the same as the initial switch.

  • Accounts that have SAML enabled will need to re-configure their SAML IdP settings to use the old client
  • Accounts that employ the Adobe Acrobat Sign for Salesforce integration will need to re-link the applications after the switch
  1. Log in to Acrobat Sign as an account-level administrator

  2. Navigate to Account > Account Settings > Account Setup

  3. Click the Update now button, and then click Save

    • You will be logged out automatically
    Update the domain


Common questions

Below you will find a list of common questions about the domain migration.

If you can not find an answer for your question here, please contact your success manager or customer support.

Case: Account migrated to adobesign.com domain - API call made using echosign.com domain

  • Sample Request URL:  https://api.na2.echosign.com/api/rest/v6/baseUris
  • Sample Response

{

  "apiAccessPoint": "https://api.na2.adobesign.com/",

  "webAccessPoint": "https://secure.na2.adobesign.com/"

}

Note:

The domain in the sample response, points to adobesign.com even if the request was made from echosign.com.

  • If you check the response for echosign.com, then your check will fail
    • Replace the echosign.com hostname to adobesign.com if there are any hardcoded cases

Case: Account migrated to adobesign.com domain - API call made using adobesign.com domain

  • Sample Request URL:  https://api.na2.adobesign.com:443/api/rest/v6/baseUris
  • Sample Response

1

2

3

4

{

  "apiAccessPoint": "https://api.na2.adobesign.com/",

  "webAccessPoint": "https://secure.na2.adobesign.com/"

}

No.

Accounts on any *.documents.adobe.com URL are not being migrated.

Only accounts on the *.echosign.com domain are being migrated to the adobesign.com domain. 

No.

The same IP ranges (listed on the system requirements page) are being used for the adobesign.com domain.

Nothing new is being added; nothing is being removed.

 Adobe

Get help faster and easier

New user?