Currently, Atlassian Cloud synchronizes Google Workspace groups based solely on the group display name. This approach creates a limitation for organizations that manage multiple domains and have legitimate use cases for groups with identical or similar names (differing only by case or domain), but unique email addresses or group IDs.

For example, an organization may have:

• DATA (data@abc.com)

• Data (data@abcd.com)

Both are distinct groups in Google Workspace, belonging to different domains and serving different purposes. However, Atlassian Cloud cannot sync both groups due to the display name conflict, even though their email addresses and unique Google Workspace group IDs are different.

Request:
Enhance Atlassian Cloud’s group synchronization logic to allow identification and syncing of groups based on unique Google Workspace group identifiers (such as group email address or group ID), rather than relying solely on the display name. This would enable organizations to sync all valid groups, regardless of naming similarities, and better support multi-domain environments.