b4ec286b8e12 as far as I know, it is required to have enterprise for all products, not just for one.

Does this mean it only works per product on Enterprise plan? Or is it a generic Enterprise administration feature working for all products?

Thanks to 7a79c351a973 for getting CLOUD-12193 - Reduce occurrences of accidental site creations created. I hope everyone can vote for this Suggestion that is actually addressing the issue of accidental creations.

There are some industries that are regulated whom use the Atlassian tool, my industry is one of them.  If an employee would happen to make an additional site, this could be a compliance risk if any company information is saved in a non-company approved tool. 

Ideally, admins could do these things:

1. Block any creation of Atlassian sites associated with any claimed domain.  For example: XYZ.atlassian.net would block any other creation of XYZxxx.atlassian.net or xxxXYZ.atlassian.net.  
2. Block claimed domain user accounts from creating a new Atlassian site without the admin approval.

It would be great if we claim a domain, if the admins of the claimed domain, would be notified in these 2 instances:

1. If a claimed domain account would create an Atlassian site (this is CURRENT capability)
2. If any Atlassian site is created with the matching names of any claimed domains, ex. user with private Atlassian account creates a site with company name (XYZ) in it, XYZxxxxxx.atlassian.net

Pretty wild that their workaround is not to enable org admins to block it, but to make org admins have substantially more work and time to shut things down after they're (very easily and quickly) created by users.

Unless you shell out for enterprise on EACH APP.

See also https://jira.atlassian.com/browse/ACCESS-1135?focusedId=3425851&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3425851 and https://support.atlassian.com/requests/JST-968487 

Support issue from a colleague of mine CA-2813147 relates to this and a clearly related critical issue I experienced, I'm awaiting Atlassian's replies to my feedback, which I suspect will be of interest to many of the other 1611 voters for this issue before the voting was frozen. 

Hi Atlassian,
Has this problem been solved and is it possible to prevent users from creating a administer product outside mcesys?

I spoke to Customer Service at Atlassian Unleash earlier this week. Short answer is that Atlassian don't see this as a problem, and it's working as intended. 

Where are we on this?  Can this issue be re-opened yet or not enough interest?

Non-Enterprise customers may be interested in watching this ticket: CLOUD-10325 – Allow non-Enterprise administrators to control managed users' associated sites and products 

Please include this in Premium. Any former employee that created their site, would still be a billable account to the main company site. We should be able to stop that or at the very least, prevent it from happening in the first place. 

Trello is a free app, but if they use their company email because they are using it for work, then that site will be alive until perpetuity without the main site being able to do anything about it.

Imagine having a premium account, and having many employees create their own Trello site... then those people leave and are replaced by people who created their own Trello site. Now the premium account can't do anything about it, because there is no way to prevent it.

Please enable this feature to Premium licensing users at the earliest.

At this point it is beyond apparent that if you don't pay them enough money they really don't give a rats about you.

@melanie,   yeah and who know how many users are no longer using the platform at this point because of how old this case is. or who switched orgs and cant access their accounts etc.  very  anti-customer move  by Atlassian

There's <100 votes on each of the four new tickets they created to downplay this one. If you haven't yet, please go vote on them all to encourage fixing this customer exploitation!

• https://jira.atlassian.com/browse/ACCESS-1645
• https://jira.atlassian.com/browse/CLOUD-11684
• https://jira.atlassian.com/browse/BCLOUD-22918
• https://jira.atlassian.com/browse/CLOUD-11690

Also, did anyone else notice a revision which removed "thank you" from Atlassian's update? :\

Is there a ticket created on the subject "Preventing access to a specific product"? (Possibility to remove access to specific products).
I did not find it. Thanks.

please vote and watch for the 4 new related tickets! 4 ticket for 1 topic ! 

WOW basically ignored everyone.

Lets call it what this is, hiding the age of the ticket by creating new ones. Now instead of looking almost 4 years old, it's just a recently created issue.

I mean, separating them into separate tickets so you can dilute the problem is a bold move, let's see how it plays out.

📣 1611 of us who voted on this, let's f*{}ing go.

@Asher - at this point considering how bungled this feature request seems to have materialized as I suspect Griffin may not even sure himself.

Instead of just letting all Atlassian Access subscribers regardless of the product subscription tier simply disable external sign ups FOR ANYTHING you've now got this splitting off into more individual product asks involving "shadow IT".

It's not even "shadow IT" based on the external instances we've dealt with, it's just curious staff members who have absolutely zero to do with anything remotely IT related.
It really shouldn't be this hard... but apparently it is for Atlassian's project managers.

Thanks Griffin, that was a lot of words for a very short answer to a very simple question.

Can I remove FREE trello users from my PAID Atlassian access yet? Do I now have complete control over who is contributing to my paid Atlassian access license, or do I still have to pay for free Trello/Bitbucket users?

Can this be added for Cloud Premium Users as well as this would really be beneficial to have?

https://getsupport.atlassian.com/browse/PCS-205212

We have got the feature deployed and we can't forbid people to create new products because "we don't have an enterprise subscription" for them ? 

We don't because we use Data Center, can someone please fix this and allow every Altassian Access Admin to completely manage their licenses and products?

Thanks

Graziella

It would be great if this was available for Atlassian Access users, not just enterprise. 

I followed the instrucitons and I dont see Trello as an option to disallow and thought maybe they are still in the process of setting this up and it will show eventually... Then I saw this comment... is this true?  Since we dont use it we cant block it???

Even with the Product Access options, since we are not paying for Trello, it does not show up on the Product Access page to disallow. The recent update to this page seems tone-deaf to the outcry from everyone dealing with the issue of free Trello accounts sucking up paid Atlassian Access licenses

