Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×So I am currently faced with a requirement to add external users to our JIRA and Confluence platforms. However, this needs thorough security analysis as we deal with different external subsidaries.
Currently, we have 'jira-users' as the default group for newly added users (we dont manually create users, this is synced and automated from our AD), and there are tons of projects and schemes that have this group associated to them. Bear in mind that there currently are no external users added as yet, they sit in a seperate AD folder that is not linked as yet.
My question is whats the best approach for us to ensure that external users only have access to the space/s and project/s that they are supposed to have access to? Can we point the external user AD folder to an external_user group and create a rule that when an external user is added, they are by default added to the external_user group?
Regards
Rethabile M
Atlassian Government Cloud has achieved FedRAMP Authorization at the Moderate level! Join our webinar to learn how you can accelerate mission success and move work forward faster in cloud, all while ensuring your critical data is secure.
Register Now
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.