> 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/common-questions/permissions/lead-permissions.md).

# Lead Permissions

To check a lead's Access Permissions, open its LEADS tab and search for the desired lead. Then click "Edit";

{% hint style="warning" %}
**Only the administrator user can access all leads with different permissions**
{% endhint %}

\
In the lead information, below the photo, click "**Access Permissions**";

<figure><img src="/files/1b23ff9ad645a1b10ed3b7a0e8b3684fcceb12f3" alt=""><figcaption></figcaption></figure>

**Responsible Employee:** Select who will be the user responsible for this lead. The user responsible for the lead will always have access to it, and their data will be used in some system automations (such as sending emails, for example).\
\
**Users and Departments:** Select which users and/or departments of the system will be able to **access** this lead (**in addition to the responsible employee**). If a user does not have access to the lead, **they&#x20;**<mark style="color:red;">**will not be able to view or edit it**</mark>**, regardless of their permissions in the system's “Permission Groups”**. If you leave the user and department lists **empty**, all system users will be able to access this lead.

{% hint style="danger" %}
This configuration is important, because depending on it, you may not be able to access opportunities in the sales pipeline, service records in SAC 360, and may even be unable to view the lead itself.
{% endhint %}


---

# 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/common-questions/permissions/lead-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.