> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/quick-start/s-sign-setup/first-step-installing-s-sign.md).

# First Step: Installing S-Sign

This page will walk you through the installation process for the S-Sign Package.

## S-Sign Quick Install Guide: Salesforce Lightning

This guide provides a step-by-step walkthrough for installing and configuring S-Sign, a 100% native e-signature solution for Salesforce.

***

### Phase 1: Installation

Unlike S-Docs, S-Sign is not available on the AppExchange. To install S-Sign:

1. Request Link: Contact [**S-Docs Sales**](https://www.sdocs.com/about?qgad=703925338752\&qgterm=s-docs\&gad_source=1\&gad_campaignid=21410070609\&gbraid=0AAAAADBYf9M1VfW8vCUAWRql9uBDlauQm\&gclid=Cj0KCQjwkYLPBhC3ARIsAIyHi3RenceVMoyo3g4ObZ837vOb6Fs4hHTibU0llZAvHIQDl9J3B40IJVcaAsW7EALw_wcB#contact-us\&utm_campaign=AVA-Brand\&utm_source=adwords\&utm_medium=ppc\&utm_term=s-docs\&hsa_kw=s-docs\&hsa_net=adwords\&hsa_grp=165564168842\&hsa_cam=21410070609\&hsa_acc=6588399060\&hsa_tgt=kwd-940841427764\&hsa_ver=3\&hsa_ad=703925338752\&hsa_mt=e\&hsa_src=g) to obtain the latest installation link.
2. Installation Type: Select **Install for Admins Only**.
3. Environment: It is highly recommended to setup and test in a Sandbox before installing in Production.
4. Verification: Navigate to **Setup > Installed Packages** to ensure S-Sign and S-Docs version numbers are up to date.
5. Permissions: Assign either the **S-Sign User** or **S-Sign Administrator** permission set to yourself and relevant users.

{% hint style="info" %}
**Major Package Versions for S-Docs and S-Sign must align to ensure proper functionality.** Please contact your Customer Success Manager or S-Docs Support to request patch links corresponding to your organization's current version.
{% endhint %}

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.sdocs.com/quick-start/s-sign-setup/first-step-installing-s-sign.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
