About Enrollment Flows and Petitions
Every organization has one or more ways of bringing new people into that organization. There are a number of terms used to described this process: application, enrollment, intake, invitation, petition, signup, etc. These processes vary significantly across organizations.
COmanage Registry has a sophisticated, configurable mechanism for representing these processes, and translating them into ways to bring people into a CO's registry. (You can see a representation of the model here.) COmanage Registry refers to these processes as Enrollment Flows, and the execution of these processes as Petitions.
Each CO can define as many Enrollment Flows as it needs to reflect it's specific processes, subject to the COmanage platform configuration. (A CO can also use the very basic default mechanism.) When a new person is to be enrolled, the new person (if self-signup is enabled) or an appropriate administrator creates a Petition to begin the process.
Creating Organizational Identities As Part of An Enrollment Flow
For COs that will not collect Organizational Identities from authoritative sources (ie: via LDAP or SAML), Enrollment Flows must be configured to collect this data. In order to allow this, the platform must be configured to enable this, via these instructions.
Once enabled, CO administrators will be able to add Enrollment Attributes to a CO Enrollment Flow with the type "Organizational Identity".
(See also the platform configuration Pooling Organizational Identities.)
Common Enrollment Patterns
Pattern |
Description |
CO Enrollment Flow Configuration Settings |
|---|---|---|
conscription |
Petitioner adds enrollee, possibly with CO admin approval but without enrollee confirmation. |
Enable Self Enrollment: No |
invitation |
Petitioner adds enrollee, possibly with CO admin approval. Enrollee confirms before becoming active. |
Enable Self Enrollment: No |
self-signup |
Enrollee is also petitioner. No approval processes needed for enrollee to become active. |
Enable Self Enrollment: Yes |
application |
Enrollee is also petitioner. Approval processes required before enrollee is active. |
Enable Self Enrollment: No |