Adobe Sign for Salesforce: Simple Sign

Simple Sign is an easy out of the box component to allow community portal users to sign self service agreements. Add this component to any Salesforce Experience Cloud portal (customer, partner, employee, etc.), or embed the component into other Lightning components.


To gain access to the Simple Sign functionality, you must have version 21.0 or later of the Adobe Sign for Salesforce package installed.

New installations should be mindful to Generate Sample Agreement Templates when linking Salesforce to Adobe Sign


If the templates were not generated during install, or if you have upgraded from a previous version of the package to v19, you can generate the templates on the Adobe Sign Admin tab.


Verify that the Agreement Templates tab has the Test Community Agreement template:


If you haven't already, Enable Lightning

Lightning must be enabled within your Salesforce organization for the portal to work.

To enable Lightning interface:

  • From the top menu, select Switch to Lightning, Or
  • Select your name and from the drop-down menu, select Switch to Lightning Experience.
Switch to Lightning

Enable Chatter

Chatter must be enabled in your SFDC organization. To do so:

  1. Navigate to: Setup > Platform Tools > Feature Settings > Chatter > Chatter Settings.
  2. Select Edit.
  3. Select Enable check box.
  4. Select Save.

Enable Digital Experiences

To enable Digital Experiences:

  1. Navigate to Setup >  Platform Tools > Feature Settings > Digital Experiences > Settings.
  2. Select Enable Digital Experiences checkbox.
  3. Provide a domain name for your experiences.
    If your account already has an established domain, you can use the same value for experiences.
  4. Select Save.
  5. On the dialog with a warning that your Domain cannot be changed once established, select Ok.
Enable Digital Experiences

Activate two CSP Trusted Sites

