...
- A COmanage installation is referred to as a Collaboration Management Platform, or CMP.
- A CMP is a multi-tenant installation, each tenant is referred to as a Collaborative Organization or CO.
- The core operational record of a participant within the CO is the CO Person.
- The CO Person record maintains information that is unique to a person within the CO, such as names and identifiers.
- An individual person should only have one CO Person record within a CO.
- However, an individual person may participate in multiple COs housed within the same CMP, and could therefore have multiple CO Person records (each isolated from the other) within the CMP.
- In order for a person to become a CO Person, they must first have at least one Organizational Identity, which conceptually represents their identity as asserted by a "home" or "external" institution, such as their University or a social identity provider.
- It is possible for Org Identity records to be pooled across all COs within the CMP, however this setting is deprecated and not recommended.
- A person's external credentials (federated or social login information) are attached to the Organizational Identity, and typically used for access to the platform's services.
- A CO Person record is created and one or more Org Identities are linked to it.
- A CO Person may have one or more CO Person Roles within the CO. A CO Person Role record maintains information that is unique to a role a person has within a CO, such as title and physical address.
- For some use cases, it is necessary for the CO to manage credentials such as SSH Keys. In this case, these Authenticators attach to the CO Person.
There are two ways to create sets of CO People within a CO.
...