> For the complete documentation index, see [llms.txt](https://docs-vnext.kiflo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-vnext.kiflo.com/leads-deals/deal-pipeline/how-to-configure-condition-deal-stage-properties.md).
# How to configure conditional deal stage properties?
It is common for deals to be enriched while they move from stage to stage in your deal pipeline. The best example is ensuring you collect the "Closed lost reason" when a deal is moved to the lost stage.
Kiflo allows you to define which properties must be filled in for each deal stage.
## Configure conditional properties
* Go to the **Account Settings**
* Click on **Deal settings**
* Click on the button **Configure** in the Deal stages section
{% hint style="info" %}
**Don't know how to edit deal stages?**
Please read this article: [How to customize deal pipeline?](/leads-deals/deal-pipeline/customize-deal-pipeline.md)
{% endhint %}
In the **Conditional stage properties** section:
* Click the **Add property** button
* Search for the property you want to make required/optional for this stage
* Select it:
Once added you can make the property required or optional:
If the property is *required*, it is ***not*** possible to move deals into this stage (in the above example "Closed Lost") without providing a value.
If the property is *optional*, users are invited to fill it in but it won't block deals from moving into this stage if no value is provided.
{% hint style="warning" %}
**Don't forget to save!**
Don't forget to click the Save button once you're done configuring stages.
{% endhint %}
## Fill in conditional properties
Once configured, any user who moves a deal to the customized stage is presented with a form to fill in:
---
# 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-vnext.kiflo.com/leads-deals/deal-pipeline/how-to-configure-condition-deal-stage-properties.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.
