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.
I'm John Allspaw, co-founder of Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs