Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Cloud Authentication Policies for Older Orgs

Hello -

I'm looking to use Atlassian Access to configure SAML for my Atlassian org. It's several years old so it does not have authentication policies. I see that there's a "workaround" detailed  although I'm not sure what impact following those steps will have on my users.

For example, when I remove my verified domain won't that trigger an email to all of my users saying that their Atlassian accounts are no longer centrally managed? And wouldn't they get another email when the domain gets validated in the new org?

Also, will this change the base URL we use for users to access our Jira and Confluence? ie: will change to

1 comment

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 14, 2021

Hi @terekha most organizations should have authentication policies now so you can create a separate policy to specifically test your SAML setup without disrupting your users. Hope this helps!


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events