Two different things people call “disconnecting”
GitLab accounts can involve two separate kinds of outside access, and they are cleaned up in different places:
| What you are removing | What it is | Where it is handled |
|---|---|---|
| A sign-in service | An external provider used to enter GitLab instead of, or alongside, the regular username-and-password login | Edit profile → Access → Password and authentication → Service sign-in |
| An authorized application | An app you previously allowed to read GitLab data on your behalf | The applications/authorizations area of your account settings |
Removing an authorized application does not remove a sign-in service, and disconnecting a sign-in service does not revoke an app’s access to your data. Treat them as separate tasks.
Before you disconnect anything
The risk in this task is simple: if the external provider is your only route into the account, disconnecting it can leave you with no way in. Confirm a fallback first.
- Identify the service you want to remove. Open Edit profile, then Access, then Password and authentication, then Service sign-in, and note which connected accounts are listed.
- Confirm a second, usable login route. Check that you know your GitLab username and password and that they actually work — sign out and back in with them, or verify the password through the account’s own recovery options, before touching the service sign-in list. If you are unsure of the password, resolve that first.
- Only then disconnect. Use the Disconnect control next to the connected account you want to remove.
- Verify immediately. Sign out and sign back in using the remaining route. If that fails, use the account recovery options rather than assuming the disconnect did not take effect.
GitLab can use external sign-in services in addition to its regular username-and-password login. Source
Connected sign-in services are managed under Edit profile, Access, Password and authentication, Service sign-in. Source
The Disconnect control next to a connected account removes that sign-in service. Source
Failure paths to plan for
- You are not sure the password works. Do not disconnect yet. Confirm or reset the password through the account’s own recovery flow while the external sign-in still works.
- The provider is also used elsewhere. Disconnecting it in GitLab affects only the GitLab connection; it does not close your account with the provider. Check the provider’s own settings if you want to review that side too.
- You meant to remove an app, not a login method. Stop here and use the app-review task instead; the Service sign-in page is the wrong place for that.
- You cannot reach the settings page at all. That is a sign-in problem, not a disconnect problem. Sort out access first.
After the sign-in service is removed
Disconnecting the service changes how you enter GitLab; it does not by itself review which applications still hold access to your account. If your goal is a broader cleanup, the next task is to review the apps you authorized: see review and revoke apps authorized with your GitLab account.
When a username search fits — and when it does not
If you are checking where a username appears publicly, a username lookup can surface public profile pages as leads. That is a different question from account security: a public match is not proof of ownership, and a search cannot show you which sign-in services an account uses or which apps it has authorized. For this task, the account settings pages above are the only reliable place to look.