Adobe Acrobat Sign for Salesforce works from any browser and mobile device. The app is available from the AppExchange and supports the following Salesforce Editions:

• Professional
• Enterprise
• Unlimited
• Developer
• Performance

Reap immediate benefits for your document and signature workflows:

• Save time and money by eliminating snail mail, overnighting, and faxing
• Send contracts for e-signature or approval directly from Salesforce, access real-time contract history, and view saved contracts from any object
• Track deals in real-time across your organization and also get updates with Chatter when agreements are viewed, signed, canceled, or declined
• e-Sign in over 20 languages and support fax-back service in 50+ locales worldwide
• Merge Salesforce data into documents before sending and map signer data back to Salesforce objects – automatically and seamlessly
• Create reusable Agreement Templates for sending options and enable one-click 'Send for Signature’ buttons to send custom agreements from any Salesforce object
• Native integrations with Conga Composer, Apttus, Selectica, Drawloop, Zuora, Emptoris, and more
• All Adobe Sign objects and pages in Salesforce are translated to all 16 languages supported by Salesforce.com so your Salesforce users can send and track all their agreements in their native language

Prerequisites

There are a few prerequisites that you need to be aware of and some basic discoveries that will help ensure your deployment runs smoothly.

Before downloading the package, contact the Acrobat Sign support team to:

• Ensure the Acrobat Sign account is properly provisioned in the Salesforce channel
• Verify the correct userID (email address) is designated as an administrator in the Acrobat Sign system
• Provide all of the owned domains that your users could be using in their email addresses (Do not include public use domains like gmail.com or yahoo.com)
• Obtain a list of all users in the Adobe Acrobat Sign system using your owned domains
  • You may need to request valid users to be moved into your Adobe Acrobat Sign account
  • It is vital that the user email in Adobe Acrobat Sign match the primary email of the user. In the event that it is not, the Adobe Acrobat Sign email value should be changed.

Within the Salesforce environment there are a couple of items to take note of:

• Disable any pop-up blockers during installation/configuration
• Adobe Sign for Salesforce requires that you enable cookies on your browser. Please also check that third-party cookies are enabled as that is required in some browsers
• My Domain must be enabled in order to use Adobe Sign in the Lightning environment 
• Navigate to Setup > Settings > Security > Session Settings and ensure:
  • Lock sessions to the IP address from which they originated is disabled
• Licensing - Adobe Acrobat Sign Users and Administrators need to be assigned a valid license to use the service.
• File Limitations – The file upload size is limited to ~700KB in Salesforce Lightning. You can configure Salesforce to send documents from the library up to 9MB in the background (see Configure Salesforce to Send Large Documents). For most admins, this is worth configuring early.

Supported Browsers

• Chrome - current version
• Firefox - current version
• Safari - current version
• Edge - current version
  • Salesforce Administrators will not be able to launch the Set Up wizard in Edge browsers

Known Issues

There is a known issue for customers that have enabled account sharing on their Adobe Acrobat Sign account.

After account sharing is enabled, users that are not party to the agreement will not be able to view the agreement (in the Salesforce environment), unless:

• The agreement was created from a shared library template in the Adobe Acrobat Sign library
• The library template is shared in a manner that encompasses the viewer. Either:
  • Shared for all users in the account
  • Shared at the group level, where the sender and viewer are in the same group

The agreement is still viewable in the Adobe Acrobat Sign environment.

Adobe Acrobat Sign Support

If you've any questions or require additional assistance, open a ticket with Acrobat Sign Support or your contact your designated Client Success Manager.

Install Adobe Acrobat Sign for Salesforce v24

New Customer Testing and Installing for the First Time—For those who are new to Acrobat Sign for Salesforce, you can try installing and start sending test agreements within minutes.  Basic installation to the point of functionality takes only 15 minutes

Existing Customers Upgrading from Previous Versions—We strongly encourage customers to upgrade to the latest version of the package to take advantage of the latest features and also get the best support. See the Upgrade Guide for more information if you are upgrading to Adobe Acrobat Sign for Salesforce v24.x from a prior version.

The Lightning experience is fully supported by the Adobe Acrobat Sign package, and these instructions are written using the Lightning interface.

Important Sandbox Testing Notes

