Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Setting up your enterprise

This page explains how to set up your SonarQube Cloud Enterprise as part of the Getting started with Enterprise.

With the Enterprise license, you can group together SonarQube Cloud organizations from different DevOps platforms into an enterprise and benefit from many features. Contact our team to request an Enterprise license. Provide the maximum number of Lines of Code (LOC) you want to have in your enterprise. For more information, see LOC-based pricing for more information.

This page explains how to set up your enterprise from scratch.

Currently, Sonar restricts each enterprise to a maximum of 200 organizations.

Before you start

Create a SonarQube Cloud account through a supported DevOps login provider: GitHub.com, Bitbucket, GitLab, or Azure DevOps. See Signing in via your DevOps platform service. GHE.com and GitHub Enterprise Server (GHES) credentials cannot provide this initial login.

Use this DevOps platform account to create your enterprise. It becomes the initial enterprise administrator. To administer the enterprise before you configure Single Sign-On (SSO), use a DevOps platform account with the Administer Enterprise permission.

To complete enterprise creation, you must administer the first organization you add. Create an organization during setup, or use an account with the Administer Organization permission on an existing organization. An SSO account cannot create an enterprise.

Step 1: Enter your enterprise details

  1. Sign in to SonarQube Cloud with your DevOps platform account.

  2. Select the + icon in the top right corner of SonarQube Cloud UI and select Create new enterprise in the menu.

Click the plus icon and select Create new enterprise in the menu.
  1. In License key, enter the key you received from Sonar.

  2. Enter the name and key of your enterprise.

  3. Select Next.

Step 2: Create or add the organizations

First, you must add your first organization. You can import and bind the corresponding DevOps platform organization, create an organization manually, or add an existing organization. Once an organization is added to your enterprise, it’s assigned the Enterprise plan.

The Create an organization step of enterprise creation, showing options to import from GitHub.com, GHE.com, GitLab.com, Bitbucket.org, or Azure DevOps; create an organization manually; or add an existing organization.

At the end of the operation, select Create Enterprise.

Enter the enterprise details and select Create enterprise.

The enterprise is created and you’re redirected to your enterprise’s Organizations page. You can now add other organizations to your enterprise. To do so, select Create organization to create a new organization, or Add organization to add an existing organization.

Select Create new organization. Alternatively, select Add organization to add an existing organization.

Step 3: Set the enterprise permissions of users

As an Enterprise Admin, you can grant the Administer Enterprise and Create Portfolios permissions. For more information, check out the Managing the enterprise-related permissions page.

To set the enterprise-related permissions of users, follow the instructions to Retrieving and viewing your enterprise. Once inside of your enterprise:

  1. Navigate to Administration > Enterprise Permissions.

  2. Filter the list by Admins or Creators, or search for specific users.

  3. For each user, toggle the Administer Enterprise and Create Portfolios permissions.

Enterprise permissions

Step 4: Complete the enterprise onboarding

For each organization in your enterprise:

By default, all organizations share the enterprise LOC limit. You can allocate an individual LOC limit to one or several organizations within your enterprise; please check the Managing the lines of code within your enterprise page.

With the Enterprise license, you can now set up enterprise security features. For more information, see Enterprise security.

If your enterprise includes GHE.com or GHES organizations, set up SSO for developer access. Importing these organizations does not configure user sign-in. See Signing in to SonarQube Cloud for GHE.com or GHES, and Invite users to sign in.

Step 5: Prepare developer IDE access

After the enterprise is created and organizations are attached, plan how developers will install SonarQube for IDE and bind their projects in SonarQube for IDE. Connected mode applies your SonarQube Cloud quality profiles, rule selections, file exclusions, and issue states in the IDE.

SonarQube for IDE is available for VS Code, IntelliJ, Visual Studio, and Eclipse. If your organization manages VS Code extensions through a VS Code Private Marketplace, add SonarQube for VS Code to the private catalog before developer onboarding.

Last updated

Was this helpful?