# Manage User Access

***

### S-Sign License Key Considerations (Fresh Installation/Renewal)

#### Phase 0: License Key Update Pre-Work

#### Important Pre-Check

If you plan to add or change licensed users during this renewal, you must first assign them via the Salesforce Installed Packages interface before updating the key:

1. Navigate to **Setup > Installed Packages**.
2. Find the **S-Sign package** and click **Manage Licenses**.
3. Click **Add Users** and **select all users who require a license**.

***

#### Phase 1: Updating the S-Sign License Key

1. Open the **App Launcher** in the upper left corner and click **View All**.
2. Locate and click **S-Docs Setup.**
3. Navigate to **S-Sign License Key Page.**
4. **Enter your new license key into the License Key field.**
5. Click **Update License Key.**
6. Confirm that you receive a **Success** message.

***

### 🔑 Internal User Permissions

These sets are intended for your standard Salesforce users and system administrators.

#### SSign Administrator

* Description: The highest level of access for S-Sign management.
* Key Capabilities: \* Grants full access to the S-Sign Setup page.
  * Enables the S-Docs Template Editor for creating and modifying S-Sign enabled templates.
  * Allows configuration of global S-Sign settings and custom integrations.

#### SSign User

* Description: The standard permission set for internal employees who need to facilitate the signing process.
* Key Capabilities: \* Provides the ability to generate and send S-Sign requests from Salesforce records.
  * Allows users to track the status of envelopes they have initiated.
  * *Note: This set contains certain permissions that are incompatible with restricted Experience Cloud profiles.*

***

### 🌐 Experience Cloud & Guest Permissions

These sets are optimized for external-facing environments and specialized portal users.

#### SSign Experience Cloud User

* Description: Specifically tailored for Experience Cloud (Community) users.
* Key Capabilities: \* Grants portal users the ability to send S-Sign requests.
  * Why it's used: It excludes specific system permissions found in the "SSign User" set that cannot be technically assigned to certain Experience Cloud license types, preventing deployment errors.

#### S-Sign Site Guest User

* Description: A mandatory permission set for the public-facing side of the signing process.
* Key Capabilities: \* Provides the necessary access for the Site Guest User profile to interact with S-Docs and S-Sign.
  * Ensures that external signers (who do not have a Salesforce login) can view the document and submit their signature via the S-Sign Site.
  * *Note: This permission set is intend to be applied to the S-Sign Site Site Guest User*

***

### ⏳ Legacy Permissions

#### S-Sign Site Internal User (Legacy)

* Description: A specialized permission set for specific older configurations.
* Key Capabilities: \* Grants access to S-Docs/S-Sign specifically for users who are authenticated via the SSign Connected App.
  * Generally used in legacy environments or specific architectural setups where the Connected App is the primary driver for S-Sign actions.

***

{% hint style="info" %}
Note: **Permission Sets give functional access** to object, apex classes, visual force pages, and more. **Sharing Settings give record level** access to S-Docs and S-Sign Objects. It is recommended to limit record level access and extend access through **Sharing Rules**.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.sdocs.com/quick-start/s-sign-setup/manage-user-access.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.