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
Hi all, I would like to start a discussion about Atlassian Access and surprises it brings to our customer usecases. I have some feedback from our solution architects here and I want to compare it with your experience.
We always liked Atlassian products because it had very clear payment plans (tiers). Customer always knew what will be final price of the solution.
With cloud we have more plans but it is still quite clear.
With Atlassian Access, there are some pitfalls. First one for me is that if your employee already has an Atlassian Account created for his domain email and the domain is not verified, so when the company buys an Access and enables some security policy, the employees account is automatically calculated as paid account.
Also most of our customers need an Access because of synchronization of user accounts from Active Directory. This functionality was available on Jira Server by default, on Cloud they need to pay 3$/account (companies to 250 employees). Price for Jira Standard is 5$/account. When the customer compares functionality of Jira Work Management and Access (they only use AD synchronization), they just don't understand that price for the whole solution increases by more than 50% because of Access.
I think it would be great to have an Access as part of the pricing of Premium and Enterprise and to pay only for access to the domains the company really owns.
Did you have to argue with some of your customer? What was your response? Or are we missing any best practices for Access implementation? What is your experience?