Go here to access the Adobe Acrobat Sign application package on the Salesforce AppExchange.
Adobe Acrobat Sign for Salesforce: Installation Guide provides instructions on how to install the Acrobat Sign extension into your Salesforce.
Adobe Acrobat Sign integration for Salesforce is designed to provide you with a smooth e-signing experience that has multifold benefits, including:
Acrobat Sign for Salesforce works from any browser and mobile device. The app is available from the AppExchange and supports the following Salesforce Editions:
Before downloading the Adobe Acrobat Sign for Salesforce package, you must contact the Acrobat Sign support team to ensure that:
Note: The user email in Adobe Acrobat Sign must match the primary email of the user. Else, you must Change the Adobe Acrobat Sign email value.
To successfully install and use Adobe Acrobat Sign for Salesforce, you may need to make the following settings in the Salesforce environment:
Note: Salesforce administrators cannot launch the Set Up wizard in Edge browsers.
Known Issue with the Acrobat Sign for Salesforce application:
If you've enabled account sharing on your Acrobat Sign account, the users that are not included in the agreement cannot view the agreement in the Salesforce environment, unless:
Note: You can use Adobe Acrobat Sign to view the agreement.
For any questions or additional assistance, contact Adobe Acrobat Sign Support or your designated Client Success Manager.
New Customer Testing and Installing for the First Time—For those who are new to Adobe 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 v23.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.
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.
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:
Go here to access the Adobe Acrobat Sign application package on the Salesforce AppExchange.
Select Get It Now.
Select an appropriate login option:
When prompted, select which environment to install into, Production or Sandbox
On the Confirm Installation Details page:
When prompted to log in to your Salesforce organization, provide your login credentials and select Login into Salesforce.
On the Install Adobe Acrobat Sign page:
Once the installation is complete, you receive an email notification that the package is installed.
To verify the installation go to Setup > Platform Tools > Apps > Installed Packages.
The Installed Package page displays your installation information, as shown below.
You must complete the following configuration steps before you can start sending Adobe Acrobat Sign agreements from Salesforce:
Acrobat Sign installs four permission sets to facilitate granting field-level access to the custom objects:
Assign yourself and any other full-access Admins the Adobe Acrobat Sign Integration User permission set.
All users of the Adobe Acrobat Sign package will need to have Adobe Acrobat Sign User applied before they can use the service.
Select App Launcher> Adobe Acrobat Sign for Salesforce.
Select the Adobe Acrobat Sign Admin tab to launch the installation wizard.
On the Adobe Acrobat Sign for Salesforce Setup wizard:
The Enable Adobe Analytics and add *.adobe.io to CSP Trusted Sites feature is enabled by default for most newly installed accounts.
This setting allows Adobe Acrobat Sign to collect usage data to improve the product. This data is used only for development and not for marketing purposes. Admins can enable/disable this feature on the Adobe Acrobat Sign Admin tab.
Note: Organizations originating in Canada and the European Union have this option disabled by default.
Select Next.
On the “Step 2: Enable Adobe Acrobat Sign Automatic Status Updates” page:
From the bottom of the page, select Next.
Once the setup is complete, the Setup Wizard displays a message saying Congrats! Your setup is complete.
Select Done.
You can now start using Adobe Acrobat Sign for Salesforce.
After the initial setup, you can use the Adobe Acrobat Sign Admin tab to access advanced Adobe Acrobat Sign features, account setup, and other resources.
You can improve the usability of Adobe Acrobat Sign by adding the Agreement object to the page layouts. Users need to interact with the Agreements object most when sending documents for signature.
Go to the Adobe Acrobat Sign Admin tab and select Send for Signature Components.
On the dialog that appears, select a page layout that you want to modify from the given options: Account, Opportunity, Contract, Lead, and Contact.
From the left panel of the object page that appears, select Page Layouts.
Select the page layout that you want to edit.
From the left panel, select Related Lists, then drag and drop the Agreements object to the desired place on the page layout.
Select Save.
With the Agreement object in place, you can see all agreements related to the Salesforce object, or send new agreements directly from the relevant record.
Adobe Acrobat Sign allows for a very wide array of optional configuration options that can elevate your e-signing experience.
To learn about the optional and valuable configurations, refer to the Advanced Configuration guide.
Delegator roles are only supported in the Lightning environment
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:
Navigate to Setup > Platform Tools > Custom Code > Custom Settings.
On the Custom Settings page, select Adobe Sign Settings.
On the Adobe Sign Settings page, select Manage.
Select New (or Edit, if you have configured settings before).
Select the checkboxes for values you want to adjust with the “Find” function (cmd/ctrl + f):
Select Save.
You may associate Adobe Acrobat 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 shows all the related Agreements on that object’s page.
Follow the steps below to associate Agreements with an object:
Navigate to Setup > Platform Tools > Objects and Fields > Object Manager.
Select Agreement.
From the lef panel, select Fields & Relationships.
Select New.
In Step 1. Choose the field type, select Lookup Relationship, then select Next.
In Step 2. Choose the related object, select your object (Order in this example) from the drop-down, then select Next.
In Step 3. Enter the label and name for the lookup field, enter a Field Name and select Next.
In Step 4 and Step 5, select Next.
In Step 6. Add custom related lists, ensure that the Add Related List option is enabled then select Save.
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 Acrobat Sign provides four second-factor identity verification methods (US-based customers have five options when KBA is included):
There are two configuration options to consider:
To enable the advanced authentication methods in the Adobe Acrobat Sign account:
Log in to Adobe Acrobat Sign with your Account Administrator userID.
Navigate to Account Settings > Send Settings > Identity Authentication Methods.
Check the options you want to enable.
Select Save.
To adjust the available authentication methods in Salesforce:
Navigate to Setup > Platform Tools > Custom Code > Custom Settings.
On the Custom Settings page, select Adobe Sign Settings.
Select Manage.
Select New (or Edit).
Find the values you need to adjust using the “Find” function (cmd/ctrl + f).
Method |
Setting |
Default |
---|---|---|
Password |
Hide Signing Password |
Disabled |
Phone |
Enable Phone Authentication |
Disabled |
KBA |
Disable Knowledge Based |
Enabled |
Government ID |
Enable Government ID Authentication |
Disabled |
Once you've made the changes, select Save
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.
To enable the options in the Adobe Acrobat Sign account:
Log in to Adobe Acrobat Sign with your Account Administrator userID.
Navigate to Account Settings > Send Settings > Identity Authentication for Internal Recipients.
Select Enable different identity authentication methods for internal recipients.
Check the verification options you want to allow for internal signers.
Select Save.
To adjust the available authentication methods in Salesforce:
Navigate to Setup > Platform Tools > Custom Code > Custom Settings.
On the Custom Settings page, select Adobe Sign Settings.
Select Manage.
Select New (or Edit).
It loads the Adobe Sign Settings page.
Find the values you need to adjust:
Select Save.
If you are using Salesforce Professional Edition, please make sure to follow the instructions in the following sections after completing the standard installation steps.
Navigate to Setup > Platform Tools > Objects and Fields > Object Manager.
From the left panel, select Agreement.
From the left panel, select Page Layouts.
Under Page Layout Name, select Agreement Layout Professional.
With Fields selected, drag and drop the following fields to the page layout:
Select Save.
Navigate to Setup > Platform Tools > Objects and Fields > Object Manager.
From the left panel, select the Recipient.
Select Page Layouts.
Under Layout Name, select Echosign Recipient Layout Page.
With Fields selected, drag and drop the following fields to the page layout:
Select Save.
All the custom objects shipped in Adobe Acrobat 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 guidelines.
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:
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.
The below settings are not specific to the Adobe Acrobat 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 Acrobat Sign does not want to override the admin’s configured setting.
However, we strongly recommend enabling these settings for the following reasons:
Clickjacking attacks typically use a combination of stylesheets, iframes, and form elements to convince a targeted user that they are interacting with an innocuous page when instead, they are typing into or clicking on an invisible frame controlled by an attacker.
A successful clickjacking attack could circumvent cross-site request forgery (CSRF) protections that attempt to confirm transactions with the user, resulting in an unwanted transaction.
This can be prevented by modifying session security settings and enabling:
Without the HttpOnly attribute set on a cookie, an attacker can use client-side JavaScript for a cross-site scripting attack and capture the cookie's value via the injected script.
Note that the restrictions imposed by the HttpOnly attribute can potentially be circumvented in some circumstances and that numerous other serious attacks can be delivered by the client-side script injection, aside from simple cookie stealing.
You can prevent this threat by modifying session security settings and enabling Require HttpOnly attribute.
This setting commands the web client (i.e., browser) to ensure that all subsequent requests are forced to use HTTPS, thereby helping prevent man-in-the-middle attacks that can occur if the user or application ever initiates any HTTP requests.
Enable HSTS for Sites and Communities.
During installation, you may have only granted Administrators access to Adobe Acrobat Sign for Salesforce.
To extend access to additional user profiles, refer to Adobe Acrobat Sign for Salesforce: Granting Profile Access.
If the Salesforce password or username has changed for the account linked to Adobe Acrobat Sign for your Salesforce Org, remember to update it so that status updates continue to work appropriately for agreements in your Org.
If a user in your Salesforce organization has an email address change, that user’s email address must also be changed in Adobe Acrobat Sign.
Acrobat Sign users can change their own email addresses. To learn how to change email addresses in the Acrobat Sign Help, refer here.
Acrobat Sign account administrators can also change the email addresses of users using the bulk update feature. To learn how to use bulk updates in the Acrobat Sign Help, refer here.
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:
An optional Analytics setting is implemented to allow Adobe Acrobat Sign to collect usage data to improve the product. This data is used only for development and not for marketing purposes.
Note that:
Bejelentkezés a fiókba