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
Next: Root
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
Hello,
We are looking into to the Atlassian access option to add a non billable policy.
We found the non billable info Here .
Question is what would that mean for the specific users whom we add to that policy? Are they restricted from any access?
Thx all for the info and help.
Kind regards,
Dirk
Hi @Dirk De Mal,
Welcome to the Community!
From the documentation there are a couple of caveats with setting up a non-billable policy.
First, if you have User Provisioning enabled and user coming from user provisioning cannot be included in the non-billable policy.
Once you have converted an authentication policy to a non-billable policy, any user you add to that policy will not be able to use SSO authentication and you can't enforce two factor authentication for them.
They will be treated as if Atlassian Access has not been setup for those users.
I hope that helps!
-Jimmy
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.