-
Suggestion
-
Resolution: Unresolved
-
None
-
40
-
Current Situation
At the moment, whenever a Google Workspace integration is established in an Atlassian Cloud product, all the domains listed in that Google Workspace will have to login through Google Workspace. Also, it is not possible to remove a domain verified via the Google Workspace integration while the integration remains active.
Suggestion
Allow the admin to choose which domain to claim from Google Workspace list
Why is this important
Consider this scenario:
- A company has 2 domains for different set of users, domain abc.com and xyz.com
- abc.com is connected with Google Workspace and users are using Google account
- xyz.com is connected to Azure AD and users are using Microsoft account
If xyz.com is added to Google Workspace (with intention of creating alias only), all users under xyz.com will be forced to login through Google Workspace as it as the domain is claimed when added to Google Workspace.
- is duplicated by
-
- Closed
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
- relates to
-
[ACCESS-1271] Ability to choose which domain to claim through Google Workspace
We also fall into same category of having multiple domains with different Email accounts. An Option to choose domains to claim from the G-Suite list is very important.
Any update on when this feature will be released?
The feature to be able to claim users from specific domains/organizational Units in GSuite is crucial for an enterprise customer.
Our customer manages a few social entities, so they want to onboard the users from these social entities in phases. So it's not possible for our customer to onboard all users at once.
The users of these social entities are managed under Organizational Units in GSuite and they can be identified by the domain of their email address. We also noticed that GSuite integration does not provide an option for Org Admin to sync users from specific Organization Units nor domains.
As we know Atlassian will send an email notification to the users once an Atlassian Cloud account is created for them.
Hi everyone,
Thank you for raising and following this suggestion. Because there has been no user engagement (votes, watches, comments) over the last year, we have no plans to implement this in the foreseeable future. In order to set expectations, we're closing this request to focus on our upcoming roadmap.
If you still feel that this feature significantly impacts your team, please let us know on the ticket. Thanks again for continuing to provide valuable feedback to our team.
Regards,
The Identity PM team
This a blocker issue for us. The additional domain added to G Suite is not used for authentication, and only as an email alias. There is no user account associated with it so it is a bug for the G Suite integration to redirect to the Google login for this domain.
Administrators must have the ability to choose which domains are to be used for authentication.
There is background information here: https://support.google.com/domains/answer/6304395?hl=en
Any update?