Resolve conflicting accounts
You may find that some of your users create a personal Google Account using your email address at your company or school. If you then sign up for a Google Cloud product and add those users to your organization's account, they'll have the same address in both their personal and work Google Account, which creates a conflicting account. When they next sign in to their personal Google Account, they'll be asked to resolve this conflicting account.What is a conflicting account?
A conflicting account exists if a user created a personal Google Account with the same email address as a Google Cloud account managed by your organization. Conflicting accounts most commonly occur if users sign in to other Google services before your organization signs up for Google Cloud.
What isn't a conflicting account? Personal Google accounts that don't use your organization's Google address as either the primary or alias email address. For example, a personal Gmail account (firstname.lastname@example.org) with no alias addresses is never a conflicting account.
After you add users who then have conflicting accounts, they're prompted to rename their personal Google Account the next time they sign in. All data within their personal account remains in the account when it's renamed.
If the user has added their organization-managed address as an alternate email address (or email alias) in their personal Google Account, the alias is removed from the personal accounts and the user sees this notification of change the next time they sign in.
Here are two suggestions on how to avoid conflicting accounts:
- Don't delete a user from your Google Account to address a conflicting account if that person is actively using your Google services for mail, calendar, and other services. Instead, resolve the conflict.
- Before adding users to your Google Account, ask them if they've created a personal Google Account using your organization's email address. If they have, ask them to rename their personal account. When they do this, the data in their personal accounts remains safe and accessible to them.
If you've already created the user's Google Account, the next time that user signs in to a consumer product, they'll be asked to change their account. For example, if email@example.com has a conflicting account with your organization, Jane is prompted to rename the account using a different email address the next time she signs into a consumer product. She has the following options:
- Rename the consumer account to a new Gmail address.
- Rename the consumer account to a non-Gmail address that she already owns (for example firstname.lastname@example.org).
- Sign in with a temporary username Google provides (email@example.com).
In all cases, the data in the user's personal accounts remains safe and accessible to them.