Kullanıcı Kılavuzu İptal

Acrobat Sign for Salesforce: Configure the package

Ara

Son güncelleme: 30 Kas 2023

Adobe Acrobat Sign Entegrasyonları
Yenilikler
Ürün Sürümler ve Yaşam Döngüsü
Salesforce için Acrobat Sign
Microsoft için Acrobat Sign
1. Microsoft 365 için Acrobat Sign
  1. Kurulum Kılavuzu
2. Outlook için Acrobat Sign
  1. Kullanıcı Kılavuzu
3. Word/PowerPoint için Acrobat Sign
  1. Kullanıcı Kılavuzu
4. Teams için Acrobat Sign
5. Microsoft PowerApps ve Power Automate için Acrobat Sign
  1. Kullanıcı Kılavuzu
  2. Sürüm Notları
6. Microsoft Arama İşlevi için Acrobat Sign Bağlayıcı
  1. Kullanıcı Kılavuzu
  2. Sürüm Notları
7. Microsoft Dynamics için Acrobat Sign
8. Microsoft SharePoint için Acrobat Sign
ServiceNow için Acrobat Sign
HR ServiceNow için Acrobat Sign
1. Kurulum Kılavuzu
SAP SuccessFactors için Acrobat Sign
Workday için Acrobat Sign
NetSuite için Acrobat Sign
1. Kurulum Kılavuzu
2. Sürüm Notları
SugarCRM için Acrobat Sign
VeevaVault için Acrobat Sign
Coupa BSM Suite için Acrobat Sign
1. Kurulum Kılavuzu
Acrobat Sign Geliştirici Belgeleri

Overview

Welcome to the comprehensive guide on configuring the 'Acrobat Sign for Salesforce package. This document provides step-by-step instructions to seamlessly set up and enhance the integration between Adobe Acrobat Sign and Salesforce. Using the powerful capabilities of both platforms, you can streamline your document signing processes and enhance your productivity.

Adobe Acrobat Sign allows for a wide array of optional configuration options to elevate your e-signing experience. Refer to the following topics to learn how to:

Control Adobe Acrobat Sign access
Enable Salesforce settings
Switch to Acrobat Sign Sandbox environment
Add 'Agreements' Object to Page Layouts
Enable Delegator roles for recipients
Add Agreements to other Salesforce Objects
Enable Advanced Identity Authentication Methods
- In Acrobat Sign
- For each recipient in Acrobat Sing
- In Salesforce
- For internal recipients in Salesforce
Grant access to additional profiles
Update email address or password
Enable/Disable analytics collection (For commercial cloud only)

To learn about the optional and valuable configurations, refer to the Advanced Configuration guide.

Control Adobe Acrobat Sign access

The custom objects included in the Adobe Acrobat Sign for Salesforce package have a default access level of "Private" at the organization level. This default setting is implemented to ensure adherence to Salesforce Security guidelines and maintain proper security levels.

As an administrator, it is essential to thoroughly read and understand Salesforce's Record Level Sharing and other permission models.

If your business requirements demand a less restrictive environment, you have the option to make adjustments. Here's how you can achieve that:

Go to Setup > Security > Sharing Settings.
Edit the sharing permission for the objects according to your requirements, setting it to Public Read/Write if needed.
Select Save.

By changing the objects to "Public" access, all authenticated users can view and edit the records. However, instead of modifying the Organization-wide default, we recommend utilizing other mechanisms such as role hierarchy, groups, profile permissions, and permission sets to achieve your desired access control.

These alternative methods provide more granular control over record access, ensuring a well-structured and secure environment within your Salesforce instance.

Enable Salesforce settings

The following settings are not specific to the Acrobat Sign for Salesforce application, but they are resources that are utilized by it:

Application Vulnerable to Clickjacking
HttpOnly Attribute Not Set on Sensitive Cookies
HTTPS Strict Transport Security (HSTS) Not Enforced

It's important to note that any modifications made to these settings will impact the entire organization, including other applications installed in the org, as well as custom code. As a result, Adobe Acrobat Sign does not want to override the settings configured by the administrator.

But we highly 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:

Enable clickjack protection for Setup pages
Enable clickjack protection for non-Setup Salesforce pages
Enable clickjack protection for customer Visualforce pages with standard headers
Enable clickjack protection for customer Visualforce pages with headers disabled

https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/admin_sessions.htm#SLS_s1

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.

https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/admin_sessions.htm#SLS_s1

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.

https://developer.salesforce.com/docs/atlas.en-us.securityImplGuide.meta/securityImplGuide/admin_sessions.htm#SLS_s1

Link to Acrobat Sign Sandbox environment

