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
Next: Root
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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Davor,
You should take a look at the following page for a detailed explanation: https://confluence.atlassian.com/display/CROWD/Effective+memberships+with+multiple+directories
Let's suppose you have an application called JIRA and that you linked this application to two directories in Crowd, for instance Directory A and Directory B (in this order). Now, let's also suppose that each of these directories has two groups called jira-users and jira-administrators.
Now, let's suppose that user john_doe belongs only to jira-users within Directory A and to both jira-users and jira-administrators within Directory B.
From JIRA's perspective, if you do not select aggregating membership, john_doe will only be a member of jira-users. However, if you do select aggregating membership, john_doe will be a member of both jira-users and jira-administrators.
Best regards,
Bruno
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.