> 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/s-sign/advanced-signer-scenarios/s-sign-authentication-and-signer-links.md).

# S-Sign Authentication and Signer Links

This page details the different signing links that are produced via our S-Sign product and how generation methods, licensing, and permissions can affect their output.

In our [February '24](https://www.sdocs.com/resources/release-notes/2024-02) release, we introduced authenticated signing for S-Sign.

This functionality uses S-Sign users' Salesforce authentication to secure signatures.&#x20;

Here's how the process works:

1. When an Envelope is created, S-Sign collects the email address merged in for each signer profile and searches the org's User records for any match.
2. If an email address matches a User, S-Sign then checks to see if the User has any [S-Sign permission sets](https://kb.sdocs.com/knowledge-base/ssign/install-configure-ssign/s-sign-permission-sets/) assigned
3. For Users with S-Sign permission sets assigned, S-Sign then checks the User's License/Profile to determine if they are an Internal or External User.
4. Finally, for Experience Cloud Users, S-Sign queries for the Site to which the User belongs

S-Sign will then generate a Sign Link with a **base domain** appropriate to the signer:

1. Experience Cloud users (Portal, Community) with S-Sign permissions will be directed to the site to which they belong to authenticate before signing
2. Internal org Users with S-Sign permissions will be directed to authenticate via the org's internal domain
3. Signers whose email does not match a User with S-Sign permissions will be directed to the S-Sign Site to sign via the Site Guest User - no login screen here.

To ensure the most accurate testing, be sure to generate requests for emails that represent your signers; if your signers will not be Salesforce or Site users, be sure that your signer profiles merge in emails that do not match the User records in your environment.

### Envelope Creation and Sign-Link Behavior:

In current versions, the internal user that needs to receive the internal URL, will need to have one of the following permission sets assigned:**(SSign User, SSign Admin, SSign Experience Cloud)**

#### **Envelope created as Internal User** <a href="#envelope-created-as-internal-user" id="envelope-created-as-internal-user"></a>

*Email Address linked to signer profile associated to user record. User record **w/o licensing**, **w/o permission set** assigned:*

* **SDLegacy**
* Sign In-Person: External domain
* Email via SDLegacy: External domain
* **LWC**
* Sign In-Person: External domain
* Email via SDLegacy: External domain
* **SDK**
* Signing Link: External Domain

*Email Address linked to signer profile associated to user record. User record **is inactive**:*

* **SDLegacy**
* Sign In-Person: External domain
* Email via SDLegacy: External domain
* **LWC**
* Sign In-Person: External domain
* Email via SDLegacy: External domain
* **SDK**
* Signing Link: External Domain

*Email Address linked to signer profile* *associated to user record. User record **w/o licensing**, **w/ permission set** assigned:*

* **SDLegacy**
* Sign In-Person: Internal domain
* Email via SDLegacy: Internal domain
* **LWC**
* Sign In-Person: Internal domain
* Email via SDLegacy: Internal domain
* **SDK**
* Signing Link: Internal Domain

*Email Address linked to signer profile associated to contact record, **no user record**:*

* **SDLegacy**
* Sign In-Person: External Domain
* Email via SDLegacy: External Domain
* **LWC**
* Sign In-Person: External Domain
* Email via SDLegacy: External Domain
* **SDK**
* Signing Link: External Domain

*No Email Address linked to signer profile:*

* **SDLegacy**
* Sign In-Person: External Domain
* Email via SDLegacy: External Domain
* **LWC/SDK: Will not work. Email Address required.**

#### **Envelope created as Experience Cloud User** <a href="#envelope-created-as-experience-cloud-user" id="envelope-created-as-experience-cloud-user"></a>

*Email Address linked to signer profile associated to user record. User record **w/o licensing**, **w/o permission set** assigned:*

* **SDLegacy**
* Sign In-Person: External domain
* Email via SDLegacy: External domain
* **LWC**
* Sign In-Person: External domain
* Email via SDLegacy: External domain
* **SDK**
* Signing Link: External Domain

*Email Address linked to signer profile associated to user record. User record **is inactive**:*

* **SDLegacy**
* Sign In-Person: External domain
* Email via SDLegacy: External domain
* **LWC**
* Sign In-Person: External domain
* Email via SDLegacy: External domain
* **SDK**
* Signing Link: External Domain

*Email Address linked to signer profile associated to user record. User record **w/o licensing**, **w/ permission set** assigned:*

* **SDLegacy**
* Sign In-Person: Internal domain
* Email via SDLegacy: Internal domain
* **LWC**
* Sign In-Person: Internal domain
* Email via SDLegacy: Internal domain
* **SDK**
* Signing Link: Internal Domain

*Email Address linked to signer profile associated to contact record, no user record:*

* **SDLegacy**
* Sign In-Person: External Domain
* Email via SDLegacy: External Domain
* **LWC**
* Sign In-Person: External Domain
* Email via SDLegacy: External Domain
* **SDK**
* Signing Link: External Domain

*No Email Address linked to signer profile:*

* **SDLegacy**
* Sign In-Person: External Domain
* Email via SDLegacy: External Domain
* **LWC/SDK: Will not work. Email Address required.**

#### Additional considerations:

* **Envelope created as Experience Cloud User**
* *Email Address linked to signer profile associated to user record. User record **is member of multiple exp cloud sites**:*
* **SDLegacy: Not recommended.**
* **LWC**
* Sign In-Person: Internal domain, same site envelope generated from
* Email via SDLegacy: Internal domain, same site envelope generated from
* **SDK**
* Signing Link: Internal domain, same site envelope generated from


---

# 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/s-sign/advanced-signer-scenarios/s-sign-authentication-and-signer-links.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.
