> 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/users-and-permissions/user-on-and-offboarding.md).

# User onboarding and offboarding

SonarQube Cloud creates user accounts automatically at first login and lets you delete only your own account. Without SCIM, SSO users removed from your identity provider remain in your organization.

## User onboarding <a href="#onboarding-users" id="onboarding-users"></a>

Whether through a DevOps platform or an SSO identity provider, when users first sign up with SonarQube Cloud, their account is automatically created in SonarQube Cloud.

At login time, users are automatically added to organizations in the following cases:

* For organizations bound to GitHub.com, through GitHub member synchronization when it's enabled. In this case, you cannot add DevOps platform (DOP) users manually.
* In an SSO-enabled enterprise, through Just-in-Time (JIT) or auto-provisioning. You cannot add SSO users manually.

Otherwise, you must manually add the DOP users to their organization, see [Adding organization members](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/organization-members.md) for more information.

{% hint style="info" %}
In an SSO-enabled enterprise, DOP users can be added manually to organizations.
{% endhint %}

## Deleting a DOP account <a href="#deleting-dop-account" id="deleting-dop-account"></a>

You can only delete your own account, see [Deleting your account](/sonarqube-cloud/managing-your-account/deleting.md). If you want to delete another user’s DevOps platform (DOP) account:

* If your organization uses GitHub member synchronization, remove the user from the GitHub.com organization.
* Otherwise, remove the user’s DOP account from the SonarQube Cloud organizations they are a member of, see [Adding organization members](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/organization-members.md).

## Deleting an SSO account <a href="#deleting-sso-account" id="deleting-sso-account"></a>

If you use the SCIM provisioning feature, SonarQube Cloud automatically deprovisions a user as soon as their account is deactivated or removed from your identity provider. For more information, see [About SSO and provisioning](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/about.md#scim).

Without SCIM, removing a user from your identity provider prevents them from logging in to SonarQube Cloud, but their account stays in the organization members list. You cannot remove SSO users from SonarQube Cloud.

{% hint style="info" %}
Just-in-Time (JIT) provisioning adds users to your organizations when they log in, but it does not remove them when you remove them from your identity provider.
{% endhint %}

To manage the user lifecycle automatically, including removing users from your organizations, set up SCIM provisioning. See the [Set up SCIM](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/set-up-scim.md) page.

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

* [Default authentication through DevOps platform](/sonarqube-cloud/administering-sonarcloud/about-sonarqube-cloud-solution/user-management/devops-platform-authentication.md)
* [Set up SCIM](/sonarqube-cloud/administering-sonarcloud/enterprise-security/sso-and-provisioning/set-up-scim.md)
* [Adding organization members](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/organization-members.md)
* [Managing user groups](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/user-groups.md)
* [Managing organization permissions](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/organization-permissions.md)
* [Disabling GitHub member synchronization](/sonarqube-cloud/administering-sonarcloud/managing-organization/users-and-permissions/github-member-sync.md)
* [Recovering organization admin access](/sonarqube-cloud/administering-sonarcloud/managing-organization/recovering-org-admin-access.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/users-and-permissions/user-on-and-offboarding.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.