> 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-company-fields.md).
# CRM - How to Block Stage Changes Based on Company Fields
In SprintHub, it is possible to configure locks to prevent a Lead or Company from advancing stages in the funnel if certain conditions are not met.
This feature ensures greater control of the sales process, preventing contacts from being moved without essential information from the **Company** filled in.
### How to configure the lock
1. **Access the CRM**
* Go to the “CRM” menu via *Find Services* or by typing the feature name directly.
2. **Open the Lock Settings**
* Within the CRM, locate the gear icon ⚙ to access the lock rules.
3. **Add a New Rule**
* Click on “Add Lock.”
* Choose the option **Company Fields** as the validation criterion.
4. **Set the Conditions**
* Select the company fields you want to make mandatory (example: Tax ID, Segment, Region).
* Configure the condition that will prevent the stage movement if the field is empty or has a specific value.
5. **Save the Configuration**
* After defining the rules, click **Save** to activate the lock.
***
{% 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.\
**Reinforcing:** if the Lead is not linked to a Company, the lock by company fields will have no effect.
**CONCLUSION**
With locks based on **Company Fields**, you ensure that only properly qualified contacts advance in the funnel. This prevents failures in the sales process and improves the quality of the pipeline.
---
# 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-company-fields.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.
