Hello again,
In setting up Atlassian Access, we are learning that to do this we have to claim all of the email addresses in our domain in order to configure SSO. But our department Cloud instance will be for less than 1% of the total email address accounts. We realize that there are a handful of other departments at our institution who are Atlassian customers too. Plus there are a lot of Trello users who may be small groups in a department using its free tier. And there are alumni using their email address for personal/professional projects they have set up on Atlassian Cloud.
Has anyone else set up Access with SSO and run into this issue who could share how much extra "administration" you have to do for accounts that are not in your billable users? I've been asked to try to identify what additional workload I might have as an administrator if I have to "manage" users outside of our department.
Thanks,
Jack
Hi Dave,
I was able to export all the 12K+ Virginia.EDU domain email address related Atlassian accounts via the Access domain claim process without having to claim the accounts. The very first step offers an export feature and then I cancelled the claiming process. That resulting file provides names, status, what Atlassian resources they are using, last activity, etc. It was helpful for me to determine that the majority of people with accounts are using Trello.
Right now the claim is for all people in the domain. Our Atlassian Solutions Engineer did mention that Atlassian is working on a change to the Access domain claim to allow you to claim a subset of an email domain's accounts. But the timeframe on that is not soon enough for us.
Thanks,
Jack