SonarQube Cloud organization concept
On this page
Projects on a repository platform are typically grouped into organizations. This enables teams to work together, define different permissions for different users, and configure common settings and features.
In GitHub and Azure DevOps collections of projects are called organizations, in BitBucket Cloud, workspaces, and in GitLab, groups. For simplicity, we will refer to all of these generically as organizations.
SonarQube Cloud uses the same organization-based structure. Each SonarQube Cloud organization represents a corresponding organization on the repository platform side. The SonarQube Cloud organization is created by importing the DevOps platform organization: the SonarQube Cloud organization is bound to the DevOps platform organization. (It's also possible to create organizations manually but they won't benefit from the same features.) A SonarQube Cloud user can be a member of one or several organizations.
SonarQube Cloud does not support linking an organization to more than one DevOps platform. If you want to link to more than one, you will need to create a separate organization to link to each DevOps platform.
Different management and analysis features are supported for an organization depending on its subscription plan.
The figure below shows SonarQube Cloud reproducing the organization-based structure of the DevOps platform service it is used with.
Related pages
- Setting up your organization
- Managing the organization's subscription
- Importing your GitHub organization
- Importing your Bitbucket workspace
- Importing your GitLab group
- Importing your Azure DevOps organization
- Performing global analysis setup
- Adding / removing members to / from your organization
- Managing the user groups in your organization
- Managing the organization-related permissions
- Managing the projects of your organization
Was this page helpful?
© 2008-2025 SonarSource SA. All rights reserved.
