To learn how to install and configure S-Sign for Salesforce Classic, you can watch the following tutorial video, which will walk you through the process. You can also refer to the written instructions below the video, which provide a detailed, step-by-step guide to installing S-Sign. Timestamps from the video are provided in the table of contents. To view the same guide for Salesforce Lightning Experience, click here.
Unlike S-Docs, S-Sign is not available on the AppExchange. Contact S-Docs Sales to obtain an installation link for the latest version of S-Sign. Make sure to select "Install for All Users." We recommend testing in a sandbox environment before installing in your production org.
You may need to update S-Docs if you're running an older version.
Head over to Installed Packages by typing "installed" into the Quick Find / Search bar in Setup to ensure that S-Sign has downloaded correctly and that your version numbers are up to date.
If you are using S-Sign version 2.110 or higher, you need to create a Sharing Rule on the S-Sign Envelope and SDoc Template objects. First, navigate to Setup > Sharing Settings, and choose your object. You will need to repeat this step for both objects.
Click New to create a new sharing rule.
Enter the following settings:
Rule Type: Guest user access, based on criteria
Field: Core Version
Operator: not equal to
Share With: S-Sign Site Guest User
Access Level: Read Only
Once your Sharing Rules are created, you're ready to start configuring S-Sign.
S-Sign uses SendGrid, an email service, to send out verification emails to signers in order to confirm the signer's identity. This bypasses any email limitations you may run into in your Salesforce org, ensuring that your e-signature requests will always send. To allow S-Sign to tell SendGrid when to send out a verification email, you must create a Remote Site Setting within Salesforce that whitelists SendGrid's API domain (i.e. allows S-Sign to communicate with SendGrid).
To do this, navigate to the Setup menu, type "Remote" in the Quick Find / Search bar, and click Remote Site Settings from the options that drop down. Then, click New Remote Site.
Fill in the following fields for your new remote site:
Remote Site Name: SSign_Email_Verification_Site
Ensure that the Active checkbox is checked. You can leave everything else as it is.
Note: In some cases, you may need to add a second remote site for the Salesforce login URL if you don't have one already set up. Click New Remote Site again and enter the following values:
For Production Org:
Remote Site Name: Salesforce_Production
Remote Site URL: https://login.salesforce.com
For Sandbox Org:
Remote Site Name: Salesforce_Sandbox
Remote Site URL: https://test.salesforce.com
Like S-Docs, S-Sign is native to the Salesforce platform. This means that all signers must sign within Salesforce, even if they do not have a Salesforce account. To accomplish this, we'll set up a Site in our org that will display your document(s) and allow users to sign them.
Start by again navigating to the Setup menu, then type Sites into the Quick Find search bar and  click Sites from the options that drop down. Next,  Register a Force.com Domain from this page if you don't have one already. Then,  click the New button on the "Sites" list to create a new Site.
Fill in the following fields for your Site:
- Site Label: S-Sign Site
- Site Name: S_Sign_Site
- Site Contact: This is the user responsible for receiving site-related communications from the site visitors and Salesforce.com. By default, it is set to the user creating the Site.
- Default Web Address: You can append something to the end of your site's domain, but it is not necessary.
- Active: Make sure this is checked so that the site is active.
- Active Site Homepage: You can choose anything you want for this, but we recommend setting it to "Under Construction." This won't be visible to anyone.
- You can choose whatever you'd like for the rest of the fields or leave them at the default settings. We recommend keeping the first six checkboxes at the bottom checked for better security.
- Click Save.
Once you click Save, you should be redirected to the Site Detail Page. The only thing left to do for this step is to add a few Visualforce pages to our site. Scroll down to the "Site Visualforce Pages" list on the Site Detail Page and click Edit.
Add the pages SDOC.SDTemplateHTML, SSSign.SSMultiSign, SSign.SSCreateSig, SSign.SSTemplatePDF, and SSign.SSViewEnvIncl. Then, click Save. You've now completed this step!
You need to create a lookup field for any objects you’ll be using with S-Sign.
In the Setup menu, type "Objects" into the "Quick Find / Search" bar, then click Objects from the options that drop down. Click S-Sign Envelope (NOT the S-Sign Envelope Document and NOT the edit button).
Scroll down to the Custom Fields & Relationships section and click New.
Step 1 of 6: Choose Lookup Relationship for the field type. Click Next.
Step 2 of 6: Select the object for which you are creating the lookup relationship (the object you want to use S-Sign with). Click Next.
Step 3 of 6: This step is where you’ll add the field label and name. Default values can be kept for the rest of the fields.
- For custom objects, the field label will just be the name of your custom object. The field name should be the API name of your custom object with a single underscore and a 'c' at the end, instead of the usual "__c." For example: if your custom object was named CustomObject and the API name was CustomObject__c, then your field label would just be CustomObject, and your field name would be CustomObject_c.
- If your custom object is part of a managed package, it will have a namespace at the beginning. Say the object's API name is NSP__CustomObject__c. For the field name, you would replace the two underscores after the namespace with _u_ and remove one of the underscores from __c, so the resulting API name would be NSP_u_CustomObject_c.
- For standard objects, just enter the name of your standard object (ex. the Quote object would have the field name and field label 'Quote').
Step 4 of 6: Select your own field-level security settings. Click Next.
Step 5 of 6: Keep the default values.
Step 6 of 6: Add the S-Sign Envelopes related list to the appropriate page layouts. Click Save, and when you go to your object’s page, you’ll see the S-Sign Envelopes related list.
The next step is providing S-Sign with your Site's Site label and URL, in addition to adding the S-Sign Site Guest User permission set to your site's guest user. Don't worry, it's a lot less complicated than it sounds.
Start by navigating to the S-Sign Configuration page via one of the following links:
- The S-Sign Configuration page contains a field for your S-Sign Site URL. Ensure that the URL shown in this field matches the Site URL you created in step 2. To do so, navigate to the Site detail page for your S-Sign site (Setup > Sites > S-Sign Site), copy the site domain from the Custom URLs list, and paste it into the S-Sign Site URL field on the S-Sign Configuration page. Make sure to add https:// at the beginning of the domain.
- If your Site detail Custom URLs list includes two S-Sign Site URLs (shown below), use the URL that ends with secure.force.com.
Then, click the Set Site Info & Assign Permissions button. This will give guest users on this site (the people who will be signing documents) read-write access to all of the fields on the S-Sign Envelope and S-Sign Envelope Document objects. It all happens behind the scenes...all you have to do is click the button!
Once you've completed steps 1-4, you are ready to enter you license key and assign licenses to users in your org. Click Click here to be redirected to the S-Sign License Page at the top of the S-Sign Configuration page.
From there, you can enter your license key.
If you are on the trial version, all you need to do is enter the license key, and then all users in your org will be able to use S-Sign. If you are on the paid version, you can now scroll down to assign licenses to individual users by selecting their names and clicking Add Selected Users.
That's it! S-Sign is configured for your org. You are now ready to create S-Sign-enabled S-Docs templates to send for E-Signature.
Orgs that need to add or remove a large number of S-Sign licenses can use the addSSignUserLicenses and removeSSignUserLicenses functions. These functions are global and can be called from anywhere, allowing for flexibility if you need to make a bulk update to your S-Sign license assignments. These functions take a List<String> object. Although there are many ways to use them, the following example demonstrates how to add an S-Sign license to all active users: