Log in to your Acrobat Sign for Salesforce account using admin credentials.
- Adobe Acrobat Sign Integrations
- What's New
- Product Versions and Lifecycle
- Acrobat Sign for Salesforce
- Install the package
- Configure the package
- User Guide
- Developer Guide
- Advanced Customization Guide
- Field Mapping and Templates Guide
- Mobile App User Guide
- Flows Automation Guide
- Document Builder Guide
- Configure Large Documents
- Upgrade Guide
- Release Notes
- FAQs
- Troubleshooting Guide
- Additional Articles
- Acrobat Sign for Microsoft
- Acrobat Sign for Microsoft 365
- Acrobat Sign for Outlook
- Acrobat Sign for Word/PowerPoint
- Acrobat Sign for Teams
- Acrobat Sign for Microsoft PowerApps and Power Automate
- Acrobat Sign Connector for Microsoft Search
- Acrobat Sign for Microsoft Dynamics
- Acrobat Sign for Microsoft SharePoint
- Overview
- SharePoint On-Prem: Installation Guide
- SharePoint On-Prem: Template Mapping Guide
- SharePoint On-Prem: User Guide
- SharePoint On-Prem: Release Notes
- SharePoint Online: Installation Guide
- SharePoint Online: Template Mapping Guide
- SharePoint Online: User Guide
- SharePoint Online: Web Form Mapping Guide
- SharePoint Online: Release Notes
- Acrobat Sign for Microsoft 365
- Acrobat Sign for ServiceNow
- Acrobat Sign for HR ServiceNow
- Acrobat Sign for SAP SuccessFactors
- Acrobat Sign for Workday
- Acrobat Sign for NetSuite
- Acrobat Sign for SugarCRM
- Acrobat Sign for VeevaVault
- Acrobat Sign for Coupa BSM Suite
- Acrobat Sign Developer Documentation
Overview
Adobe Acrobat Sign for Salesforce: Large Documents & Push Agreements Services Guide explains how to configure Acrobat Sign for Salesforce to send Large Documents (greater than 4.0 MB from the send agreement page and 9.0 MB when sending in batch) or Push Agreements for agreements created outside of the Salesforce environment.
To establish and use the Large Documents and Push Agreement services, you must define the callback environment. The callback environment can be used for one or both services. The callback environment requires you to create a new and dedicated user and profile, which ensures that:
- A known and minimally authorized set of permissions are in effect.
- The functionality does not break due to a disabling of the user.
To establish the Callback environment and use Large Documents and Push Agreements services, you must complete the following steps:
- You must have the Adobe Acrobat Sign for Salesforce package installed.
- You must have My Domain configured to permit the OAuth authentication of the Callback User.
Salesforce professional edition doesn’t support Large document transactions or Push agreements.
You must create a dedicated user to grant object permissions for the callback process. To do so:
-
-
- Log in as the newly created callback user.
- Navigate to App Launcher > Adobe Acrobat Sign Admin.
- Under the Callback User, select Link an Account.
- On the Allow Access dialog, select Allow.
It prompts you to log into your Salesforce account again. - Once you are logged in, go to the Adobe Acrobat Sign Admin page and verify that the callback user is linked.
- Log in to Acrobat Sign for Salesforce account using Standard System Admin profile.
- On the ‘Sign for Salesforce’ lightning page, select Adobe Acrobat Sign Admin tab.
- Under the Callback User, select Link an Account.
- On the Allow Access dialog, select Not you?
- On the Salesforce log-in page, enter the credentials for the callback user and then log in.
It takes you back to the Adobe Acrobat Sign Admin page. Verify that the callback user is linked.
Acrobat Sign admins, on the Commercial Cloud, must establish and configure a site specifically for the Adobe Acrobat Sign Callback. This setup ensures that agreement updates are promptly pushed to Salesforce and large documents can be easily downloaded. Please note that the push agreements feature isn’t available for Government Cloud users.
Before using Salesforce sites in your organization, you must register a Force.com domain, which is used for all the Salesforce sites in your account. When choosing a domain name, keep it short to prevent exceeding Adobe Acrobat Sign's 255 character limit for callback URLs.
-
If you want to use an already registered site, you can skip this step.
Else, follow these steps to register your site domain name:
- Enter the desired domain name in the text field after the https://
- Select Check Availability to ensure that the domain is available. Once you have an available domain, a success message displays.
- Accept the Terms of Use and select Register My Force.com Domain.
-
On the Site Edit page:
- Set the Site Label value to Adobe Acrobat Sign Callback.
- Select the Site Name field. It automatically sets the value to Adobe_Acrobat_Sign_Callback.
- Set the Site Contact value to a Salesforce user who will receive notifications about Sites. In most cases, this is the account admin.
- Set the Default Web Address value to AdobeAcrobatSignCallback.
- Select Active checkbox.
- Set the Active Site Home Page value to EchoSignCallback.
EchoSign is a legacy name for the Adobe Acrobat Sign. - Select Save.
-
Add the IP ranges for public access settings in the Site to restrict them to Adobe Acrobat Sign IPs. To do so:
- From the Site Details page for your Callback Site, select Public Access Settings.
- Select Login IP Ranges.
- Select New.
- In the Login IP Ranges dialog, enter the first IP address range:
- Start IP Address: 52.71.63.224
- End IP Address: 52.71.63.255
- Description: Acrobat Sign
- Select Save.
- Repeat steps 2-5 for the IP address ranges in the table below.
To determine the IP ranges associated with your region, refer to one of the following list of IP addresses based on the environment that you are using:
List of sample IP address ranges:
Start IP End IP Description 13.126.23.0 13.126.23.31 Adobe Acrobat Sign 3.236.206.64 3.236.206.95 Adobe Acrobat Sign
40.67.154.249 40.67.154.249 Adobe Acrobat Sign
40.67.155.112 40.67.155.112 Adobe Acrobat Sign
40.67.155.147 40.67.155.147 Adobe Acrobat Sign
40.67.155.185 40.67.155.185 Adobe Acrobat Sign
44.234.124.128 44.234.124.159 Adobe Acrobat Sign
51.105.221.160 51.105.221.191 Adobe Acrobat Sign
52.196.191.224 52.196.191.255 Adobe Acrobat Sign
52.35.253.64 52.35.253.95 Adobe Acrobat Sign
52.48.127.160 52.48.127.191 Adobe Acrobat Sign
52.58.63.192 52.58.63.223 Adobe Acrobat Sign
52.65.255.192 52.65.255.223 Adobe Acrobat Sign
52.71.63.224 52.71.63.255 Adobe Acrobat Sign
The final Login IP ranges for the Adobe Acrobat Sign Callback Site should display as follows:
Note:If you get a “The list of IP Ranges does not cover your current IP address….” error, enable the Save this IP Range even though it doesn’t cover my current IP address option and then select Save.
Large documents provide default support for sending transactions and background actions, each with its own size limit as follows:
- Send transactions— You can send a single document or multiple documents totaling up to 4.0 MB via the 'Send for signature' option on the Agreements page.
- Background actions—These allow sending of a single document or multiple documents totaling up to 9.0 MB. For more details, see the Advanced customization guide.
To enable sending large documents, you must complete the following steps:
- Edit the Callback User Profile to grant additional access.
- Enable the LargeFileDownloadService Apex class for the site.
- Update the Custom Settings to use the Callback URL.
To enable Object Level Permissions for the Adobe Acrobat Sign Callback Site User:
- Navigate to the Profiles page and then for the callback user that you created (Demo callback user in this example), select Edit.
- Scroll down to Custom Object Permissions and enable all the permissions for Agreements object: Read, Create, Edit, Delete, View All, Modify All.
- Select Save.
You must adjust your Adobe Acrobat Sign Callback site to include the 'LargeFileDownloadService' Apex class for visibility.
The instructions below align with the enhanced profile interface. For details on profile interfaces, see Salesforce Profiles.
-
On the Adobe Acrobat Sign Settings Edit page:
- In the Callback URL Adobe to Salesforce Site field, paste the URL of the ‘Secure web address’ that you copied after configuring your Adobe Acrobat Sign Callback site.
Ensure that the address prefix is ‘https’ and not ‘http’. - Select Save.
It enables the Large Document Service.
- In the Callback URL Adobe to Salesforce Site field, paste the URL of the ‘Secure web address’ that you copied after configuring your Adobe Acrobat Sign Callback site.
The Acrobat Sign API allows you to send signature requests, create web forms, and embed them on your website. These agreements are then pushed and created in Salesforce as if dispatched directly from it. You can also send agreements via the adobesign.com web application, and they'll sync back to Salesforce.
To enable Push Agreements:
To enable the Push Callback Agreements to function properly post the webhook 2.0 migration, you must add the Webhook IP addresses to the Site callback user profile.
After adding the Visualforce page, you’re returned to the Site Details page for the callback site. Follow the steps below to edit the page:
- Select Public Access Settings.
- On the Adobe Acrobat Sign Callback Profile page, select Edit.
- Scroll down to the Standard Objects Permissions section.
- Enable Read and Create for the following objects: Account, Contacts, Contracts, Leads, and Opportunities.
- Select Save.
It returns you to the callback profile. - To make field-level adjustments where required, scroll down to the Field-Level Security section, and then edit the settings for the the following fields, as described:
- Contact
- Account: ensure that you select the checkboxes for Read Access and Edit Access.
- Email: ensure that you select the checkboxes for Read Access and Edit Access.
- Name: ensure that you select the checkboxes for Read Access and Edit Access.
- Lead
- Company: ensure that you select the checkboxes for Read Access and Edit Access.
- Email: ensure that you select the checkboxes for Read Access and Edit Access.
- Name: ensure that you select the checkboxes for Read Access and Edit Access.
- Company: ensure that you select the checkboxes for Read Access and Edit Access.
- Contact
To have all agreements sent outside of Acrobat Sign in your account created and transferred to Salesforce, follow these steps:
-
Copy the secure URL address from the Acrobat Sign Callback Site you created and append /echosign_dev1__EchoSignAgreementPushCallback to compose the callback URL.
-
Contact Adobe Support and provide them with your callback URL to set as your Adobe Acrobat Sign account’s default callback URL.
Example: If your site address is https://<MyDomain>.my.salesforce-sites.com/AdobeSignCallback, your Acrobat Sign API URL should be: https://<MyDomain>.my.salesforce-sites.com/AdobeSignCallback/echosign_dev1__EchoSignAgreementPushCallback.
Adobe Support must enter your Adobe Acrobat Sign userID for the default callback URL API user setting. Ensure all Salesforce accounts are set to add the document key to the callback URL.
For sending agreements via the API:
-
Copy the secure URL from the Adobe Sign Callback Site you've created and append /echosign_dev1__EchoSignAgreementPushCallback to create the callback URL for the Adobe Acrobat Sign API.
Example: If your site address is https://<MyDomain>.my.salesforce-sites.com/AdobeSignCallback, your Acrobat Sign API URL should be: https://<MyDomain>.my.salesforce-sites.com/AdobeSignCallback/echosign_dev1__EchoSignAgreementPushCallback
-
When sending an agreement or creating a web form through the API you must provide a callback URL.
See the current list of Acrobat Sign Document API Methods and refer to the API parameter ‘CallbackInfo’. -
Ensure that your account settings are set to append the document key to the callback URL that should be the default for Salesforce customers using Adobe Sign.
For any issues, Contact Adobe Support. -
Go to Push Mappings Settings to define preferences for how records are created when agreements are pushed to Salesforce.