> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/quality-standards-administration/managing-quality-gates/changing-default-quality-gate.md). # Changing instance's default quality gate A default quality gate is assigned in your SonarQube Server 2026.5 settings. This quality gate is automatically applied to new projects and can be modified at any time. A default quality gate is defined in your instance: any project that is not explicitly associated with a quality gate, is associated with the default quality gate. The default quality gate is indicated in the UI with the `DEFAULT` tag. By default, the default quality gate is the built-in quality gate **Sonar way**. You can set any built-in or custom quality gate as the default quality gate. See the[Understanding quality gates](/sonarqube-server/quality-standards-administration/managing-quality-gates/introduction-to-quality-gates.md) to learn more. {% hint style="info" %} If you set as default a quality gate that is explicitly associated with projects, the explicit association is not shown anymore in the UI but is not removed: if you change again the default quality gate, the explicit association will show up again. {% endhint %} To change the default quality gate: 1. In the top navigation bar, select **Quality Gates**. 2. In the left panel, select the quality gate you want to set as default. 3. In the top right corner of the quality gate, select the action menu and then **Set as default**.
Setting a quality gate as a default one
To disable the fudge factor at the global level: 1. Go to **Administration** > **Configuration** > **General Settings** > **General** > **Quality Gate**. 2. Unselect the **Ignore duplication and coverage on small changes** option. ## Related pages * [Understanding quality gates](/sonarqube-server/quality-standards-administration/managing-quality-gates/introduction-to-quality-gates.md) * [Viewing a quality gate](/sonarqube-server/quality-standards-administration/managing-quality-gates/viewing-quality-gate.md) * [Managing custom quality gates](/sonarqube-server/quality-standards-administration/managing-quality-gates/managing-custom-quality-gates.md) * [Associating a quality gate with projects](/sonarqube-server/quality-standards-administration/managing-quality-gates/associating-projects-with-quality-gate.md) * [Quality gate for agentic AI](/sonarqube-server/quality-standards-administration/ai-code-assurance/quality-gate-for-agentic-ai.md) * [Notifications](/sonarqube-server/user-guide/managing-your-account/subscribing-to-notifications.md) * [Managing your project's quality gate](/sonarqube-server/project-administration/adjusting-analysis/changing-quality-gate-and-fudge-factor.md) * Changing the quality gate fudge factor: * [Quality standards](/sonarqube-server/instance-administration/analysis-functions/quality-standards.md) * [Managing your project's quality gate](/sonarqube-server/project-administration/adjusting-analysis/changing-quality-gate-and-fudge-factor.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://docs.sonarsource.com/sonarqube-server/quality-standards-administration/managing-quality-gates/changing-default-quality-gate.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.