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!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Control of password strength and 2-factor authentication for guest accounts

We are using SAML and 2 factor authentication for our Jira and Confluence users. We now have very often external team members that need access. They will use their own e-mail to sign on. If I give them access to our URLs, do I have any control over the password strength that they use?

1 answer

1 accepted

0 votes
Answer accepted
Daniel Eads
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 17, 2019

Hi Frank,

Since Cloud users can be members of multiple instances, password policies are set at the email domain level rather than at each individual Jira/Confluence instance.

I'm guessing from your previous question that you've already gotten familiar with Atlassian Access (formerly known as Identity Manager). That's how organization owners set password policies, but it's specific to accounts for the email domain owned/claimed by that company.

In this sense, you control the password strength for your employees working across all Atlassian Cloud instance (even ones that you don't manage). But the downside as you're finding out is that you're at the mercy of "external" vendors to set the password strength for accounts in their organization. Erego, if the external team members have an email like, someone would need to verify with Atlassian Access to apply password policies to those users.

The minimum password strength for non-managed accounts is 8 characters (no complexity requirements). We hope users are selecting passwords stronger than this, but their domain would need to be verified with Atlassian Access to enforce a different policy.


Thank you. That would mean that if we want to enforce the password strength we would need to enforce that the people would use a P&G email.


Like Daniel Eads likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events