-
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
-
ACCESS-1569 Google Workspace - Selective domain claim and default domain claim settings
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
- relates to
-
ENT-1528 Loading...
[ACCESS-1271] Ability to choose which domain to claim through Google Workspace
Support reference count | Original: 39 | New: 40 |
Support reference count | Original: 38 | New: 39 |
Support reference count | Original: 28 | New: 38 |
Support reference count | Original: 26 | New: 28 |
Support reference count | Original: 25 | New: 26 |
Remote Link | New: This issue links to "Page (Confluence)" [ 943835 ] |
Description |
Original:
h3. 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. h3. Suggestion Allow the admin to choose which domain to claim from Google Workspace list h3. 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. |
New:
h3. 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. h3. Suggestion Allow the admin to choose which domain to claim from Google Workspace list h3. 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. |
Support reference count | Original: 24 | New: 25 |
Remote Link | New: This issue links to "Page (Confluence)" [ 932165 ] |
Support reference count | Original: 23 | New: 24 |