Changing login provider for manage.sanity and the need to create a new account.

Unfortunately, Sanity does not currently support changing or switching your login provider (like moving from GitHub to Google or email) for an existing account. This is an important limitation to be aware of.

According to the Platform terminology documentation, different login providers (email-password, Google, GitHub, etc.) do not map to the same Sanity user account even if they use the same email address. Each authentication method creates a separate user identity in Sanity's system.

Your Options

Since GitHub's 2FA changes are causing issues with shared login access, here are your alternatives:

1. Create a New Account with a Different Provider

You'll need to:

• Sign up with a new authentication method (Google or email/password)
• Have an existing organization or project administrator invite your new account to the relevant projects/organizations
• Transfer any necessary roles and permissions to the new account
• The old GitHub-authenticated account will remain separate but can be removed from projects once the transition is complete

2. Use SSO (Single Sign-On) - For Growth+ Plans

If you're on a Growth plan or higher, you can configure SAML SSO at the organization level. This allows you to:

• Control authentication through your own identity provider
• Map groups from your authentication provider to Sanity project roles
• Avoid dependence on individual social login providers
• Have centralized control over authentication

3. Set Up Individual Accounts for Team Members

Instead of sharing a GitHub login (which isn't recommended for security and accountability), each team member should:

• Create their own Sanity account with their preferred authentication method
• Be invited to the project/organization by an administrator
• Receive appropriate role-based permissions based on their responsibilities

Managing the Transition

If you need to transition ownership or administrative access:

• Organization administrators can manage project membership across all projects in the organization
• Project administrators can invite members to specific projects
• Make sure at least one person with admin access creates a new account first, so they can invite others
• You can have the same person hold admin roles on both the old and new accounts during the transition

The shared GitHub login approach was never ideal from a security or accountability perspective, so this GitHub 2FA change is actually a good opportunity to establish proper individual access for team members with clear role assignments!