> 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-tutorial-videos/crm-status-field-approval-blocks.md).

# CRM - Status/Field/Approval Blocks

Set criteria to prevent opportunities from advancing or going back between the different stages.

It is very common for salespeople to move opportunities through the funnel stages and forget to fill in important fields. Imagine reaching an opportunity at the end of a stage for contract signing by email, and the Lead’s email doesn’t exist in the Lead record?

You create a series of automations to make everything automatic, and the system can’t execute the automations because the fields were not filled in or are filled in incorrectly.

With our Blocking module, you can control all of this.

Watch the video:

{% embed url="<https://www.youtube.com/watch?v=jcjanzPxt6M>" %}


---

# 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-tutorial-videos/crm-status-field-approval-blocks.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.