-
Suggestion
-
Resolution: Fixed
-
52
-
Add an enhancement to the Atlassian Access Automatic Product Discovery feature to allow admins to 'add' themselves to an unmanaged instances and take control of the site.
- is related to
-
- Closed
- supersedes
-
- Closed
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
[ACCESS-1645] Add admin to unmanaged user-created sites
Hello, we recently migrated to the cloud.
The problem still exists for all those who have not subscribed to the Enterprise plan.
The management of product requests is only available for the Enterprise plan.
Please also make it available for the other plans ‘Standard’ and ‘Premium’.
As an organisation admin, I can authorise myself to the site, at least somewhat.
However, it is very time-consuming to create a ticket for deletion for every site created by mistake.
As an organisation, we would like to decide for ourselves whether employees can create additional sites.
Hi all, we are excited to share that the enhancements to Automatic Product Discovery are now live for Atlassian Access admins to take advantage of. For full details on our solution, please visit our community announcement.
Best,
Griffin
Due to the current economy, and companies looking to scale back, I'd rather cut the users that aren't actually using these shadow IT products anymore than scale back actual users that use our real systems. Please fix this!
+10 
we have the same issue; this also poses security-issues as we can't manage the contents of these products. Critical company data could easily leak this way.
Can this finally be implemented, please - as the initial request (comp. https://jira.atlassian.com/browse/ACCESS-1468) is already from 30/Jan/2020 ???
This is genuinely asinine since this request https://jira.atlassian.com/browse/ACCESS-1468 is being split into multiple issues.
When people talk about rigging the vote, diluting the constituency, invalidating the polls, or just generally intentionally missing the point, this is EXACTLY what they mean, this ticket and its siblings, right here.
Yes, we're mad about this. This is infuriating.
See also: Gerrymandering - Wikipedia
+1
Absolutely necessary for Org Admins to be able to manage domain-verified user-created sites.
This is a very important security feature, which should have been there already since a long time!
As an organization administrator for an organization that is using Atlassian Access, I still don't have any control over the users of my organization. They can create as many sites as they want, and I have to beg them to make me an "organization admin" for their sites.
The fact that the development of such an important feature gets delayed (and moved to new tickets), shows that Atlassian is still preferring the "shadow IT" way of working above the "enterprise IT".
Nevertheless, Atlassian is interested to sell their products to enterprises, and is charging additional for "Atlassian Access" and "Enterprise subscriptions". So they want the money, but still keep thinking in the "shadow IT" way of working.
So, this is one of those “why are we waiting to gather interest” moments that baffles my mind. The increasing regularity of SaaS-related breaches to security incidents, should be a major concern. The impact to Atlassian’s reputation and their end users, confirms the need for Securing SaaS / Cloud platforms at all cost.
Let’s face it: Any vendor that provides (SaaS) applications must take security risks seriously, from shadow IT, data protection, to compliance requirements.
Currently Administrators are prevented from having any visibility and control over their own applications, users, and data caused by Shadow IT environments. Not to forget personal workspaces in the Bitbucket, which I hope is included in this request also. Add to that current inadequate monitoring and logging for cloud products and insider threats caused by * negligent or malicious * employees.
Would you agree, empowering administrators to take control of their environment to prevent and protect both Atlassian’s reputation and their customers should be a major concern? A priority item that needs fixing? 
By the way, the capability to protect one’s environment should not be a license-based functionality. If you are a cloud provider, it should be a major security feature that is required for all plans offered. 
nothing like a company trying to hide feature requests by moving it to new tickets and delaying development.
an essential feature of atlassian access. But what's the point of paying so much for it?
This is incredibly important for organization admins just so we can make sure all of our environments are properly protected within the org.
3c1174b9abcf ,
Please check this article (and scroll through the long history of posts):
Other related topics:
Shame on Atlassian!
They couldn't care less about their customers!
Stefaan