You must configure two CSP (Content Security Policy) Trusted Sites to allow the base URLs for your Adobe Acrobat Sign account. To do so:

  1. Get your Acrobat Sign account shard value as follows:

    1. Log in to your Adobe Acrobat Sign account.
    2. From the URL, copy the parameter just before the (possibly part (the shard value). 
      For example, the URL has a shard value of na1.
    3. Close the tab.

    See how to identify the Adobe Acrobat Sign account environment.


  2. Navigate to Setup > Settings > Security > CSP Trusted Sites and then select New Trusted Site.


  3. In the new Site Definition page that opens, fill in the required fields as follows:

    1. Trusted Site Name - Provide a name such as AcrobatSign
    2. Trusted Site URL - Enter the site URL https://secure.<shard>
      For example,
      If your account isn't updated to the domain, you may use instead.
    3. Select the  Active checkbox.
    4. Context - Select Experience Builder Sites for Context.
    5. Select CSP Directive Allow site for frame-src checkbox.
    6. Select Save.

  4. Navigate back to Setup > Settings > Security > CSP Trusted Sites and then select New Trusted Site.

  5. In the new Site Definition page that opens, fill in the required fields as follows:

    1. Trusted Site Name - Provide a name such as AcrobatSign2
    2. Trusted Site URL - Enter the site URL
    3. Select the Active checkbox.
    4. Context - Select Experience Builder Sites for Context.
    5. Select CSP Directive Allow site for frame-src checkbox.
    6. Select Save.
    Second CSP trusted site

  6. Verify the two CSP Trusted Sites.

    CSP Trusted sites

Creating the Community Portal User

Clone the Community User Profile

To configure your user profiles to use the Adobe Acrobat Sign self-service portal, you must clone and edit one of the standard profiles. To do so:

  1. Navigate to Setup > Administration > Users > Profiles.

  2. For any of the standard Customer Customer profiles, select Clone.

    There are four Customer Community profiles, and you can use any of them to clone and create a user profile. Note the User License type of the profile that you clone.


  3. Provide an intuitive name for your cloned profile and then select Save.


  4. On the cloned profile page that opens, select Edit.


  5. On the Custom Edit page, scroll down to the Custom Object Permissions and enable all Adobe Acrobat Sign objects. You can select the Modify All check box or select only the required permissions for added security. 


Create an Account, Contact, and User for the community

You must create an Account, a Contact, and a User for the Community. 

An account owner must be associated with a Role to enable portal users. To associate a role with your Salesforce user, go to Setup > Administration > Users > Users. Then, from the list of users, select Edit for a user and then in the page that opens, open the Role drop-down menu > select a role > select Save.

To create an Account:

  1. Launch the Sales app from the App launcher.

  2. Open the Account drop-down menu and select +New Account.


  3. In the New Account page that opens, enter an Account Name value and then select Save.

    The account name should identify the account as an Adobe Acrobat Sign Portal account. The Account name is the only value that you need to provide here.


Configuring the SFDC Community Page

Start a new Community

  • Navigate to: Setup >  Platform Tools > Feature Settings > Digital Experiences > All Sites
  • Click the New button
Digital Expereinces - All sites


  • Select the Customer Service experience
    • The Customer Service experience is required for the Self-Service components


  • When the Customer Service page loads, click Get Started


  • Enter a Name for the community
    • Optionally, you can add site-specific name to the URL, which is useful if you have multiple Communities
  • Click Create when the Name is configured

A delightful graphics show runs while the Community is created. Once done, the Community page is displayed.

►The name of the Community is displayed at the top of the window, highlighted in yellow

►The site-specific string in the URL can be seen in the address bar, highlighted in teal

Configure the Experience workspace to enable Users

  • Navigate to: Setup > Platform Tools > Feature Settings > Digital Experiences > All Sites
  • Click the Workspaces link of your community
Click Workspaces

The My Workspaces page loads:

  • Click the Administration option

The Administration page opens for your community.

With Settings selected on the left rail:

  • Click the Activate button to the right of the Status indicator


Select Members from the left rail

  • Select All from the Search drop-down
  • Select the custom Profile that you created from the Available Profiles list
  • Click the Add button, moving the profile to the Selected Profiles list
  • Click the Save button

Set the Profile Visibility settings for the Email setting of the community user to Public

The email address in the Profile Visibility section of the community must be set to Public:

  • Open the Contact page for the user you are using to send on behalf of
  • Select Log in to Experience as User
Log in to experience as user

The portal interface opens:

  • Click the user name at the top-right of the community page window to open the drop-down window
  • Select My Settings

The My Settings page for the user opens:

  • In the Profile Visibility section, set the Email value to Public
  • Click Save

Add the Adobe Simple Sign component to the Workspace

  • Navigate to: Setup > Platform Tools > Feature Settings > Digital Expereinces > All Sites
  • Click the Workspaces link of your community
  • Click the Builder option in the My Workspaces section of the page
  • Click the Components icon in the top-left of the page, scroll to the bottom of the menu, and click-drag the Adobe Simple Sign option onto the page layout.
    • Drop the component where ever you want the Adobe Sign agreements to be exposed
Drag Simple Sign into the portal tempalte


The page refreshes to show the added component on the page layout, and exposes the management panel for the component in the top right corner.

The management panel in the upper-right of the window has only one configurable option:

Agreement Template - What is the template that governs the agreements listed in the component


Select the template, and then click the Publish button to make the portal available.

  • Every time you make a change to the portal or any settings, you must re-publish the portal

Embed Simple Sign code into your Lightning components

The Simple Sign component can be embedded in another lightning component.

Example code of the component:

<echosign_dev1:SimpleSign templateId="a0L190000019xUrEAI" />


When the component is embedded programmatically in another component, the following additional parameters can be specified:

  • agreementId - The salesforce ID of the agreement which is in-flight or draft 
    • Draft agreements should have send-on-behalf configured
  • templateId - The salesforce ID of the template which governs the agreements generated
  • pollingInterval - Value would be a number in milliseconds
    • This denotes the time which goes by before each attempt to fetch the signing URL
      • Min value is 500
      • Max value is 50000
      • Default value is 1000
  • showSigningModal
    • If set to false, then it just returns the signingURL without loading the e-sign page in an overlay modal
    • If set to true, it returns the signingURL and also loads the e-sign page in the overlay modal
    • Default is true


Parameters follow these rules:

  • Either the agreementID or templateID should be specified
    • If both are specified, then the agreementID will be used
    • If neither are specified an error is returned
  • When using an agreementID, the agreement must be in draft or out for signature status, where there is at least one remaining recipient left to sign
    • If the agreement is in draft state, send it out as is, grab the signing URL and show it
    • If the agreement is in-flight, grab the signing URL and show it
    • If the agreement is completed, show and notify an error
  • If a templateID is used, Auto Send is enabled regardless
    • When an agreementID is used, the Auto Send setting on the template is respected
  • Simple Sign agreement templates must have a master object type of Contact
  • Send on behalf of is strongly recommended because the bulk of community users usually are typically not licensed to send


The component can also publish events to consumers.  Here's an example of the event handler:

<aura:handler name="notifyError" event="echosign_dev1:ErrorEvent" action="{!c.onError}"/>

Available events are:

Agreement Sent

name="notifyAgreementSent" event="echosign_dev1:AgreementSentEvent" action="{!c.onAgreementSent}"

Agreement loaded from template

name="notifyAgreementLoaded" event="echosign_dev1:AgreementLoadedEvent" action="{!c.onAgreementLoaded}"

Signing page opened

name="notifySigningLoaded" event="echosign_dev1:SigningLoadedEvent" action="{!c.onSigningLoaded}"


name="notifyRecipientCompleted" event="echosign_dev1:RecipientCompletedEvent" action="{!c.onRecipientCompleted}"

No Signed

name="notifyRecipientNotCompleted" event="echosign_dev1:RecipientNotCompletedEvent" action="{!c.onRecipientNotCompleted}"

Error During any action

name="notifyError" event="echosign_dev1:ErrorEvent" action="{!c.onError}"

Agreement Template Requirements for Simple Sign

Templates in the Simple Sign environment must be configured to assign the recipient based on a lookup to a Master Object, and that object must be a Contact.

On the Template Details tab:

  • Click the drop down under Salesforce Object
  • Select Choose from other objects
    • a new drop-down field is exposed
  • Select Contact from the second drop-down field

  • Click the Recipient tab
  • Delete the one recipient already on the template
  • Click the Add recipient from object or run-time variable link
    • The Add recipient overlay appears
  • In the Choose object or runtime variable field, select Look Up Based on Master Object Field
    • The first recipient must be set to the Master Object (Contact) and the Source field from master object should be contact ID.
  • Click Save

A file of some type must be attached to the template for Simple Sign to work.  There is no chance for "the sender to attach the document" like an active send process.

  • Click on the Attachment tab
  • Upload a document from your local system
    • Or select the environment where your document resides (in the Select to add documents section).
      • Click the lookup field to see all of the available documents in that section
      • Select one at a time to attach them to the template

Click Save when all of your documents are attached


Any file you upload is stored in Salesforce (in the Salesforce CRM & Files option)

If you have portal users that aren't licensed in Adobe Sign, you will need to circumvent the user licensing by exploiting the "Send on Behalf of" feature built in to the package.  This allows a community user to generate an agreement using the licensing of another user.

This setup requires three configurations:

  • Enable the setting Allow Sending on Behalf of Others in the custom settings
  • Configure a licensed user to Allow Sending on Behalf of  their user
  • Configure the Agreement Template with the Salesforce ID of the above user 

Enable the setting

  1. Navigate to Setup > Platform Tools > Custom Code > Custom Settings
    • This loads the Custom Settings page
  2. Click the label Adobe Sign Settings
    • The Adobe Sign Settings page will load

    3. Click the Manage button

    4. Click New (or Edit, if you have configured settings before)

  • The Adobe Sign Settings page will load.

5. Search for Allow Sending on Behalf of Others

  • Enable the setting by checking the check box
  • Click Save

Configure the User to have agreements sent on their behalf

To enable a User to support the Send on Behalf of functionality, two fields have to be added to the User record layout:

  • Navigate to Setup > Platform Tools > Objects and Fields > Object Manager
  • Select User from the Object Manager
  • Select User Page Layouts from the left rail of the User object page
  • Click the User Layout link
  • With Fields selectedclick and drag the below two fields to the “Additional Information (Header visible on edit only)” section of the layout
    • Adobe Sign Allow Sending As Other Users
    • Adobe Sign Email Verified 
  • Click Save

With the fields in place, enable the specific User:

  • Navigate to: Setup > Administration > Users > Users
  • Click the Edit Action for the "community contact" user
  • In the User Edit page, Additional Information section
    • Check the Adobe Sign Allow Sending as Other Users option
    • Check the Adobe Sign Email Verified option

With the User Edit page still open, copy the UserID from the URL in your browser bar.

The UserID is found in the URL of the page (highlighted in yellow below):

The above URL reads (with the ID in bold):

Be careful not to include the %2F at the beginning, and the %3 at the end

  • Copy and save the UserID for the next step


Click the Save button when you are done to save the configuration.

Update the template with the userID

  • Navigate: App Launcher > Adobe Sign > Agreement Templates
  • Click the Agreement Template Name that you want to edit
Navigate to the Agreement Template

Click the Recipients tab and edit the Send On Behalf Of field

  • Paste the Salesforce UserID into the field (there is a place holder ID that you can delete without worry)
  • Click Save
Edit Send on Behalfof

Limitations of the component

There are some limitations for the Simple Sign component that you need to be aware of:


1. The Template may not be configured with Only Sender Signs enabled

○ In this case, community user will see the error that the there is no signing URL for the current user

2. The Template may not have the Enable Preview and Position Fields option checked

○ In this case, the agreement remains in pre-send state, and no signing URL will be loaded

3. The Template may not have the Enable hosted signature option checked

4. Simple Sign does not support delegation

○ In this case, the other recipient will not be able to access the signing URL

5. Simple Sign does not support Replace Signer (which is a form of delegation)

○ In this case, the new signer will not be able to access the signing URL

6. To access the Notes and Attachments of any Salesforce object, admins must enable Lets customer users access notes and attachments in Communities Settings

Adobe logo

Sign in to your account