> **Source:** https://knowledge.leegality.com/document-execution/integrations/salesforce/administration > **Site:** Leegality Knowledge Base — https://knowledge.leegality.com > **About:** Leegality is a document execution platform covering eSigning, stamps, NeSL, workflows, and REST API integration. > **Navigation:** Every article on this site has a plain-text version at `.txt` (this format). To get an index of all articles with their `.txt` links, read: https://knowledge.leegality.com/llms.txt > **AI Guide:** For instructions on how to navigate this knowledge base as an AI agent, read: https://knowledge.leegality.com/ai-readable.txt --- # Administration Ongoing admin tasks: managing who can use Leegality in your org, and configuring the webhook that keeps document statuses in sync. ## User management The app's **User Management** tab gives admins a shortcut to the two Leegality permission sets without going through Salesforce Setup. ### Assign admin permissions 1. In the **Leegality for Salesforce** app, open the **User Management** tab. You are redirected to the **Permission Sets** page. 2. Find and click **Leegality Admin User Permission Set**. 3. Click **Manage Assignment**, then **Add Assignment**. 4. Choose the users to assign and click **Save**. ### Assign sender permissions 1. Open the **User Management** tab. You are redirected to the **Permission Sets** page. 2. Find and click **Leegality Sender User Permission Set**. 3. Click **Manage Assignment**, then **Add Assignment**. 4. Choose the users to assign and click **Save**. > **Note** > > Users also need the **Leegality External Credential Access** permission set to call Leegality APIs — see [Installation & Setup](https://knowledge.leegality.com/document-execution/integrations/salesforce/installation-and-setup#24-grant-credential-access-to-users). ## Webhook configuration Leegality pushes document status updates into Salesforce through a webhook endpoint hosted on a Salesforce **public site**. Set it up as follows: 1. From your Salesforce home page, click the **Setup** gear icon (top right). 2. In the Quick Find box, type **Sites** and open the Sites setup page. 3. Click **New** to create a new public site. 4. Fill in the required information — Site Label, Site Name, and Site Contact — and save. 5. Locate the new site in the list and click its name to open the site details. 6. Click **Public Access Settings**. 7. Under Public Access Settings, click **View Users** to see the users associated with the site. 8. Assign the **Leegality Webhook Permission Set** to the site's Guest User: open the user, click **Edit Assignments** under Permission Set Assignments, and add the permission set. 9. In Leegality (the webhook provider), set the webhook endpoint to: ``` https://{siteurl}/services/apexrest/LeegalityforSF/leegality/webhook/2.5/document ``` replacing `{siteurl}` with the URL of the public site you created. > **Info — Guest User permissions** > > Creating a site automatically generates a **Guest User**. This user must have **both** the **Leegality Webhook Permission Set** and the **Leegality External Credential Access** permission set for webhook and credential handling to work. ## Timezone configuration Dates and times in the integration are affected by three different timezone settings: - **Organization timezone** — the Apex job that updates document and invitee details runs on the organization's timezone setting. - **Current user timezone** — the Invitation Date and the date filters on All Documents follow the timezone of the current Salesforce user. - **Guest/site user timezone** — the webhook operates on the guest user's timezone setting. To ensure accurate date and time display, set the timezone to **Indian Standard Time (IST)** for the organization, all Salesforce users, and the site's guest user. This is necessary because the Leegality API responds in GMT, which Salesforce converts to IST based on these settings. See [Troubleshooting](https://knowledge.leegality.com/document-execution/integrations/salesforce/troubleshooting#dates-or-times-look-wrong) if you're seeing incorrect dates.