> 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/crm/crm-initial-settings/crm-how-to-block-stage-changes-based-on-lead-status.md).
# CRM - How to Block Stage Changes Based on Lead Status
In SprintHub, it is possible to use the locking feature in the CRM to prevent a Lead from advancing stages or having its Status changed, according to the current Status. This functionality is essential to avoid incorrect movements in the pipeline, ensuring that only qualified Leads progress in the sales process.
This helps maintain organization, prevent failures due to lack of information, and stop unqualified Leads from advancing through the pipeline stages improperly.
#### 🚀 How to configure the lock in the CRM
1. **Access the “CRM” feature**
* Go to the side menu or use the shortcut **"Find Services"**;
* Type “CRM” and select the corresponding feature.
2. **Choose the Sales Funnel you want to configure**
* Click on the desired funnel to view its stages.
3. **Edit the stage where you want to apply the lock**
* Click on the stage edit icon;
* Enable the option **“Block stage or Status change based on the Lead's Status”**.
4. **Select the Statuses that should be blocked**
* Check the Statuses that will not allow movements;
* Save the changes to apply the configuration.
***
{% embed url="" %}
#### ⚠️ Important
The lock is applied only to manual stage changes. That is, movements performed by automations or external integrations will not be prevented by this setting.
**CONCLUSION**
With locks based on the Lead's Status, your team gains more control over the sales funnel, avoids operational failures, and focuses its efforts on the right Leads at the right time.
Use this feature to standardize processes, maintain data quality, and increase the efficiency of your sales team.
---
# 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/crm/crm-initial-settings/crm-how-to-block-stage-changes-based-on-lead-status.md?ask=&goal=
```
`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.
