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

What happens to our organization in Access if we also integrate an Okta sandbox?

My goal is to make our Atlassian Sandbox available to users in Okta.


What would be the impact to our current Production organization?


If we want to authenticate users using only the new sandbox, do we need segregation at the organization level, in effect, using a separate account?

1 answer

1 accepted

1 vote
Answer accepted
Ivan Lima
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 01, 2021

Hi @William Kennedy. For now, as you can only create Sandboxes for each linked product, they will be created underneath your linked product's organization. Therefore, users will follow the authentication process as per your organization. You can, however, make your Sandbox available to the set of users you grant access to. Wouldn't it be sufficient? It shouldn’t have any impact on your production sites.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events