When testing on a Salesforce Sandbox, you often are not using a real email address that you have access to. (e.g., user@company.com.sandboxname) If so, we strongly recommend that you change your Salesforce Sandbox email to a real email address before you begin testing so that your Adobe Acrobat Sign account is tied to a real email address. If not, it may be problematic if you want to change your email address later when you move to Production because your Adobe Acrobat Sign account will be tied to an email address that does not exist and cannot be verified to make email changes.

Installing the Adobe Acrobat Sign package

You must have a Salesforce account to install the Adobe Acrobat Sign package. If you do not, you can create one during the installation process as described below:

Post-Install Configurations (Required)

A few simple setup steps are required before you can start sending Adobe Acrobat Sign agreements from Salesforce. These steps are described below.

Apply the Acrobat Sign Permission Sets as needed

Adobe Sign installs four permission sets to facilitate granting field level access to the custom objects:

• Adobe Sign User - Minimum required permissions for an Adobe Sign for Salesforce sender user. Includes limited access to the required components included in the managed package: objects, fields, tab, classes and pages
• Adobe Sign Community User - Minimum required permissions for an Adobe Sign for Salesforce community user
  • Includes limited access to the required components included in the managed package: objects, fields, tab, classes and pages
• Adobe Sign Admin - Minimum required permissions for an Adobe Sign for Salesforce administrator user. Includes full access to all of the components included in the managed package: objects, fields, tab, classes and pages.
• Adobe Sign Integration User - All required permissions for an Adobe Sign for Salesforce integration user. Includes all admin access as well as access to all org data.

Assign yourself and any other full-access Admins the Adobe Sign Integration User permission set.

All users of the Adobe Sign package will need to have Adobe Sign User applied before they can use the service.

Launch the AdobeAcrobat Sign Setup Wizard

Add the Agreements Object to Page Layouts

You can greatly improve the usability of Adobe Sign by adding the Agreement object to the page layouts that your users interact with most when sending documents for signature.

Optional Post-Install Configurations

What follows are the optional configurations that will move your installation from functional to valuable. Adobe Sign allows for a very wide array of configuration options, and the rest of this document describe the most commonly used adjustments. The less common (read: situationally valuable) configurations can be found in the Advanced Configuration guide.

Enable Delegator Roles for Recipients

The Delegator roles are a placeholder for the situations where you know someone will have to interact with the agreement, but you can’t determine who that will be at the time you are sending the agreement.  The Delegator is not expected to act, so no fields are available to them when they receive the document.  Once they have delegated the agreement, the delegatee will have full access to all of the fields designated for their access.

There are delegator options for all five of the standard roles (signer, approver, acceptor, form filler, and certified recipient).

To enable the Delegator roles:

Adding Agreements to other Salesforce Objects

You may associate Adobe Sign Agreements with Salesforce objects of your choosing (standard or custom objects). This enables you to create Agreements that are linked to those objects and that show all the Agreements that relate to an object on that object’s page.

The instructions below describe how to associate Agreements with an Order object, but they can be applied to any other object in your Salesforce Organization.

Advanced Identity Authentication Methods

Legally, authenticating to an email account (and thus the signing URL on the email) is sufficient to capture a binding signature. However, in many cases, a second factor authentication for the signer’s identity is desired. Adobe Sign provides four second-factor identity verification methods (US based customers have five options when KBA is included):

• Password—Recipients enter a password to view and sign the agreement.
  • Password must be communicated to recipients out of band
  • Enabled by Default
• Phone Authentication—Recipients are sent an automated text (SMS) message or phone call with the required code.
  • Per transaction costs apply
  • Disabled by default
• Knowledge Based Authentication—Recipients answer questions taken from publically accessible databases to verify their identity.
  • Per transaction costs apply
  • US based signers only
  • Disabled by default
• Government ID Authentication - Recipients submit an image of a passport or government issued ID/Driver License
  • Per transaction costs apply
  • Must be enabled by your success manager in the Adobe Sign system
  • Disabled by default

There are two configuration options to consider:

• Which (if any) second factor verification methods do you want to enable?
  • Keep in mind that Phone, KBA, and Government ID authentication have a cost attached, so they should not be enabled unless there is contract in place permitting this usage.
