> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/sac-360/sac-360-common-questions/sac-360o-how-to-configure-lead-access-permissions.md).

# SAC 360º - How to configure Lead Access Permissions

<mark style="color:red;">**Step 1:**</mark> To access the Lead access settings, just click on the **gear** settings icon within the **SAC** (lower left corner):

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FOgGLhnBMGpbE8qopJLHW%2Fimage.png?alt=media&amp;token=31dcdcfa-6b47-412f-99e1-d08260fb1b61" alt=""><figcaption></figcaption></figure>

<mark style="color:red;">**Step 2**</mark><mark style="color:red;">:</mark> In **Service Settings**, it is possible to select who will have access to the Lead at the moment when the **support** is **is started**. By default, the selected option is "**Do not change permissions**".

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FsJaxRLlfJBSkPw3GLY8C%2Fimage.png?alt=media&amp;token=98b32b3b-2871-4251-bc0d-cd5d3b3c8bcb" alt=""><figcaption></figcaption></figure>

&#x20;

The option **"Add the Agent as Responsible for the Lead (automatic)"** will **change** the lead owner to the <mark style="color:red;">**agent who starts the service**</mark>, and will also adjust the lead permissions so that only the respective agent can view it.

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FWMkbO17TVEQYcofpkvXw%2Fimage.png?alt=media&amp;token=f525118d-3d3f-4553-918b-379658302258" alt=""><figcaption></figcaption></figure>

Note that there is also the option **"Add the Agent as Responsible for the Lead (ask)"** which performs the same settings mentioned above only if the agent **allows it**.

The option **"Add to the Lead the permissions configured in the Agent User (automatic)"** makes the access to this Lead the <mark style="color:red;">**same as those configured in "Access Permissions"**</mark> on the user edit screen. For more details on how to make these settings, see the article **Lead Permissions**: <https://docs.sprinthub.com/duvidas-comuns/permissoes/permissoes-do-lead>

<figure><img src="https://684109703-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9FzUKkagBNy5uQ7AtGNa%2Fuploads%2FS0rV05jdz3QbVPf0psAd%2Fimage.png?alt=media&amp;token=9de7eb62-a1cd-4b80-8fdf-cd6eef387b23" alt=""><figcaption></figcaption></figure>

As with the previous option, we can also set as **"Add to the Lead the permissions configured in the Agent User (ask)"** which performs the same settings mentioned above only if the agent **allows it**.

<mark style="color:red;">**Notes:**</mark>

* If the lead already has an owner when the service starts, it **will not be changed**.
* &#x20;If the lead already has access permissions configured when the service starts, **they will not be changed.**


---

# 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 dynamically by asking a question.

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

```
GET https://docs.sprinthub.com/en/topics/general/sac-360/sac-360-common-questions/sac-360o-how-to-configure-lead-access-permissions.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.