...
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. |
| Note |
|---|
For Self-Signup enrollments, you will need to somehow provide the URL to start the enrollment to potential enrollees, perhaps by sending it in email or posting it on a web page. To obtain, the URL as an administrator, go to People >> Enroll to generate a list of available enrollment flows and copy the link from the appropriate Begin button. |