Self Sign is an Acrobat Sign for Salesforce component that allows community portal users to sign self-service agreements. You can add Self Sign to any Salesforce Experience Cloud portal, such as customer, partner, employee, and more to help users initiate and sign their agreements right from the portal.
Adobe Acrobat Sign for Salesforce: Self Signing User Guide provides instructions on how to configure Acrobat Sign for Salesforce to generate self-signing agreement templates. To enable community portal users to receive and sign agreements on the Community Portal, you must complete the following steps:
If you're using Acrobat Sign for Salesforce V22 or older, you must enable Chatter in your SFDC organization. To do so:
To enable Digital Experiences:
You must configure two CSP (Content Security Policy) Trusted Sites to allow the base URLs for your Adobe Acrobat Sign account. To do so:
Get your Acrobat Sign account shard value as follows:
See how to identify the Adobe Acrobat Sign account environment.
In the new Site Definition page that opens, fill in the required fields as follows:
In the new Site Definition page that opens, fill in the required fields as follows:
You must enable the community users with the Adobe Acrobat Sign Community User permission set to allow them to use the portal. To do so:
Note: You can build the Community Portal without enabling the Adobe Acrobat Sign Community User permission set.
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:
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:
To create a Contact:
In the New Contact dialog that appears:
On the dialog that appears:
A delightful graphics show runs while the Community is created. Once done, the Community page is displayed, where the name of the Community is displayed at the top of the window (highlighted in yellow) and the site-specific string in the URL can be seen in the address bar.
From the left panel, select Components icon and then:
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.
You can control the Portal settings via the Management panel in the upper-right of the window. The settings are applied to all the agreements exposed within the component.
Note: None of the settings are required, and should only be used when you intend for the setting to be applied globally.
The management panel has following controls:
Refer to The Community Users View to see examples of the above settings.
You can enable the "Allow Sending on Behalf of Others" setting for the users who don't have Adobe Acrobat Sign licensing. This setting allows a community user to generate an agreement using the licensing of another user.
To do this setup, you must complete the following confiuguraiton steps:
Each Agreement Template can have one (and only one) User that the agreements are sent on behalf of. The chosen user must be able to send agreements through Adobe Acrobat Sign, but no other restrictions are in place.
You must configure the Agreement Template with the Salesforce ID of a community user with an Adobe Acrobat Sign license. To do so:
Select the Full Name link of the user.
It opens the Setup Users page, where the UserID is found in the URL of the page (highlighted in yellow).
The above URL reads (with the ID in bold): https://adobe-1df-dev-ed.lightning.force.com/lightning/setup/ManageUsers/page?address=%2F0055j000006w2LP%3Fnoredirect%3D1%26isUserEntityOverride%3D1
You must set the community user's Email setting to make the profile public. To do so:
You can use any one of the below two methods to deliver Agreements to Users in the community portal:
An Account level Template must meet the following requirements:
With the Users and Portal correctly configured, Agreements sent to the Contact populate on the Portal for Users to access and sign at their own discretion.
Agreements waiting for the user to sign are listed at the top. The button to the right of the agreement name indicates if a Signature or Approval is required.
Whenever a user successfully signs or approves an agreement, a success message is displayed at the top of the component panel
Agreements previously signed by the user, but waiting on other recipients to complete their actions are listed next.
At the bottom of the component panel are the completed agreements, with the email address of the signer/approver and the execution date listed.
An Agreement Template can be inserted into the community portal through the component management panel for the community.
When added, the template is viewed in the Waiting for You section, and looks just like a directly sent agreement to the user.
The difference is that the Send/Approve button triggers the template to generate a new agreement at the time it is clicked, and then hosts the agreement within the portal. So the Agreement list isn't populated with these potential agreements until the user initiates the signing process.
Only one template can be used at any given time, and that template is controlled by the other settings on the management panel (described below).
The Agreement Scope limits who can trigger the template in terms of volume:
If a Signing Deadline is entered into the component management panel, agreements must be signed by that date. The deadline is clearly indicated under the agreement name.
Once the defined date has passed, the Sign button is removed, and the deadline text appears in a red font.
The Renewal Days value is not explicitly visible from the Customer side, but causes the template link to become available again once the number of days has passed.
For example, if there is a value of 360, the agreement template link will appear again 360 days after the last time the template was signed.
The header title is an open text field that can be changed to any value.
The header logo is an on/off option that either shows the Adobe Acrobat Sign logo or suppresses it.
Влезте във вашия акаунт
