> 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-cloud/administering-sonarcloud/managing-organization/setting-config-at-org-level/introduction.md).

# Introduction

With SonarQube Cloud Enterprise, your can define default settings for long-lived branch patterns, automatic analysis, and set your analysis scope, all of which can be overridden at the project level.

As an organization admin, you can define the new code definition that will apply to all new projects. You can also enable in-code issue resolution with `sonar-resolve` for your organization—see [#in-code-issue-resolution](#in-code-issue-resolution) below.

In addition, with the [Enterprise plan](https://www.sonarsource.com/plans-and-pricing/sonarcloud/):

* You can define the long-lived branches name pattern that will apply by default to all projects in the organization. This setting can be overridden at the project level.
* You can disable the automatic analysis for all new projects in the organization. This setting can be overridden at the project level.
* You can define the analysis scope adjustment that will apply by default to all projects in the organization. The adjustment can be overridden at the project level.

## In-code issue resolution <a href="#in-code-issue-resolution" id="in-code-issue-resolution"></a>

You can enable usage of in-code issue resolution with sonar-resolve for your SonarQube Cloud organization. To do this, retrieve your organization (see [Retrieving your organizations](/sonarqube-cloud/getting-started/viewing-organizations.md) for more information), then go to **Administration** > **Organization Settings** > **General** and activate the **Enable in-code issue resolution** setting. For more information on in-code issue resolution, see [Resolving issues in your code](/sonarqube-cloud/managing-your-projects/issues/editing.md#resolving-in-code).

You can enable `sonar-resolve` by default on all new projects using the **Enable in-code issue resolution for projects by default** setting.

See [Other advanced procedures](/sonarqube-cloud/managing-your-projects/administering-your-projects/advanced-administration/other-advanced-procedures.md#in-code-issue-resolution) to manage this setting at the project level.

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Setting new code definition](/sonarqube-cloud/administering-sonarcloud/managing-organization/setting-config-at-org-level/setting-new-code-definition-at-organization-level.md)
* [Setting long-lived branch pattern](/sonarqube-cloud/administering-sonarcloud/managing-organization/setting-config-at-org-level/setting-long-lived-branch-pattern.md)
* [Adjusting analysis scope](/sonarqube-cloud/administering-sonarcloud/managing-organization/setting-config-at-org-level/adjusting-analysis-scope.md)
* [Turning off automatic analysis](/sonarqube-cloud/administering-sonarcloud/managing-organization/setting-config-at-org-level/disabling-automatic-analysis.md)
* [Other advanced procedures](/sonarqube-cloud/managing-your-projects/administering-your-projects/advanced-administration/other-advanced-procedures.md#in-code-issue-resolution)


---

# 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-cloud/administering-sonarcloud/managing-organization/setting-config-at-org-level/introduction.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.