Registry Enrollment Flow Configuration

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.

Default Enrollment (Invitation)

By default, COmanage Registry operates using an invitation-based enrollment flow. As a CO Admin, you can tell this is in effect by viewing "My Population" for your CO. There will be a button labeled " Invite" at the top of the page.

Defining Enrollment Flows

To customize enrollment, select "CO Enrollment Flows" from your CO's menu. You can define more than one flow, to allow for different enrollment processes.

After you define the basic settings of enrollment (see also the table below), define the attributes that will be collected as part of this flow.

XXX Certain attributes are required. Which ones?
XXX Default attribute values. (CO-283)
XXX Pre-packaged enrollment flows. (CO-323)

Once an Enrollment Flow is defined, the button at the top of the "My Population" page will become " Enroll" instead. Clicking that button will present a menu of available Enrollment Flows to execute.

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.)

Enrollment Authorization

Various authorization levels can be selected to determine who may initiate a given Enrollment Flow.

• CO Admin: Only a CO Admin for the CO. CO Admins can always initiate any Enrollment Flow within the CO.
• CO Group Member: Any member of the specified CO Group.
• CO or COU Admin: Any CO or COU Admin in the CO.
• CO Person: Any person who is a member of the CO.
• COU Admin: Any COU Admin for the specified COU.
• COU Person: Any person who is a member of the specified COU.
• None: No authorization required. Useful for self-signup patterns.

Identity Matching

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. The following matching policies are available:

• None: No matching is performed.
• Advisory: Potential matches are identified, but Registry does not take any action.
• 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.

Common Enrollment Patterns