> 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/creating-organization/binding-unbound-organization.md). # Binding an unbound organization Binding your unbound SonarQube Cloud organization is slightly different depending on your DevOps platform. If you created your organization manually, then it’s not bound to its corresponding DevOps platform organization and you don’t benefit from many advantages. This procedure explains how to bind your unbound organization. See [Binding with the DevOps platform](/sonarqube-cloud/administering-sonarcloud/about-sonarqube-cloud-solution/resources-structure/binding-with-dop.md) for more information. To do so, you need the corresponding permissions on your DevOps platform and the **Administer Organization** permission in SonarQube Cloud enabled. See [Managing organization permissions](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/organization-permissions.md) for more information. {% hint style="warning" %} * You cannot unbind nor change the binding of an organization bound to a GitLab group or an Azure organization. * If the binding fails because the organization already exists in SonarQube Cloud and you’ve lost administrator access to this organization, send a request to with all the necessary details. {% endhint %} ## Binding to a GitHub organization You must be an owner of the GitHub organization. ### To a GitHub.com organization 1. Log in to SonarQube Cloud with your GitHub account.\ If you’re a member of an enterprise, you may use any of your DevOps Platform accounts or your SSO account. In that case, see [Using multiple accounts](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-from-multiple-platforms.md) for important insights. 2. Retrieve your organization. See [Retrieving your organizations](/sonarqube-cloud/getting-started/viewing-organizations.md) for more information. 3. Go to **Administration** > **Organization settings** > **Organization binding**. 4. Select the **GitHub.com** button. The **Install SonarQube Cloud** page opens. The SonarQube Cloud app is required to allow SonarQube Cloud to access your GitHub organization. 5. Select the GitHub organization you want to import. 6. In **Repository access**, choose which Git repositories the **SonarQubeCloud** GitHub app can access. The app must have access to a repository for it to be imported to SonarQube Cloud, analyzed, and have its pull requests decorated. If a repository isn't accessible, it won't be available for import or analysis and its pull requests won't be decorated. You can always change this setting later, see [Importing GitHub.com organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-github-organization.md#modifying-repository-access) for more details. For help diagnosing a repository that isn't analyzed or decorated, see [Importing GitHub.com organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-github-organization.md#diagnosing-repository-access). 7. Select **Save**. Your SonarQube Cloud organization is bound. ### To a GHE.com Cloud organization *This feature is available in the* [*Enterprise*](https://www.sonarsource.com/plans-and-pricing/) *plan.* To bind an unbound organization to a GHE.com Cloud organization, you must add it to your existing SonarQube Cloud enterprise if it’s not already there. Proceed as follows: 1. Create the GHE.com application to be used to bind your SonarQube Cloud organization as described in [Importing GHE.com Cloud organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghecom-cloud-organization.md#step-1). You can also reuse an existing one. 2. Install the application as described in [Importing GHE.com Cloud organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghecom-cloud-organization.md#step-2). 3. Log in to SonarQube Cloud with your enterprise admin account and retrieve your SonarQube Cloud enterprise. 4. Go to **Organizations**. 5. If your organization is not part of your enterprise, add it as follows. Otherwise, go to the next step.\ a. Select **Add organization**. The **Add an organization** dialog opens.\ b. Select your GHE.com Cloud organization and confirm. Your organization is now added to your enterprise. 6. Select your organization from your enterprise list. Your organization page opens. 7. Select **Bind Organization** in the header. The Repository binding page opens. 8. Under **GitHub**, select **GHE.com Cloud**. The GitHub app details form opens. 9. Complete the form with the details of your GHE.com application. See [Importing GHE.com Cloud organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghecom-cloud-organization.md#step-3) for more information. 10. Select **Bind organization**. ### To a GHES organization *This feature is available in the* [*Enterprise*](https://www.sonarsource.com/plans-and-pricing/) *plan.* To bind an unbound organization to a GHES organization, you must add it to your existing SonarQube Cloud enterprise if it’s not already there. Proceed as follows: 1. Create the GHES application to be used to bind your SonarQube Cloud organization as described in [Importing GHES organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghes-organization.md#step-1). You can also reuse an existing one. 2. Install the application as described in [Importing GHES organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghes-organization.md#step-2). 3. Log in to SonarQube Cloud with your enterprise admin account and retrieve your SonarQube Cloud enterprise. 4. Go to **Organizations**. 5. If your organization is not part of your enterprise, add it as follows. Otherwise, go to the next step.\ a. Select **Add organization**. The **Add an organization** dialog opens.\ b. Select your GHES organization and confirm. Your organization is now added to your enterprise. 6. Select your organization from your enterprise list. Your organization page opens. 7. Select **Bind Organization** in the header. The Repository binding page opens. 8. Under **GitHub**, select **GHES**. The GitHub app details form opens. 9. Complete the form with the details of your GHES application. See [Importing GHES organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghes-organization.md#step-3) for more information. 10. Select **Bind organization**. ### Auto-import new GitHub repositories GitHub.com, GHE.com Cloud, and GHES all support the **Auto-import new GitHub repositories** feature. Once your organization is bound, you will see an additional option for this feature. It’s enabled by default. It automatically imports newly added or created repositories in your GitHub organization into SonarQube Cloud without having to go through the manual new project analysis setup flow. 1. As a requirement, **All repositories** must be selected in GitHub’s Repository Access settings. See [Importing GitHub.com organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-github-organization.md#modifying-repository-access) for more details. 2. Existing repositories in GitHub created prior to enabling the **Auto-import new GitHub repositories** feature are excluded. 3. Note that a sudden spike in new repositories might cause you to reach your plan limits and pause analysis. Ensure the plan you currently use has enough allowance.
Automatically import new GitHub repositories
## Binding to a Bitbucket Cloud workspace You must be an administrator of the Bitbucket workspace and have permission to install apps on it. If your organization was [created manually](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/creating-organization-manually.md) and isn't yet bound to a Bitbucket workspace, you can bind it using the **SonarQube Cloud for Bitbucket Cloud** app. 1. Log in to SonarQube Cloud with your Bitbucket account. 2. Retrieve your organization. See [Retrieving your organizations](/sonarqube-cloud/getting-started/viewing-organizations.md) for more information. 3. If the **SonarQube Cloud for Bitbucket Cloud** app isn't already installed on your Bitbucket workspace, install it:\ a. In SonarQube Cloud, go to **Administration** > **Organization settings** > **Organization binding**, then select **Bitbucket**.\ b. Select **Get app**, select your workspace, then select **Install**. 4. In Bitbucket, go to your **Workspace settings** > **Forge apps** > **SonarQube Cloud**. 5. Select your unbound organization from the list, then select **Connect**. Your organization is now bound and its repositories are available to import. ## Binding to a GitLab group You can bind your SonarQube Cloud organization to: * Any GitLab parent group of which you’re the owner. * Your personal GitLab group. This group refers to the repositories that are under your personal namespace. To bind your unbound organization to a GitLab group: 1. In GitLab, create the personal access token required by SonarQube Cloud to access the GitLab group. See [Importing GitLab group](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-gitlab-group.md#create-personal-access-token) for more details. 2. Log in to SonarQube Cloud with your GitLab account.\ If you’re a member of an enterprise, you may use any of your DevOps Platform accounts or your SSO account. In that case, see [Using multiple accounts](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-from-multiple-platforms.md) for important insights. 3. Retrieve your organization. See [Retrieving your organizations](/sonarqube-cloud/getting-started/viewing-organizations.md) for more information. 4. Go to **Administration** > **Organization settings** > **Organization binding**. 5. Select the **GitLab** button. 6. Select either * **Import any GitLab group**, if you want to import a GitLab group other than your personal one, or * **Import my personal GitLab group**, if you want to import only the repositories that are under your personal namespace. 7. **In GitLab group key** (if you don’t import your personal GitLab group), enter the group key. To retrieve the key, see [Importing GitLab group](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-gitlab-group.md#retrieve-group-key) for more information. 8. In **Personal Access Token**, paste the personal access token you created in the first step. ## Binding to an Azure DevOps organization You must be an administrator of the Azure DevOps organization. To bind your unbound organization to an Azure DevOps organization: 1. In Azure DevOps, create the Personal Access Token (PAT) required by SonarQube Cloud to access the Azure DevOps organization. See [Importing Azure DevOps organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-azure-devops-organization.md#create-pat) for more information. 2. Log in to SonarQube Cloud with your Azure DevOps account.\ If you’re a member of an enterprise, you may use any of your DevOps Platform accounts or your SSO account. In that case, see [Using multiple accounts](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-from-multiple-platforms.md) for important insights. 3. Retrieve your organization. See [Retrieving your organizations](/sonarqube-cloud/getting-started/viewing-organizations.md) for more information. 4. Go to **Administration** > **Organization settings** > **Organization binding**. 5. Select the **Azure DevOps** button. 6. Follow the instructions. 7. In **Personal Access Token**, paste the PAT you created in the first step. ## Related pages * [Importing GitHub.com organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-github-organization.md) * [Importing GHE.com Cloud organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghecom-cloud-organization.md) * [Importing GHES organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-ghes-organization.md) * [Importing Bitbucket workspace](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-bitbucket-workspace.md) * [Importing GitLab group](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-gitlab-group.md) * [Importing Azure DevOps organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-azure-devops-organization.md) * [Creating organization manually](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/creating-organization-manually.md) * [Changing organization binding](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/changing-organization-binding.md) * [Changing organization settings](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/changing-organization-settings.md) * [Deleting organization](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/deleting-organization.md) * [Using multiple accounts](/sonarqube-cloud/administering-sonarcloud/managing-organization/creating-organization/importing-from-multiple-platforms.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-cloud/administering-sonarcloud/managing-organization/creating-organization/binding-unbound-organization.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.