> 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/codescan/quality-gates/customizing-quality-gates.md).
# Customizing Quality Gates
Quality Gates return a **Pass** or **Fail** (sometimes referred to as **Go/No-Go** rules) rating for analysis, depending on the selected criteria.
To create a new Quality Gate, follow the steps below:
1. Navigate to your organization's page and select the **Quality Gates** tab.
Quality Gates tab
2. **Copy** an existing Quality Gate to use as a template or select **Create** to design it from scratch.
3. Give it a unique name and select **Save**.
Create Quality Gate
4. To add desired conditions with their Warning and Error thresholds, click on **Add Condition**.
{% hint style="info" %}
Note: To customize a Quality Gate that is already in use, click on **Unlock editing** first, as shown below.
{% endhint %}
5. Conditions on **New Code** and **Old Code** must be added separately.
6. To assign Quality Gates to specific projects, use the **Project Settings > Quality Gates** menu for your project and select the one you would like to use.
7. A default **Quality Gate** can be set at the org level. Select **Set as Default.**
Then it will be assigned automatically to every new project, except those for which you specify a different gate. (See step 6.)
{% hint style="info" %}
**NOTE:** BUILT-IN Quality Gates are standard and can’t be edited. But you can always **Copy** and customize as needed. (See step 2.)
{% endhint %}
{% hint style="info" %}
**NOTE**: Changing the severity to '**Info**' will not block the Quality Gates.
{% endhint %}
---
# 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/codescan/quality-gates/customizing-quality-gates.md?ask=&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.
