# Security and Permissions

To grant your team access to S-Docs, you need to configure security settings. Depending on your Salesforce environment, this involves up to two main steps: assigning package licenses and applying the correct permission sets.

> Best Practice Warning: Before configuring user permissions, we recommend reviewing standard Salesforce user management best practices. Always adhere to the principle of "Least Privilege"—starting users with a minimum access profile and layering on permission sets only as needed based on their job functions.

### Part 1: Licenses (Production vs. Sandbox)

Before you begin assigning licenses, you need to determine if your current environment actually requires them.

If you are installing in a Sandbox environment: You do not need to assign licenses. S-Docs provides site-wide licensing automatically in sandboxes. You can skip this entire section and move directly to Part 2: Permission Sets.

If you are installing in a Production environment: You must have a license, but the type of license you purchased dictates your next steps:

* Site License: If your organization purchased a Site License, S-Docs is automatically licensed for all users in your org. You do not need to assign seats manually. Skip to Part 2: Permission Sets.
* Seated License: If your organization purchased a specific number of seats, you must manually assign those licenses to individual users. Follow the steps below.

### How to Assign Individual Licenses (Seated Production Orgs Only)

1. Navigate to the Setup menu by clicking the gear icon in the upper right corner.
2. Type Installed Packages into the Quick Find bar and select it from the drop-down menu.
3. Find the S-Docs package in your list of installed packages and click Manage Licenses.
4. On the Package Manager page, click the Add Users button.
5. Use the checkboxes to select yourself and any other users who need access to S-Docs.
6. Click Add at the bottom of the screen.

Your selected users will now appear in the Licensed Users list. You do not have to assign all of your available licenses at once; you can return to this page to add or remove users at any time.

### Part 2: Permission Sets

Regardless of whether you are in a Sandbox or Production environment, all users must be assigned permission sets to use S-Docs.

S-Docs provides several out-of-the-box permission sets. For standard internal setup, you will primarily use the following two:

* SDocs Administrator: Grants full access to S-Docs, including the template editor and S-Docs Setup tab. Assign this to users who will be building templates and managing the app's configuration.
* SDocs User: Designed for standard internal users. It grants them the access required to generate documents and insert S-Docs Jobs but restricts them from altering templates or backend configurations.

### Additional Permission Sets

Depending on your organization's specific workflow and additional add-ons, you may also utilize the following permission sets:

* SDocs LWC Community User: Ensures that Experience Cloud users can interact with S-Docs Lightning Web Components.
* S-Doc eSignature Requester: Allows users to send e-signature requests (requires S-Sign).
* S-Doc eSignature Signer: Assigned to the site guest user profile associated with an Experience Cloud site created for the e-signature interface.
* SDocs Jobs (Guest Users) (legacy): Grants a website guest user the ability to insert SDoc Jobs.
* **Note**: The "S-Doc Site Guest User" permission set is deprecated.


---

# 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/getting-started/security-and-permissions.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.