Why is this implemented for only those with Enterprise subscriptions to the tools that this control supports?  If I don't use Trello at all, for example, I should be able to block random managed accounts from creating it. 

I get you want to jack up ARR, but this is a really ugly way of doing it. 

We open a ticket with Atlassain EVERY time this happens.  If it costs us time, it's going to cost them time.

What a23395f92dd8 said! In addition it is really tedious to follow up the cleanup process on all managed accounts given the retention/deletion time.

This feature should be available for all the subscription tiers. It's unbelievable that it is locked behind a paywall. It's basically security risk in a company-managed site!

I've been talking with Atlassian support about accidental site creations. A new ticket has been created to reduce the chance that new sites will be created accidentally via the "sign-up" flow.

Note this new ticket is just about reducing the likelihood that new sites will be accidentally created, not preventing new sites completely. To quote the ticket description: "The intention of this Suggestion ticket is not to block new Cloud site creations, but to reduce the occurrences of accidental site creations".

I suggest you go and vote for / follow this new ticket: https://jira.atlassian.com/browse/CLOUD-12193

And as always I sent a reply I'm not happy with the 14/45 days deletion time ;

Thank you for sharing your concerns with us. I understand how frustrating this situation must be for you, and I truly appreciate your patience as we work toward a more permanent solution.
I would like to address your concerns and let you know that we value your feedback. We are actively engaging with our internal teams and directly expressing the frustration you are experiencing regarding this issue. Our goal is to provide enhanced shadow IT controls for non-enterprise customers, though I am unable to provide a specific timeline for when these improvements will be available.
Please note that I have initiated the hard deletion from my end to get the site "****" deleted and it will take around 14 days. I will soon share the final deletion date with you after I receive a confirmation from the internal team.
I sincerely appreciate your understanding and cooperation as we work together to resolve these issues.

Appreciate the perspective.  I think the point of frustration for a lot of us is, whether it can be deleted in 14 days, 45 days, or 1 minute, that this is entirely preventable by Atlassian and serves nobody's interest except Atlassian's interest in increasing their metrics and profit.  It is a frustrating and an total waste of everyone's time to have to deal with any of these sites being created by unwitting users who are misdirected by intentionally and poorly designed login pages.  The solution, according to Atlassian is, pay more.  I will happily pay more for other features that bring value to my teams, but this is a design decision by Atlassian to intentionally inflate their metrics and profit.  They would rather ignore the noise here than fix the problem, and the problem they have created is 101 security and manageability.  Its basic, not enterprise.   DO YOU HEAR US ATLASSIAN?   

0780f5450831 just wanted you and others know that as frustrating as this problem is (and I just had two new sites accidentally created in the last 24 hours, so it'd definitely still happening), you really can delete a site and the organization in less than 45 days (but more than 14). [Yes yes, it's a soft-delete, which I don't care about since it was an accidental site.]

Most recently, I had sites two Confluence sites created 20-Dec-2024. I cancelled them on 22-Dec-2024 and requested expedited deletion. On 10-Jan-2025 (20 days - maybe they took off Christmas and New Years), the sites were deleted, and I was able to delete the organizations as well.

Another more recent example: 5-Jan-2025 a Confluence site was created. It was cancelled 6-Jan-2025, and again after filing a ticket to request expedited deletion, it was finally deleted yesterday, 21-Jan-2025, and we were able to delete the org. That's 15 days exactly.

I wish I could automate this process. :-/

Hi all,

Indeed, we are all familiar with this typical repsonse by Atlassian support:

• When a site is marked for deletion, there is a 14-day period before you can proceed with deleting the organization. This time allows us to ensure that all necessary processes are in place to protect your data.You will be able to delete the organization 14 days after the deletion request is initiated. I will soon share the deletion date for your site after confirming with the internal team.
• Following this, there is an additional 30-day soft deletion window. This is part of Atlassian’s commitment to safeguarding your information against accidental loss. During this period, your data is tagged as "Soft Deleted" but not permanently erased. This provides a safety net in case the deletion was unintentional or if you need to recover any data.

What we really need is the same kind of responsibility and some proactivity (instead of reactivity) when a user is creating a site entirely by accident:

• We need the ability to control whether managed users are allowed (or not allowed) to request new sites or products
• When a user is allowed to request a new site or product, this must be subject to approval by an organization admin BEFORE the site or product is created!

This is the ONLY REASONABLE SOLUTION for this problem which is already lasting for way too long!

Stefaan

PS: for everyone following this topic, please also follow and vote for the below topics, because that's the only way to increase our visibility for this ENORMOUS PROBLEM with Atlassian products that have names or features like "PREMIUM", "MANAGED", "GUARD":

• https://jira.atlassian.com/browse/CLOUD-10325
• https://jira.atlassian.com/browse/CLOUD-12089
• https://jira.atlassian.com/browse/ACCESS-1135
• https://jira.atlassian.com/browse/ACCESS-1645
• https://jira.atlassian.com/browse/ACCESS-1468
• https://jira.atlassian.com/browse/ID-7697
• https://jira.atlassian.com/browse/ACCESS-1679
• https://community.atlassian.com/t5/Articles/What-s-the-word-I-m-looking-for/ba-p/2862486
• https://community.atlassian.com/t5/Confluence-questions/SECURITY-ISSUE-during-login-procedure-of-managed-users/qaq-p/2841895
• https://community.atlassian.com/t5/Atlassian-Account-questions/How-to-Prevent-Atlassian-Products-being-added-by-users-w-company/qaq-p/2401874
• https://community.atlassian.com/t5/Questions/Why-is-Atlassian-promoting-Shadow-IT-Or-Accidental-IT/qaq-p/2731538
• https://community.atlassian.com/t5/Enterprise-articles/An-update-on-product-requests-bringing-shadow-IT-controls-to/ba-p/2840760
• https://community.atlassian.com/t5/Articles/Proposal-to-prevent-Accidental-Site-Creations-accidentalit/ba-p/2867193#M558