Page History

...

1. Configure the EnvSource plugin, if not already done. (If you are reusing an existing plugin configuration, make sure it has exactly the same settings as below. If it does not have exactly the same settings as below you may instead create and configure a second instance of the EnvSource plugin.)
   1. Prior to Registry v4.0.0, do not attach a Pipeline to the plugin. (Pipelines are supported in Registry v4.0.0 and later.)
   2. Set Sync Mode to Manual.
   3. Enable Sync on Login, if appropriate.
   4. In the attribute configuration, flag at least one identifier type as Login.
2. Create a new Enrollment Flow with the following settings:
   
   1. Status: Active
   2. Petitioner Enrollment Authorization: Authenticated User
   3. Pipeline: None
   4. Identity Matching: None
   5. Require Approval: Optional
   6. Email Confirmation Mode: Optional
      1. Email confirmation requires v3.3.0 or later
3. Add CO Person and CO Person Role attributes as appropriate. Do not add any Organizational Identity attributes.
4. From the Enrollment Flow configuration page, click Attach Org Identity Sources.
5. Click  Add Enrollment Source.
   
   1. Organizational Identity Source: Select the Env Source you previously configured
   2. Org Identity Mode: Authenticate
      1. As of Registry v4.1.0, Identify mode is also supported for Org Identity Sources in a Self Signup flow. This is particularly useful if a Pipeline is attached to EnvSource, as it will defer CO Person creation or linking until after any enrollment attributes are collected.

Invitation (Registry v4.1.0 and later)

...