Even with the Product Access options (supposedly live by today, Sept 15), since we are not paying for Trello as a firm, it does not show up on the Product Access page to disallow. The recent update to this page seems tone-deaf to the outcry from everyone dealing with the issue of free Trello accounts sucking up paid Atlassian Access licenses.

We need to have this to prevent unwanted usage of our Atlassian Access subscription - from the past we already have a few legacy sites that are consuming some of it - but we really want to prevent new users doing the same. Not even yet touching the whole security/privacy topics: we have no idea what they are doing in those environments.

Deleting bogus products is quite a hassle - reaching out to people gaining org admin rights, deleting the products, waiting for the cancellation term to be over, then removing the organization, then....

Please let us know when we can use it in Premium too!

Hi Griffin, great to see the progress on this topic. Is there any planning available when this can be used for 'premium' customers as wel? 

Hi Griffin,

Can we have some clarification about this feature?

There only available for Enterprise plan??? Or it's activate for the moment for Enterprise then for other plan later???

We're all concerned about the security of our companies' information, and letting our companies' users create uncontrolled jira, trello, confluence etc. instances is an information leak and therefore a security breach.

Its just shocking Atlassian has paywalled this behind the Enterprise plan.

Not including one of the most requested features for access management in the Access license is not a great look for Atlassian. Giving organizations the tools to manage their product licenses is a basic feature, and locking it behind the Enterprise license is unacceptable. 

If you are going to paywall the ability to get rid of unwanted Trello accounts burdening our Access licenses, at least allow everyone the option to remove the Trello accounts that's been active before the implementation of this critical access feature.

Hi Griffin,

I'm really at a loss here...
I do not understand why this is not included in Atlassian Access instead since Access is included in the Enterprise plan. It would also make much more sense then since this is related to product access.
And we would actually be ready to pay a tad more for Atlassian Access if that feature was part of it.

Could you at least explain the reasoning behind this decision?

Cheers.

Julien.

I agree, this should be standard functionality in Access, it is the only way to manage the (unwanted) Trello accounts.

I feel everyone's pain, particularly those who are paying for Atlassian Access.... which is the service that is supposed to be regulating access, except it doesn't. If its not going to be added to Access, I seriously doubt I will renew that product. Atlassian are getting way to proud of gouging.

What? Why is this only rolled out to enterprise customers ? We need this on premium plan also, we also need to be able to control this.

"Please help me, I'm drowning in unregulated instances of Trello being spun up and taking up SSO licenses"

Atlassian: "Sucks to be you, dude. Would you like to pay more instead?"

Looks like the community post only mentions the enterprise tier.
A feature tied to security improvements being pay walled is absolutely pathetic.

Might as well delete your core values off your primary website as based on your recent product deliveries you're no longer following half of them.

Absolutely disgusting decision to paywall this behind Enterprise. Guess Atlassian is striving away from their core values. "No Bullshit", am I right?

Great support. Glad to see this being rolled out finally. I'll be enabling this as soon as I can.

What is the timeline for rolling this out to Premium and Standard subscription levels?

@Atlassian.  UPDATE?

I'm not sure if this might have been stated already, but it seems like a simple fix would be to allow people to change their email addresses for Trello from their company managed email to a personal email address.   Then the problem goes away from an access license consumption perspective.

Hi Griffin,

You've promised this feature to be shipped in "late summer 2023". Now, the summer is gone. When can we expect an update, or the feature shipped?

Thanks,
Bela

@Tom Hawkins,   they pulled this same garbage with controlling users ability to create a free product instance, specifically trello, via Atlassian admin.  'oh its rolling out soon'   became 'its only for enterprise users.' so basically if you wanted to buy a feature to stop used from using a feature... pay us.

@Thomas Weston @Mark Benson not sure that the 15 May update ever mentioned Enterprise only, still waiting for a reply from @Griffin Jones to the below:
060d05276a1e added a comment - 11/Jul/2023 8:53 AM
@Griffin Jones, your Atlassian Update - 15 May 2023 doesn't mention it being for Enterprise users ONLY, so is it just that Enterprise users are getting it FIRST? If so, what's the ETA for other tiers? If it's to be ONLY Enterprise users EVER, then agree with @Robert Condon and other commenters. 

@Thomas Weston - ahh the good old ninja edit and just pretend like it was never the actual plan... classic.

It seems the 'enterprise' wording in the update from Atlassian has been removed here. It's still there on the product updates page, though

Hi Griffin,

Was anything rolled out or is there a definitive timing for it?

https://getsupport.atlassian.com/browse/PCS-204613

https://getsupport.atlassian.com/browse/PCS-204062

Hi,

You surely must ship this to any Atlassian Access subscriber because this is becoming quite of a nightmare between new instances spun up and free Trello accounts created... It makes absolutely no sense to bind this feature to the enterprise plan.

If you stay true to your values and want to make collaboration painless, you must ship this feature for any Atlassian Access subscriber so we can consolidate collaboration within a company by disallowing managed users to create new sites or use Atlassian tools that are not sanctioned by the company.

This is a huge mess right now.

Cheers.

Julien.

P.S: An update would be appreciated also, thanks.

Does anyone know a EAP or rollout date for this "late summer 2023" is this implying September?

Hey people, I'd say if you have an Atlassian CSR you should mention stuff like this to them. I've always had good luck in getting my CSR to pass along my feedback to product teams. It doesn't always change the outcome but it's a good additional avenue to let Atlassian know what's not working for you. 

I can only hope that some engineer somewhere is going to get this done this quarter.

please add to the user story:
"PREVENT access to specific product"