Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

Table of Contents

Note
titleNot Yet Implemented

This document describes the Registry Enrollment mechanism introduced as part of COmanage Registry v0.9.4. For Registry Enrollment in older versions, see Registry Enrollment (Old).

...

COmanage Registry can also use customized Enrollment Flows to onboard new people into each organization. Enrollment Flows consists of a series of pre-defined steps, the execution of which is managed by Registry in accordance with the configuration of each specific Flow.Each

Enrollment Flow

...

Enrollment Flow Steps

See also: Registry Enrollment Flow Diagram

A step may be considered RequiredOptional, or Not Permitted, in accordance with the configuration. A Required step will execute both the core Registry functionality, as well as any Plugins. An Optional step will only execute Plugins, the core functionality will be skipped. Not Permitted means neither core nor Plugin functionality will be executed.

The order steps execute in may vary according to flow configuration.

Some "internal" steps are not documented here.

StepDescriptionCore Step Executes IfPlugins Run If Core Doesn't? (Optional)Petition Status Following Step
startInitial step of an enrollment flow. The Petition artifact is created following successful completion (including any Plugins) of this step.Introduction Text is definedYesCreated
selectEnrolleeSelect an existing identity (CO Person or Org Identity) for this enrollment.Identity Matching is set to SelfNoCreated
petitionerAttributesCollect attributes from the Petitioner.Enrollment Attributes are defined NoCreated
sendConfirmationSend an email to confirm deliverability of Enrollee email address.Require Confirmation of Email is setNo

Pending Confirmation

processConfirmationProcess the response to the email sent in the sendConfirmation step.Require Confirmation of Email is setNoConfirmed or Declined
collectIdentifierThe identifier used by the enrollee to authenticate (eg: $REMOTE_USER) is attached to the Org Identity created by the Petition.Require Confirmation of Email and Require Authentication are setNoConfirmed
sendApproverNotificationNotify the approvers configured for the Enrollment Flow that the Petition is read for review and approval.Require Approval For Enrollment is setNoPending Approval
approveProcess Petition approval.Require Approval For Enrollment is setNoApproved
denyProcess Petition denial.Require Approval For Enrollment is setNoDenied
sendApprovalNotificationNotify the enrollee that their Petition has been approved.Require Approval For Enrollment is setNoApproved
finalizeIf the Petition is not denied, assign identifiers and set person status to Active. NoFinalized or Denied

...