-
Suggestion
-
Resolution: Answered
-
8
-
User Problem
The organisation administrators of Premium organisations need to have the ability to approve or deny the creation of new sites by their end users
Suggested Solutions
Provide the functionality to alert administrators before end users create new sites and provide them with the ability to approve or deny the request
Current Workarounds
Our product team is working on new functionality that would provide admin access to shadow IT sites. The next APD enhancement will provide org admins with one-click access to ‘join’, or add themselves to, shadow IT instances and take over the management of said instance to remove if necessary. This will be available to all organisations that have Atlassian Access, regardless if they are enterprise or not.
By using this new future feature Premium customers will have the ability to remove the sites post-creation.
- is related to
-
- Closed
[ACCESS-1651] Premium organisation admins ability to approve or deny the creation of new sites
| Assignee | New: Griffin Jones [ gjones@atlassian.com ] |
| Resolution | New: Answered [ 9 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
We truly value your suggestion and the thought you've put into it. The Cloud Enterprise (CE) plan solves the challenges of customers operating our products at a large scale by addressing their complexity, governance, advanced security, and compliance needs. The Atlassian Access product solves for more foundational security requirements and provides identity and access management support. We have implemented solutions for shadow IT risks based on customer differentiation in both CE and Atlassian Access.
For more information, see https://support.atlassian.com/organization-administration/docs/control-your-shadow-it-footprint/
Thanks for your understanding and for being such an important part of our community!
| Component/s | Original: Shadow IT - Discovered products [ 64995 ] | |
| Component/s | New: Shadow IT - Product requests [ 72893 ] |
| Support reference count | Original: 7 | New: 8 |
| Support reference count | Original: 6 | New: 7 |
| Support reference count | Original: 5 | New: 6 |
Following the lead of 3ea8e896bf0d, mentioning these related issues:
- https://jira.atlassian.com/browse/ACCESS-1272
- https://jira.atlassian.com/browse/CLOUD-10325
- https://jira.atlassian.com/browse/ACCESS-1468
- https://jira.atlassian.com/browse/ACCESS-1317
I will note that in my experience ALL 39 of the sites and orgs that I've had to remove were created BY MISTAKE, likely due to the bad sign-in workflow from atlassian.com
| Support reference count | Original: 4 | New: 5 |
48d91e7b076f, your post does not add any new information.
On the contrary, it looks like Atla$$ian keeps ignoring the elementary security of their "PREMIUM" and "GUARD" products.
These are only some of the tickets that I'm aware of (and many have been closed by Atla$$ian during the past years!):
Why exactly is it that your customers need to FIGHT against their "trusted supplier"?
Why is Atla$$ian not interested/willing to provide "good value for money" products?