> 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/relate/automation-flows/common-questions/automation-flow-change-lead-access-permissions.md).

# Automation Flow - Change Lead access permissions

#### With SprintHub, you can automate changes to your users' Lead access permissions, making Lead management more efficient and saving time. This provides greater convenience and control in management.

{% hint style="info" %}
*<mark style="color:blue;">This action is also found in the Chatbot, and in the SAC 360º and CRM Automations.</mark>*
{% endhint %}

To learn more about the **“Lead Permissions”**, see the link below:&#x20;

{% content-ref url="/pages/aecd327d7290f2940316788784b38a915e4ea7b3" %}
[Lead Permissions](/en/getting-started/lead-permissions.md)
{% endcontent-ref %}

It is recommended to create a segment to start this flow; to create “Segments”, see the link below:

{% content-ref url="/pages/430a797159546371edd1e2fbb2a4fe8a2e3ddca4" %}
[Segments](/en/topics/relate/segments.md)
{% endcontent-ref %}

### To create and run your flow, follow these steps:&#x20;

1. **Create the Automation Flow:**

* Go to Automation Flows via “Find Services”. Or just type the name, and the feature appears.
* To create, click “+ New”.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd3FZAy2VZ23vBPj2oqa25EK1j-IWkRIyhgXCsAnFtbycAhj6HgkqylXgEne4_5OdZpA2uVEXKFD7HZbbYeENVprN3WrqcDlUowIJPpGJD8c21Az0Stv4AdMutZgij6KNkTNkSRoYfquUf2MhaceVvcrN5D?key=D0ykPXfhFqkB9QnTs7y6mg" alt=""><figcaption></figcaption></figure>

2. **Configure and Create:**

* **Enter a Name:** Give your flow a descriptive name.
* **Enter a description:** detail of what will happen in the flow.
* **Set up a Segment:** Choose one you prefer.
* **Category:** Choose one you prefer. This is optional
* **Allow leads to restart the flow?:** It depends on your strategy.

> If left as “YES”, it will go through the flow more than once.

* Click “Open Builder” to create the flow with your actions and conditions.\ <br>

  <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXezGv_BeUANjDO9ki5elCOUsTqKFFAKm1WJaaC1kDAFhwkGqSpmW9DtFiuFbv2XREawiCI5kXuyAxf__dNsLRSkt8ymoAi7_MniV5qx9z3q7u4I6pdptFD0L1dHUC5ljBnshJ1uJz4mcMWzsY62svgqLaO8?key=D0ykPXfhFqkB9QnTs7y6mg" alt=""><figcaption></figcaption></figure>

3. **Building the Flow:**

* **Action:** Change Lead access permissions;

> There are many possibilities; see the one that best fits your strategy and needs.\
> In the example, the user was not defined as responsible for the Lead, only included in the permissions.

* Configure the action and include in the description exactly what the action will do;

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXebDuWtqzMCqcbeRpL3SgP57wxKRAxCLf9vyW-1hb9QFkz27e_6DefOl7ji60EmLEo5P-f7a41DndLL2iHB6nRPv91N_GkGmCRJxXkeqfg_ooqaGeqnmdu0tBbZ6PzhPJM_0Jxawf3-MHJ4Rx3z6R8E0k8?key=D0ykPXfhFqkB9QnTs7y6mg" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXf-RiJXuWXn__KE8uwQ6oQjTLRxSFLOZiaiShsYZabLwu5F-ldEKMSD9jYrY1zXyxZD4oyhn_N68EKuncI8IdQqTItnGa2ZN12tvBPYl4oztUzAjI3OV41E3uK1BjvGDtodlP2wqqalOG7LWhzTG7zSlaIs?key=D0ykPXfhFqkB9QnTs7y6mg" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXeRiJNxw5Ngc7UXMq5FH_-zUynzWBX20czi5_4TzToCjD5E-ediXz-1C5GovDHOhWBe8XtNLMkyR9KXustHoJ6WpzQ6_3lFDDA4eKEiq9k5ocgrugsF1MHPR4mAatwAH1RimNCVmuo3XnMY_QKFvdyVgQ-T?key=D0ykPXfhFqkB9QnTs7y6mg" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcwe5j53PpScB2KsQVtq9TXnH0By7GGI2wx25XyODyRPpUOL7nO5Kleaw9Tq76kK8AE1eRDhrqeEMN6_oHCMW6rN9RXKwvBl5lfQYZ69QAycorK8V9BvgtpkE4SLskWtSF4imQOmLXO5I0rX3lqUUnnJ88?key=D0ykPXfhFqkB9QnTs7y6mg" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXebaYIRPtyXRKj6J9ovgs-DV9s1q9MQhCQBZcJ7y6LDYgcfdfSg53L1ADmfS5u79c-63ypBBk5ryfq1YrHBYUPDcwFwW2UJ7-3rgt4os6trb8QTUA4kCplVslCCOzUMV98UG0iPycrrOBONZWsY_8gutduc?key=D0ykPXfhFqkB9QnTs7y6mg" alt=""><figcaption></figcaption></figure>

{% embed url="<https://youtu.be/AJ2JA2cLv2A>" %}

3. **Saving the Automation Flow:**

After creating and making the necessary changes, save your Flow and publish it.

* Published: When selecting "YES", the flow will start working immediately.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcPb9m41pnUdUkWjHQBixt2PSS0duLPI9nr5JFhd6bSxarP41pDeTnlP9tUsnzmWbuncWrU9OctO_5KSzKhd0r9vCJ-obtf5VcYYKU58myRzgsc5jcCukktWJ1gAqK7nGJt4Tr9NsDTQT1WrhCx_O1a_r2c?key=D0ykPXfhFqkB9QnTs7y6mg" alt=""><figcaption></figcaption></figure>

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcZDYgaXNyQaLUqe2gj_99_tLPE_98Uk80-AlX4rmjLiKTtFuijrHT2gxM1HYPt0pf-NQS-wPRLdZBWYp9XrO9dR8ALSmtyDuKVK_KhME-NV9-nybJm296rdCvgxcWA4biqLcezItHrMYNEVS8lX6E3TGg?key=D0ykPXfhFqkB9QnTs7y6mg" alt=""><figcaption></figcaption></figure>

*And that’s it, your data will already be sent and the action completed!*&#x20;


---

# 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/relate/automation-flows/common-questions/automation-flow-change-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.