...
Pooling Organizational Identities
A given individual can have more than one Organizational Identity, and a given Organizational Identity can be affiliated with more than one CO Person. COmanage Registry can manage these relationships in different ways, according to how you design your platform.
By default, Organizational Identities are attached to the COs they are enrolled against. This means that if CO #1 and CO #2 both want to know about Pat Lee at Central University, each CO will have it's own copy of Pat Lee's Central University Organizational Identity. The reason for this is that COmanage Registry assumes, in a federated identity context, that attribute release policies between Central University and CO #1 are not the same as for attribute release policies between Central University and CO #2.
However, if Central University's attribute release policy applies to the entire platform, and not directly to the COs on a platform, Organizational Identities can (and should) be pooled. In this model, Pat Lee will have a single Central University Organizational Identity record, and both CO #1 and CO #2 will refer to it.
To enable pooling of Organizational Identities, log in to COmanage Registry as a platform administrator. Select "CMP Enrollment Configuration", check the box for "Pool Organizational Identities", and click "Save".
The correct option for you will depend on the relationship model between your platform and your COs
As of COmanage Registry v1.0.0, this setting can no longer be changed after setup. For more information, see Organizational Identity Pooling.
Populating Organizational Identity Attributes From Authoritative Sources
...