• Delete your own account
• Delete users and user contributions
  • Associated records
• Delete the root account on a self-managed instance
  • Use the UI
  • Use the GitLab Rails console
• Troubleshooting
  • Deleting a user results in a PostgreSQL null value error

Deleting a user account

Users can be deleted from a GitLab instance, either by:

• The user themselves.
• An administrator.

Delete your own account

As a user, to delete your own account:

1. On the left sidebar, select your avatar.
2. Select Edit profile.
3. On the left sidebar, select Account.
4. Select Delete account.

Delete users and user contributions

As an administrator, to delete a user account:

1. On the left sidebar, at the bottom, select Admin.
2. Select Overview > Users.
3. Select a user.
4. Under the Account tab, select:
   • Delete user to delete only the user but maintain their associated records. You can’t use this option if the selected user is the sole owner of any groups.
   • Delete user and contributions to delete the user and their associated records. This option also removes all groups (and projects within these groups) where the user is the sole direct Owner of a group. Inherited ownership doesn’t apply.

Associated records

When deleting users, you can either:

• Delete just the user, but move contributions to a system-wide “Ghost User”:
  • The @ghost acts as a container for all deleted users’ contributions.
  • The user’s profile and personal projects are deleted, instead of moved to the Ghost User.
• Delete the user and their contributions, including:
  • Abuse reports.
  • Emoji reactions.
  • Groups of which the user is the only user with the Owner role.
  • Personal access tokens.
  • Epics.
  • Issues.
  • Merge requests.
  • Snippets.
  • Notes and comments on other users’ commits, epics, issues, merge requests and snippets.

In both cases, commits retain user information and therefore data integrity within a Git repository.

An alternative to deleting is blocking a user.

When a user is deleted from an abuse report or spam log, these associated records are always removed.

The deleting associated records option can be requested in the API as well as the Admin area.

Delete the root account on a self-managed instance

You can delete the root account using either the UI or the GitLab Rails console.

Before you delete the root account:

1. If you have created any project or personal access tokens for the root account and use them in your workflow, transfer any necessary permissions or ownership from the root account to the new administrator.
2. Back up your self-managed instance.
3. Consider deactivating or blocking the root account instead.

Use the UI

Prerequisites:

• You must be an administrator for the self-managed instance.

To delete the root account:

1. In the Admin area, create a new user with administrator access. This ensures that you maintain administrator access to the instance whilst mitigating the risks associated with deleting the root account.
2. Delete the root account.

Use the GitLab Rails console

Prerequisites:

• You must have access to the GitLab Rails console.

To delete the root account, in the Rails console:

1. Give another existing user administrator access:

   user = User.find(username: 'Username') # or use User.find_by(email: 'email@example.com') to find by email
   user.admin = true
   user.save!
   

   This ensures that you maintain administrator access to the instance whilst mitigating the risks associated with deleting the root account.

2. To delete the root account, do either of the following:

   • Block the root account:

     # This needs to be a current admin user
     current_user = User.find(username: 'Username')
     
     # This is the root user we want to block
     user = User.find(username: 'Username')
     
     ::Users::BlockService.new(current_user).execute(user)
     

   • Deactivate the root user:

     # This needs to be a current admin user
     current_user = User.find(username: 'Username')
     
     # This is the root user we want to deactivate
     user = User.find(username: 'Username')
     
     ::Users::DeactivateService.new(current_user, skip_authorization: true).execute(user)
     

Troubleshooting

Deleting a user results in a PostgreSQL null value error

There is a known issue that results in users not being deleted, and the following error generated:

ERROR: null value in column "user_id" violates not-null constraint

The error can be found in the PostgreSQL log and in the Retries section of the background jobs view in the Admin area.

If the user being deleted used the iterations feature, such as adding an issue to an iteration, you must use the workaround documented in the issue to delete the user.