Hi,
I have started 30 days trial of Atlassian Access to test the functionality. I am bothered by our 700 and more billable users as they are only using free version of Trello. What would happen to this users if I moved them to un billable policy as I don’t see any reason for such a high bill just because of free Trello. They would still be able to sign in with Idp(google) but I would not be able to enforce SSO for them but for all other 1000 users I would be able to enforce SSO? I must admit this confuses me a bit 😅
Thank you for your answers.
Regards,
Nal
Hi @Nal Premik
This is a long story which is covered in this issue https://jira.atlassian.com/browse/ACCESS-1468
Unfortunately Atlassian decided not to implement anything about the free Trello users, which is causing billing problems for sure. For a user to belong to be a non-sso user he/she must have the following criteria:
On the other hand, a user is billable if:
If you want these users to have a SSO, then these 700 users will be billable. If not, then don't sync them and move them to a non billable policy (you may have only one).
Hi @Alex Koxaras _Relational_ thank you so much for your answer, I was able to change some of them to "not billed" but users who are synced from Google cannot be changed to "not billed" 😂 So now I just need to send all the users who were last active on Trello two years ago to remove it if that is even an option. Thank you very much again 🙂.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alex Koxaras _Relational_ ,
Do you have any experience if Jira Product Discovery Contributors need an Atlassian Access license?
Atlassian mentions that this group (if they don't have product access) don't need an Atlassian Access. But want happens if I need also SSO for Contributors?
Do I need an Atlassian Access license again?
Regards
Simon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nal Premik ,
For non-billable policy, you will not be able to enforce single sign-on or require two-step verification. You can only set password requirements and session duration.
It makes sense to add users to your non-billable policy when you do not want to count them against your Atlassian Access bill.
Please find detailed explanation of policies here.
Thanks,
Aditya
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.