Loading...

XML

Word

Printable

Support reference count:
43
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

Summary

For example, the user has two sites in his organization. They need to provision users and groups only to one site, there is no option to remove the site from the user provisioning.
There are cases where the same admins are working on 2 different set of domains, IDP and AA org. An admin may incorrectly attach a site to the wrong org and it won't be possible to unlink the site from the org afterwards.
When discontinuing AA or User Provisioning, it is not possible to unlink a site from an AA org. This causes the site-admin group to be disabled on the site.

Suggestion

Add an unlink/delete button to remove a site from the AA organization. Unlinking should reactivate the site-admin group locally in the cloud site.

Workaround

Remove user provisioning configuration
Transfer products where you don't want to use User Provisioning to another organization https://confluence.atlassian.com/cloud/transfer-products-to-another-organization-967318518.html
Set up User Provisioning again in your main organization

is duplicated by

ACCESS-880 Ability to remove provisioned users from linked sites

ACCESS-623 Ability to unlink a site from an Atlassian Access Organization

is related to

ACCESS-1009 Ability to control site/organization access for accounts via user provisioning

ID-7954 Approved site access based on provisioning attributes or groups

relates to

ACCESS-880 Ability to remove provisioned users from linked sites

ACCESS-623 Ability to unlink a site from an Atlassian Access Organization

ACCESS-1164 Ability to sync users to sites based on the groups

(2 relates to, 1 mentioned in)