Troubleshoot your G Suite connection
This page covers troubleshooting issues related to your G Suite connection.
| Problem | How to troubleshoot |
|---|---|
| Your users aren’t syncing. | Check your permissions:
|
| After syncing, the email address of a user’s Atlassian account changes. | Because your users must log in with Google and can’t use an email alias, G Suite will look at any email aliases (secondary email) associated with the account in G Suite and update the user's Atlassian account to use this primary email address instead. |
The email address of a user’s Atlassian account has +atlassian_conflict attached to it. | Before syncing, the email address of a Google account already linked to an Atlassian account was updated when there’s already another Atlassian account with that email address. To keep both accounts accessible, we change the email address of the non-linked Atlassian account, similar to Your users can still log in to both accounts:
|
| The full name in a user’s Atlassian account isn’t synced with the full name in the Google profile. | When you connect G Suite, Google's Directory API and the data there, including a user's full name. This data can only be updated by G Suite admins. However, Google allows G Suite admins to give users the ability to edit their profile (see Google documentation). If the user edits their name from their Google profile, that data isn’t available on the Directory API or the Atlassian G Suite integration. We recommend not allowing users to edit their name (see Google documentation) to avoid confusion. |
