> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/quality-control/gates/create-quality-gates.md).

# Create Quality Gates

## Configure Quality Gate

Create a new Quality Gate -

1. Navigate to **`Quality Control`** -> **`Quality Gates`**
2. Click on **`New Quality Gate`**
3. Enter the basic details -
   1. **`Quality Gate Name`** - Enter a name of for the Quality Gate and click in **`Submit`** 
4. Once the Quality Gate is created, start adding conditions to match the organization standards
5. Click on **`Add Condition`** to add a new condition. Parameters include -
   1. **`Key`** - Metric Key to be validated
   2. **`Condition`** - Indicated the mathematical condition to be applied
   3. **`Value`** - Value to validate the metric value against\
       

      <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F6Kjsc9kMtZNc1S2HzkQW%2Fqg-conditions.png?alt=media&amp;token=30b68ef1-e476-4b84-8e5d-a36b8f82517e" alt=""><figcaption></figcaption></figure>
6. Click on **`Submit`** to create the Quality Gate condition&#x20;
7. Click on **`Configure Condition`** in the row to edit any of the existing conditions

### See Also

* [Quality Profiles](/product-guides/integral-zone/iz-suite/quality-control/profiles/quality-profiles.md)
* [Metric Profiles](/product-guides/integral-zone/iz-suite/quality-control/profiles/metric-profiles.md)
* [Quality Rules](/product-guides/integral-zone/iz-suite/quality-control/rules/quality-rules.md)
* [Metric Rules](/product-guides/integral-zone/iz-suite/quality-control/rules/metric-rules.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/quality-control/gates/create-quality-gates.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.