• Do you want all signers to always use the same verification method, or do you want to set per recipient verification?
  • Also allowed is the idea of “internal” vs “external” signing methods. Adobe Sign classifies any email address included in your Adobe Sign account as an internal signer, whereas any email not in your account is external.
  • Strongly recommended if you are using a paid authentication method and you collect internal counter-signatures.

Enable Advanced Identity Authentication Methods (Adobe Sign)

First, you will need to enable the options in the Adobe Sign account.  To do so:

Enable Advanced Identity Authentication Methods (Salesforce)

To adjust the available authentication methods in Salesforce:

Enable Advanced Identity Authentication per Recipient (Adobe Sign)

Customers that implement second factor verification will likely want to enable separate signer identity methods so their internal signers aren’t challenged as vigorously.

The configurable settings are in the same location as the verification methods.

First, you will need to enable the options in the Adobe Sign account.  To do so:

Enable different Identity Authentication methods for internal recipients (Salesforce)

To adjust the available authentication methods in Salesforce:

Adobe Sign for Salesforce - Professional Edition

If you are using Salesforce Professional Edition, please make sure to follow the instructions in the following sections after completing the standard installation steps.

Things to consider

Adobe Sign configurations

All the custom objects shipped in Adobe Sign for Salesforce are set to Private access at the Organization Default Level Setting.  This is in place to ensure proper level security as per Salesforce Security guidlines.

Admins should carefully read through and understand the Record Level Sharing (and other permission models) in Salesforce. This trailhead is useful if you need a refresher.

If your business requirements warrant a less restrictive environment, that can be achieved:

• Navigate to Setup > Security > Sharing Setting 
• Edit the sharing permission to “Public Read/Write” for the objects as per your requirement 
• Click Save when done

Changing objects to Public access means the record can be viewed/edited by all the authenticated users.

We recommend using role hierarchy, groups, profile permission, permission sets, etc for this purpose instead of changing the Organization wide default.

Salesforce controls

The below settings are not specific to the Adobe Sign for Salesforce application, but they are resources that are used. 

Because any change to these settings apply to the whole Organization (including other apps installed in the Org, as well as custom code), Adobe Sign does not want to override the admin’s configured setting.

However, we strongly recommend enabling these settings for these reasons:

Common Problems

Granting Access to Additional Profiles

During installation, you may have only granted Administrators access to Adobe Sign for Salesforce. If you need to extend access to additional user profiles, please refer to the documentation for Granting Profile Access for Adobe Sign for Salesforce.

Updating Email Addresses or Passwords

Administrator Salesforce Account Password Changes

If the Salesforce password or username has changed for the account linked to Adobe Sign for your Salesforce Org, remember to update it so that status updates continue to work properly for agreements in your Org.

    1. Navigate to the Adobe Sign Admin page and click the Enable Automatic Status Updates link.

    2. Click the Enable button and allow access to Adobe Sign when prompted

Updating user email addresses in Adobe Sign

If a user in your Salesforce organization has an email address change, that user’s email address must also be changed in Adobe Sign.

Adobe Sign users can change their own email addresses. Users can find information on changing their email addresses in the Adobe Sign Help by clicking here.

Adobe Sign account administrators can also change the email addresses of users using the bulk update feature. Administrators can find information on using bulk update in the Adobe Sign Help by clicking here.

Lead lookup in Professional and Enterprise editions fails

Professional and Enterprise editions will fail to do a Lead lookup if the user's Profile does not permit access to the Mobile field of the Lead object.

To correct:

• Navigate to: Setup > Platform Tools > Objects and Fields > Object Manager
• Select Lead from the list of objects on the left of the window
• Select Fields & Relationships from the options on the left rail
• Click on the Field Label for the Mobile field
• Click the Set Field-Level Security button
• Set the appropriate Profiles to enable (check) Visible and Read-Only
• Click Save
  

Enable/Disable analytics collection

An optional Analytics setting has been put in place to allow Adobe Sign to collect usage data to improve the product. This data is used only for development and not for marketing purposes.

The analytics setting is enabled by default for most customers

• Customers in Canada and the European Union will have analytics disabled by default

You can disable/enable the setting by clicking the Analytics Settings link on the Adobe Sign Admin tab: