This is not an acceptable solution. As others have mentioned, limiting this to Enterprise when it impacts the cost around Atlassian Guard is just insulting to your Guard customers as well as bad optics as you are gating basic user management features that impact cost behind a higher tier. Especially considering Enterprise tier is only cost-savings when organizations are using multiple Jira/JSM sites (Premium + Standard Guard will always be more cost effective when using a single site).

Even if it is locked for Enterprise, in Enterprise you can't use it if you don't have also a Jira, Confluence JSM contract. So if a company that uses products from another vendor wants to just stop people from using Trello there is no way. That is the saddest part.

This is the exact solution I and so many others were looking for, it being locked to Enterprise plans is a crazy decision. Our main issue is users can freely use Trello and make us pay for it and Atlassian does not give us a way to help control this unless we do not use an identity provider (so non-billable policy). This should be a basic feature for companies that pay for your products. 

Dear gjones@atlassian.com ,

I hope this message finds you well. I am writing to follow up on the unresolved issue regarding Shadow IT control for Trello. Despite previous attempts to address the problem, the original issue remains unresolved. The provided workaround is not accessible to Atlassian Admin/Guard, as detailed in the following link: https://community.atlassian.com/t5/Enterprise-articles/An-update-on-product-requests-bringing-shadow-IT-controls-to/ba-p/2840760#M978.

Currently, Trello workspaces are only viewable and accessible on the Trello end-user side, and there is no solution to deactivate Trello product / Trello User access on Atlassian Admin Side.

Given these circumstances, I believe it is imperative to keep this ticket open until a viable solution is implemented. Your prompt attention to this matter is important.

Best regards,

gjones@atlassian.com - I've just found out that a Trello license can be freed up if the user no longer belongs to any Trello workspace. As long as the user is not associated with any workspace or boards in Trello, their Trello access will not count toward the company’s Atlassian Access (Atlassian Guard) license usage for Trello.
 
For example:
 
•When a user is removed from all Trello workspaces, their Trello account remains active, but they will no longer have access to Trello boards or workspaces.
•Since they are no longer part of a Trello workspace, they won’t consume an Atlassian Guard license for Trello.
•They can still be active in other Atlassian products, like Jira, without impacting the Trello licensing cost.
 
Just a suggestion:

• Allow the Org Admins to set a lifespan on a Trello workspace.
• If the user is not logging into it within this lifespan, they are automatically removed from the workspace. This would free up the guard license. 
• possibly allow the org admins to be the admin on a workspace, but without using up a license

Right now, I'm just working on getting a set of instructions to the end users and have them all log out of the Trello workspaces for accounts they are using up in Atl Guard. Very cumbersome, and we will have to manually monitor these Atl Guard licenses for the same issue. Clearly, a better solution is needed here for this. 

We are really disappointed with the decision to make this feature available only for Enterprise plans. The need for better administrative controls in Trello was raised back in 2020, and it seems like a basic access control feature that should be available for all user tiers. The fact that users who were migrated into the Atlassian Cloud and already had a Trello subscription are now required to use Guard licenses, and can't escape these license settings, is concerning.

gjones@atlassian.com, I hope Atlassian will reconsider this decision and make this feature available for all users.

gjones@atlassian.com - this is a major miss... This issue should not be closed, the feature did not match the desired outcome from the customer. Seriously, Atlassian who holds dear everything Agile, you didn't even involve the customer when building your feature. Super disappointed in this move.

If anything cheap shots like this discourage me, as an Atlassian admin, from pursuing more products for my organization.

Making this enterprise only is a real bad move. It probably solves an issue with a small handful of customers, rather than building trust within the larger pool of Atlassian evangelists here.

The story persona was "as an admin" - not "as an admin with an enterprise licence".

I'd love to know how this hit the AC, and how Atlassian thought at any point "our customers will happy with this".

I agree with e7fbeb34bb36 and f758dfca1d8c (nice near-Haiku btw!) this should not be closed until sorted for all user tiers, just as https://jira.atlassian.com/browse/ID-7697?focusedId=3515005&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-3515005 should not be closed please! 

gjones@atlassian.com Just to summarise. Trello experienced a data breach earlier in the year. Rightfully so, there has been an increased response for administrative controls to limit user access to Trello. Atlassian finally releases this functionality but behind a paywall.

I have to say the optics of this decision is incredibly poor, and quite frankly embarrassing.