Installing S-Sign

Unlike S-Docs, S-Sign is not available on the AppExchange. Contact S-Docs Sales here to obtain an installation link for the latest version of S-Sign. 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.

Pro Tip: Try to keep as few tabs open as possible during this configuration process. This will help prevent settings confirmed in one tab from being negated by another open tab.

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.

Configuring S-Sign

There are five steps to configuring S-Sign. You can click on each one below to scroll down to its explanation, or simply follow along with this guide.

  1. Create a Remote Site Setting
  2. Set up a Site for S-Sign
  3. Create a Lookup Field to your Object on the S-Sign Envelope Object
  4. Provide Site Info and Assign Site Guest User Permissions
  5. Enter License Key and Assign Licenses

Config Step 1: Create a Remote Site Setting

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, simply click the Setup cog in the upper right hand corner, 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

URL: https://api.sendgrid.com

Ensure that the Active checkbox is checked. You can leave everything else as it is.

Config Step 2: Create a Site to Capture External Users' Signatures

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 users can sign documents on. Start by again clicking the Setup cog, then type Sites into the Quick Find search bar and [1] click Sites from the options that drop down. [2] Register a Force.com Domain from this page if you don't have one already. Then, [3] 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.
  • Default Web Address: You can append something to the end of your 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 SSSign.SSMultiSign, SSign.SSCreateSig, SSign.SSTemplatePDF, and SSign.SSViewEnvIncl. Then, click Save. You've now completed this step!

Config Step 3: Create a Lookup Field to your Object on the S-Sign Envelope Object

You need to create a lookup field for any objects you’ll be using with S-Sign (you can skip this step if your object is Opportunity, as a lookup field for this object comes built into the package). Navigate to the Object Manager in the Setup menu and click the S-Sign Envelope object (not S-Sign Envelope Documents).

Click the Fields & Relationships tab 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 name of your custom object with a single underscore and a c at the end. For example: if your custom object was named CustomObject, 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. You would replace the two underscores after the namespace with _u_, so the resulting API name would be NSP_u_CustomObject_c.

  • For standard objects, just enter the name of your standard object (ex. the Contact object would have the field name 'Contact').

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.

Config Step 4: Provide Site Info and Assign Site Guest User Permissions

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:

[Production] https://login.salesforce.com/apex/SSIGN__SSConfig
[Sandbox] https://test.salesforce.com/apex/SSIGN__SSConfig

First, ensure that the S-Sign Site URL shown on this page matches the Site URL you just created. If they do not match, paste the URL from the Sites page into the box.

.

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!

Config Step 5: Enter your License Key and Assign Licenses to Users

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.