You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Recently one of our clients migrated from Server to Cloud and activated Atlassian Access (AA) as part of their Cloud migration. They were surprised to find that included in their AA license count were several people who were already using a free license for Trello. The client administrator was happy to see them use Trello, but didn’t see why they should pay for an AA license for a free product.
Trello will allow anyone to sign up for free to use Trello. There are paid tiers, but many folks have discovered what a great product Trello can be for an individual or a small team to manage their tasks and the free tier is all that is needed to use this great tool.
The downside is that if the user signs up with their business email and that email domain is managed by their company through Atlassian Access, then they become an AA licensed user. This means that the company needs to pay for their AA license even though their Trello usage was supposed to be free.
The only alternative to this, currently, is to instruct users that if they want to use Trello, they need to use a personal email address to sign up. It isn’t possible to “blacklist” Trello usage from with AA, thereby denying the corporate emails from using Trello. In the current state, the administrator will need to stay on top of how many users are using Trello and no other Atlassian product and then notify the user that they need to change. The only alternative is to deactivate their corporate email, which is almost never a valid option.
Have you encountered this problem? What has been your approach?
Atlassian Practice Manager
69 accepted answers