There are 4 types of authentication methods that Gearset supports:
​

If you need to change your Gearset login, this article outlines what you need to do.

If your Salesforce sandbox has been refreshed or if the org has moved instances, the user account Gearset uses to authenticate is now gone from Salesforce, so you won't be able to log in with that user account anymore.

You may have signed up for a Gearset account with a personal account and want to remove the association, e.g. changing from your personal Gmail to your professional Salesforce login.

If you signed up using Salesforce, you might want to change the username or the email associated in order to align with the rest of your team.

Gearset discourages the setting up of generic user accounts in Gearset, as these shared accounts lose many of the benefits of the team collaboration in Gearset - for example it’s hard to tell who did what as part of your audit trail. If your new username is a generic address, please chat to our friendly team to see if we can help.

The new username will not have any org or git connections, and you will need to set them up again.

The CI jobs (created by the old username) will have to be transferred to the new username, using the Transfer ownership feature.

The old deployment and comparison history belongs to the team and should still be there after the old account is removed from the team.

If the only team owner is the account that you've lost access to, please replace step 2 with: use the team owner email address to email [email protected] to say "Please add <new account name> to my team, and make <new account name> a team owner".

Once the new Gearset account is on the team, a team owner can transfer the license from your old user to your new user. For more information see this article.

By changing the username or email associated with the user in Salesforce, the information about the team member in Gearset will update as well.