| Panel |
|---|
| Panel | |
|---|---|
|
About Enrollment Flows and Petitions
...
- Single valued Organizational Identity attributes (basically, those defined in cm_org_identities)
- Single valued CO Person Role attributes (basically, those defined in cm_co_person_roles)
- Extended Attributes
- CO Group Memberships
- An Enrollee can only be added to a CO Group as a member, not an owner
- By setting the default value to be not modifiable, the associated CO Group is fixed; otherwise a Petitioner can add the Enrollee to any available CO Group
- By setting a default value, flagging it as not modifiable, not hidden, and optional, the CO Group becomes opt-in (by the petitioner)
...
COmanage Registry can perform identity matching when enrollment is performed. This is the process of checking for existing CO People that might match the person being enrolled. Note that matching only happens during the execution of an enrollment flow, now when manually adding a new CO Person. The following matching policies are available:
- None: No matching is performed.
- Advisory: Potential matches are identified, but Registry does not take any action. See more on Advisory Matching, below.
- Automatic: If highly likely matches are found, Registry automatically links the Enrollee to the existing CO Person. If probable matches are found, the Petitioner is given an opportunity to select one. This option is not currently implemented. (CO-298)
- Self: The new enrollment is automatically linked to the Petitioner.
| Note |
|---|
For Self matching, at least one of Require Authentication, Require Confirmation of Email, or Require Approval must be enabled in order for the enrollment to proceed from Pending Approval status to Active. |
Advisory Matching
Advisory matching currently only
...
works when the following conditions are met:
- Advisory matching is configured for the enrollment flow.
- The field where data is entered is either a given or family name field.
If an enrollment flow is configured to collect more than one type of name, only the first set of name fields emitted will be enabled for Advisory Matching. - At least 3 characters are entered into the field.
Email Verification and Authentication
...
Pattern | Conscription | Invitation | Self-Signup | Application | Account Linking |
|---|---|---|---|---|---|
Description | Petitioner adds enrollee, possibly with CO admin approval but without enrollee confirmation. | Petitioner adds enrollee, possibly with CO admin approval. Enrollee confirms before becoming active. | Enrollee is also petitioner. No approval processes needed for enrollee to become active. | Enrollee is also petitioner. Approval processes required before enrollee is active. | Enrollee is also petitioner. Enrollee already exists in the CO, and wishes to add an additional organizational identity. |
Enrollment Authorization | Any other than None | Any other than None | None | None | CO Person or COU Person |
Identity Matching | Any other than Self | Any other than Self | Automatic or None | Automatic or None | Self |
Require Approval for Enrollment | Optional | Optional | Optional | Yes | No |
Require Confirmation of Email | Optional | Yes | Recommended | Recommended | Yes |
Require Authentication | Optional | Optional | Optional | Optional | Yes |
Additional Notes |
|
|
|
| CMP Enrollment Configuration must allow Attributes via CO Enrollment Flow. |
...