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.
Config Step 1: Enter S-Sign License Key and Assign Licenses to Users
Given that you've been provided with an S-Sign license key, you will now need to enter this license key in your org.
To do this, navigate to the S-Sign Licences page via one of the following links:
If you are redirected to the S-Sign Configuration page, navigate to the S-Sign Licences page by clicking the link at the top.
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 will be able to assign licenses to individual users after entering your license key. To do this, simply scroll down on the S-Sign License Management page to the "All Users" section, and select those users whom you would like to assign licenses to.
Config Step 2: 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. 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 Setup in the upper right hand corner, type Security Controls in the Quick Find search bar, and click Remote Site Settings from the options that drop down.
Then, create a new Remote Site Setting with the following fields filled in:
Remote Site Name: SSign_Email_Verification_Site
Config Step 3: 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 Setup, then type Sites into the Quick Find search bar and click Sites from the options that drop down (it should be under "Develop").
Register a Force.com Domain if you don't have one already.
Then, click the New button on the "Sites" list to create a new Site.
- For the Site Label, use S-Sign Site.
- Require Secure Connection (HTTPS) and Upgrade all requests to HTTPS are unchecked in our examples below, but this is not necessary; make sure both boxes are checked if your signers will be providing sensitive information.
- Check Active to make the site active.
- Choose whatever you'd like for the rest of the required fields.
- Click Save.
Then, scroll down to the "Site Visualforce Pages" list and click Edit.
Add the pages SSign.SSCreateSig, SSign.SSTemplatePDF, and SSign.SSViewEnvIncl. Then, click Save.
Config Step 4: Provide Site Info and Assign Site Guest User Permissions
The next step is providing S-Sign the Site Label and Site URL of your site, in addition to adding the S-Sign Site Guest User permission set to your site's guest user.
To do this, navigate to the S-Sign Configuration page via one of the following links:
Then, click the Set Site Info & Assign Permissions button. This will give site guest users on this site read-write access to all of the fields on the S-Sign Envelope and S-Sign Envelope Document objects.
Config Step 5: 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 before you can add the S-Sign's Envelope Related List to your page (you can skip this step if your object is Opportunity, as a lookup field for this object comes built into the package). From the Setup menu, type "Objects" into the Quick Find / Search bar, then click Objects.
Select the custom object labeled S-Sign Envelope (not S-Sign Envelope Documents and not the Edit link).
Scroll down to the Custom 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 name.
- For custom objects, the field name will be the same as the object API. So, if the API name is CustomObj__c, name the field CustomObj_c (one underscore instead of two). Default values should be kept for the "Lookup Filer" section. NOTE: If you have a namespace in your object, say, where the API name were NSP__ CustomObj __c, you would replace the two underscores after the namespace with _u_, so the resulting API name would be NSP_u_CustomObj _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 Visible for all users for field-level security. 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.