Configure Global Settings
⚙️ Phase 2: Configuration
Step 1: Create Remote Site Settings
S-Sign uses SendGrid to ensure verification emails bypass Salesforce email limitations.
Navigate to Setup > Remote Site Settings > New Remote Site.
Remote Site Name:
SSign_Email_Verification_SiteRemote Site URL:
https://api.sendgrid.comActive: Ensure this box is checked.
Step 2: Create a Salesforce Site
This allows external signers to access and sign documents within your Salesforce environment.
Navigate to Setup > Sites.
Register a Domain: If you haven't already, register a Force.com domain.
Create New Site: Click New and fill in the following:
Site Label:
S-Sign SiteSite Name:
S_Sign_SiteActive: Check this box.
Active Site Homepage: Set to
Under Construction.CRITICAL: Uncheck "Lightning Features for Guest Users" for security compliance.
Assign Visualforce Pages: On the Site Detail page, scroll to Site Visualforce Pages, click Edit, and add:
SDOC.SDTemplateHTMLSSign.SSMultiSignSSign.SSCreateSigSSign.SSTemplatePDFSSign.SSVerifySSign.SSViewEnvIncl
Security Check: Navigate to Setup > Session Settings and ensure "Use Lightning Web Security for Lightning web components and Aura components" is Checked.
Step 3: Create a Lookup Field
You must link your specific Salesforce object to the S-Sign Envelope object.
Note: Skip this step if using Standard objects like Opportunity, Contact, Quote and Account; the lookup field is pre-configured for these out-of-the box.
Navigate to Object Manager > S-Sign Envelope (Object)
Go to Fields & Relationships > New
Data Type: Select
Lookup RelationshipRelated To: Select your desired object (e.g., a Custom Object).
Naming Convention (Custom Objects): * Field Label: Name of the object.
Field Name: Object API name ending in
_c(not__c). Example:CustomObject_c.
Step 4: Provide Site Info
Navigate to S-Docs Setup > Go To S-Sign Setup Page.
Site URL: Copy the URL from your Salesforce Site (from Step 2).
Use the URL ending in
secure.force.comif available.Ensure it begins with
https://.
Click Set Site Info & Assign Permissions.
Step 5: License Management
On the S-Sign Setup page, click Go To S-Sign License Page.
Enter Key: Input your license key provided by S-Docs.
Assign Users: Select users from the list and click Add Selected Users.
🛡️ Phase 3: Production-Specific Steps
Step 5B: Assign Licenses to Site Guest User
Navigate to Setup > Sites > [Your S-Sign Site].
Click Public Access Settings > View Users.
Click the Site Guest User record.
Scroll to Managed Packages and click Assign Licenses.
Add both SDocs and SSign.
Note: This step is only required in Production environments.
Step 5C: Establish Org-Wide Email Address
To ensure confirmation and subsequent emails are sent correctly, you’ll need to have an Organization-Wide Email Address configured.
If you already have a valid Organization-Wide Email Address set up, and it matches your Site Guest User email, you can skip this step.
If not, please follow the steps below:
Go to Setup → Organization-Wide Addresses → Add
Add an email address that matches the Site Guest User email
Select “Allow All Profiles to Use this From Address” and complete the verification
Update the Site Guest User record so its email matches this address
Note: This setup is required for sending confirmation and subsequent emails successfully. If the Site Guest User is not configured with a valid Org-wide email address you may notice emails after the first initial request not being sent out.
Optional: Set Organization-Wide Address for all notification emails.
Salesforce now requires email domain verification for outgoing emails, which may not be possible for your External Users (Experience Cloud Site Users) using, for example, a gmail.com email. Configure this option to have all notifications (confirmations, next signer requests, decline notifications) sent from an Org-Wide Address.
Navigate to S-Docs Setup > Go To S-Sign Setup Page.
Scroll to S-Sign Custom Settings and locate the setting From address for notification emails
Select your preferred Org-wide address
Click Save Settings
💡 Pro Tips
Keep Tabs Minimum: Avoid having multiple Setup tabs open to prevent settings from being overwritten.
Bulk Licensing: Use the global function
SSIGN.SSLicensesController.addSSignUserLicenses(userIds)in Apex to assign licenses to large groups of users simultaneously.
Last updated
Was this helpful?

