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

Atlassian Access for sub-set of users

We are looking at using the Jira / Confluence Cloud and wanted to use SAML to protect our this particular cloud instance, so we signed up for Access. The cloud instance is for a small *subset* of all our users. It looks like from reading, I need to pull in all users, not simply the one Okta Group that I want to have authenticate with Jira / Confluence Cloud.


So far I have:

  • Verified ownership of my domain
  • Configured Okta and Access with a directory 


I have not:

  • Claimed accounts in Access


My concern is we have many teams using a email address that we *don't* want to manage and these teams are using other Atlassian Cloud products. 

If I claim the accounts are those users now required to use Access and I have to pay for and control their acces? I don't want to get charged $3 / user / month for these other users if they are now in Access.

2 answers

0 votes
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 23, 2022

Hi @Casey Daniell , Atlassian Access has a multiple authentication policies feature that allows you to pull subsets of users into different policies, including a non-billable one that will be excluded from the Atlassian Access coverage. Here's additional documentation that may be helpful: Does this help?

Why has this not been answered?



Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events