The Acrobat Sign for Salesforce package has been updated to include support for the Acrobat Sign Sandbox environment. This enhancement allows administrators to test package configurations and workflows before deploying them in production.

Contact your customer success manager if your organization can't access Acrobat Sign Sandbox.

To link to the Acrobat Sign Sandbox environment:

On the Setup page, go to Custom Settings.
From the list of custom settings, locate Adobe Sign Environment Settings and select Manage for the listing.
On the Manage custom settings page, select Edit.
In the Environment Name field, enter 'Sandbox' and select Save.

Admins can now connect to the Sandbox environment. Once done, the Acrobat Sign Admin tab, Agreements, and Agreements Template page displays a Sandbox banner, as shown in the image. The Acrobat Sign Sandbox environment also supports Document Builder.

Acrobat Sign Sandbox environment displays a banner.

Add 'Agreements' Object to Page Layouts

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.

Enable Delegator Roles for Recipients

Not:

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):
- Enable Delegate Acceptor Role - Needed when you want to delegate an Acceptor role.
- Enable Delegate Certified Recipient Role - Needed when you plan to delegate a certified recipient.
- Enable Delegate Form Filler Role - Used when you have to delegate a Form Filler role.
- Enable Recipient Delegate Approver Role – Needed when you plan to delegate to Approvers.
- Enable Recipient Delegate Signer Role – Needed when you are going to delegate to Signers.
Select Save.

Add 'Agreements' to other Salesforce Objects

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.

Enable 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 Acrobat Sign provides the following second-factor identity verification methods (US-based customers have five options when KBA is included):

Password (enabled by default) —Recipients enter a password to view and sign the agreement. Password must be separately communicated to the recipients. Enabled by Default
Phone Authentication—Recipients are sent an automated text (SMS) message or phone call with the required code. It has a per-transaction cost involved. The setting is disabled by default.
Government ID Authentication - Recipients submit an image of a passport or government-issued ID/Driver's License. It has a per-transaction cost involved. The setting is disabled by default and must be enabled by your success manager in the Acrobat Sign system.
Knowledge-Based Authentication—Recipients answer questions taken from publically accessible databases to verify their identity. It has a per-transaction cost involved. The setting is applicable only for US-based users and is disabled by default.

You can enforce the same authentication method for all signers or set a per-recipient verification.

You can also specify different authentication methods for internal recipients (whose email address is included in your Acrobat Sign account) and for external recipients (whose email address is not included in your Acrobat Sign account).

Note: Since Phone, KBA, and Government ID authentications involve a per-transaction cost, they should be enabled only if the contract permits their usage.

Log in to Adobe Acrobat Sign with your Account Administrator userID.
Navigate to Account Settings > Send Settings > Signer Identification Options.
Check the options you want to enable.
Select Save.

Customers who enable second-factor verification may prefer to activate distinct signer identity methods to avoid excessive challenges for their internal signers.

The configurable settings for these methods can be found in the same location.

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.

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

To mandate the recipient name for KBA authentication for all agreements, you can enable the 'KBA Recipient Name Required' custom setting, as shown below.

Once you enable this setting and select KBA as the signer verification method, the "Recipient name required" checkbox is automatically checked and disabled in the "Identity Verification" dialog.
Once you've made the changes, select Save

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:
- Enable Separate Signer Identity Methods— Select the checkbox if you want to enable different identity verification methods for recipients within your organization and for recipients outside your organization.
  For example, you can require that a customer be verified with Knowledge Based Identity before signing the document but require that your sales manager provide no second-factor verification.
- Enable Per Signer Identity Verification—Enable this setting to allow each signer to have a different identity verification method, such as password, phone, KBA, or Government ID.
If you enable both Separate and Per Signer methods, the Per Signer Identify Verification setting is observed.
Select Save.

Grant access to additional profiles

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.

Update email address or password

Change Admin account password

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.

Navigate to the Adobe Acrobat Sign Admin page and select Enable Automatic Status Updates.
Select Enable.
When prompted, allow access to Adobe Acrobat Sign.

Update user email addresses in Adobe Acrobat Sign

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. See how to change email address in Acrobat Sign.

Acrobat Sign account administrators can also change the email addresses of users using the bulk update feature. See how to make bulk updates in Acrobat Sign.

Enable/Disable analytics collection (For commercial cloud only)

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:

The analytics setting is enabled by default for most customers.
The analytics setting is disabled by default for customers in Canada and the European Union.
You can disable/enable the analytics setting by selecting Analytics Settings on the Adobe Acrobat Sign Admin tab.
Only Commercial Cloud users can disable or enable the analytics setting. The functionality is not available for Government Cloud.