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
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
I am implementing SAML and have third-party vendors with their emails (domains I do not own) accessing my instance.
Do I need to set them up with my domain emails or how do I implement the SAML functionality?
Yes, if possible, set them up with emails from domains you own. Please see Early Access Program for Identity Manager
Say your company is Acme Inc. and it owns the acme.com and acme.co.uk domains. Your users have Atlassian accounts with email addresses from those domains, for example email@example.com and firstname.lastname@example.org .
To use Identity Manager you first verify that you own those domains. Then we collect the Atlassian accounts with email addresses from those domains into what we call an ‘organization’.
Now you can use Identity Manager to apply security policies across all the Atlassian accounts in your organization. Wherever your users log in with their Atlassian account, they’ll all be subject to the same policies.
I am running into an issue where I am site administrator for two different organization's instances.
For example OrganizationA.atlassian.net I verified the domian as "organizationA". When I logged into OrganizationB.atlassian.net, it is displaying "organizationA' under the Organization and domain verified but these are two different instances and two different organizations.