Atlassian is retiring the Bitbucket Connect app on Dec 1, 2026.
See Migrating to the Bitbucket Forge app for more details.
Ctrlk
Start FreeLogin
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Invite users to sign in

Complete your Single Sign-On (SSO) setup with SCIM or JIT provisioning in SonarQube Cloud and invite users to sign in.

After configuring Single Sign-On (SSO), complete your setup by verifying your domain, configuring your recovery account, setting up one-click access, and inviting users to sign in. Domain verification can be done during SSO setup or after it's already configured.

After configuring Single Sign-On (SSO), set up one-click access, invite users to sign in, and finalize your SSO setup.

If you don't use SCIM provisioning, create or verify first the user groups in SonarQube Cloud if not already done. See Managing groups in SonarQube Cloud if using JIT provisioning.

Step 1: Configure one-click access

SonarQube Cloud uses the Service Provider (SP) initiated SSO (IdP-initiated SSO is not supported except through the Okta dashboard if you set up SSO through the Okta Express Configuration). It means that SSO users must go to the login page of SonarQube Cloud.

Make sure to verify your company's email domain to avoid one-time email verification during SSO login.

If you want to use a shortcut link to access the SSO login, use https://sonarcloud.io/login/sso?enterprise_key=<enterprise_key>. You can copy this link directly from SonarQube Cloud as follows:

  1. Retrieve your enterprise. See Retrieving and viewing your enterprise for more details.

  2. Go to Administration > SSO & Provisioning.

  3. Expand the Single sign-on section and select Copy link in front of the Configure one-click access field.

Step 2: Invite users to sign in

You can now invite users to sign in to SonarQube Cloud with SSO. To do so, send them the login URL of your enterprise.

To retrieve the login URL of your enterprise:

  1. Retrieve your enterprise. See Retrieving and viewing your enterprise for more details.

  2. Go to Administration > SSO & Provisioning.

  3. Expand the Single sign-on section and select Copy link in front of the Invite users to sign in field. You can now paste the copied URL to your invite message.

Select Copy link.

  1. Users should check that they have access to their organization(s) in SonarQube Cloud. If they used the DevOps platform service authentication before, they should check that:

    • They can perform their tasks as before.

    • If using Personal Access Tokens (PAT): They can generate their analysis tokens with their SSO account. (They can still use their DevOps platform service (DOP) account tokens to execute analysis as long as their DOP account still exists). Note that from the Team plan, it's highly recommended to use Scoped Organization Tokens (SOT) instead of PATs.

Step 3: Terminate

  1. Sign out. Sign in through your enterprise's SSO login link. Check that your SSO account has access to your organization through its group membership. If it does not, check the group setup before you continue.

  2. Sign out. Sign in with a DevOps platform (DOP) account that has the Administer Enterprise permission. For example, use the account you used to create your enterprise. Give your SSO account the Administer Enterprise permission. See Managing the enterprise-related permissions for more details.

  3. Sign out. Sign in with your SSO account and configure your recovery account. See Recovery account for SSO for more details.

This step is strongly advised for all enterprise administrators. It lets you recover access to your enterprise if SSO login becomes unavailable.

  1. If you transitioned from a DevOps platform authentication service to SSO, you can remove the end users’ DOP accounts from the SonarQube Cloud organizations (see Adding organization members). These users can delete their DOP account within SonarQube Cloud (see Deleting your account).

Keep at least one admin or service user account in the DevOps platform. This is very important if you use Bitbucket Cloud, because you cannot link a SonarQube Cloud organization with a Bitbucket Cloud workspace using an SSO account.

Related pages

PreviousSet up SCIM
NextDomain verification

Last updated

Was this helpful?