The 'Self Sign' feature in Adobe Acrobat Sign for Salesforce enables users on community portal 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.
The 'Self Sign' feature is available for access from the following portals of a few different editions of the Salesforce community cloud:
To enable users to receive and sign agreements on the Community Portal, you must complete the following steps:
Note: Ideally, you must select Generate sample agreement templates option while linking your Acrobat Sign account to Salesforce.
If you're on Commercial Cloud using Acrobat Sign for Salesforce V22 or older, you must enable Chatter in your SFDC organization.
Acrobat Sign Government Cloud users do not need to enable Chatter.
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:
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.
On the 'Select an expiration...' page that opens, you may select an expiration date for the assigned users if required. Once done, select Assign.
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:
Navigate to Setup > Administration > Users > Profiles.
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.
Provide an intuitive name for your cloned profile and then select Save.
On the cloned profile page that opens, select Edit.
On the Custom Edit page, scroll down to the Custom Object Permissions and enable all Adobe Acrobat Sign objects. You can select the View All check box or select only the required permissions for added security.
Additional access to custom objects' records can be granted based on user licenses. For example, users with Customer Community licenses can be granted access through user profiles, while users with Customer Community Plus licenses can be provided access through sharing rules.
You must create an Account and a Contact 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 list > select a role > select Save.
To enable Digital Experiences:
To configure SFDC community portal page, you must implement the following steps:
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 configuration steps:
Our package's custom objects are initially set as "private" for external users by default. Community user permission sets provide access to custom objects and their fields, but not to records created by other users (both internal and external).
Within community portals, administrators have the following two options for setting up eSign flows:
In both cases, admins often use agreement templates to enable community users to initiate or participate in eSign flows. For this to work, community users need read-only access to agreement templates and related resources, such as merge and data mapping objects, which are typically created by internal users.
The type of community user license determines how access can be granted:
For community users to create agreements using agreement templates, they must be given "ViewAll" access to the Agreement templates and the associated Objects.
Data Mapping (echosign_dev1__SIGN_Data_Mapping__c)
If Acrobat Sign Document Builder templates are used with Agreement template as a file attachment, the objects below need to be granted access to community users:
Document Builder Template (adobesign__Document_Template__c)
Object Field Mapping (adobesign__Object_Field_Mapping__c)
To use community portal for sending and signing agreements, refer to the following topics:
To be able to send agreements or sign agreements via using the community potal, you must ensure that:
An account level template must meet the following requirements:
You can use any one of the below two methods to deliver Agreements to Users in the community portal:
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’s 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).
To send an agreement directly to a user, the recipient must be a contact. Using an email value will not populate the agreement in the portal.
Once users and the portal are properly set up, agreements sent to the contact appear on the portal. Users can access and sign these agreements at their convenience. Here's what users see on the community portal:
