...

• Manually, via People >> Organizational Identities >> Add New Org Identity From Source or by using the Search button from the list of Organizational Identity Sources.
• Using an Enrollment Flow, via Enrollment Sources.
• Via the Registry Job Shell syncorgsources and forcesyncorgsources tasks, as described below.

Organizational Identity Sources can be linked to Registry Pipelines in order to automatically create CO Person records.

...

• View Organizational Identity: Retrieves the current Org Identity operational record used by Registry in normal operations.
• View Organizational Identity Source: Performs a live query against the Org Identity Source backend and retrieves the current data as known to the backend. ie: This is the source's current data.
• View Organizational Identity Source Record: Retrieves the last data retrieved from the backend and used to create or update an Org Identity. ie: This is Registry's copy of the source data.
• Add New Org Identity From Source: Create a new Org Identity based on the Org Identity Source's data. In addition, this will create an Organizational Identity Source Record.
• Resync Org Identity From Source: Update the Org Identity and Organizational Identity Source Record using the latest (current) data available from the Org Identity Source.
• Configuration >> Organizational Identity Sources: Manage the plugins used to define and query one or more Org Identity Sources.

Sync Modes

Job Shell

When called from Registry Job Shell via the Organizational Identity Sources can be configured in one of several sync modes to allow periodic automatic synchronization of records via the Registry Job Shell. Prior to Registry v4.0.0, this is handled with the syncorgsources and forcesyncorgsources tasks, Organizational Identity Sources can be configured in the following sync modes:. As of Registry v4.0.0, this is handled via the Core Job Plugin Sync job.

• Full: Create new Org Identities for any record in the Organizational Identity Source that does not yet have one, and update (or delete, if appropriate) existing records.
• Query: Similar to Enrollment Sources Search mode, query the Organizational Identity Source for any records matching verified email addresses of all Org Identities, looking for new matching records to link. Also update (or delete, if appropriate) existing records.
  •  Query mode should only be used for Organizational Identity Sources attached to a Registry Pipeline configured for email address-based matching. Otherwise, linking to existing CO People may not happen correctly.
  • In Query mode, if a Organizational Identity Source is queried for an email address and the Source returns a record with a different email address (eg: the person changed their email address in the other system), by default a new Org Identity (and probably CO Person) will be created. This is because Registry has not confirmed the alternate email address and cannot trust the Organizational Identity Source asserting a record linkage. This corresponds to the Email Mismatch Mode of Create New Org Identity. Alternately, Email Mismatch Mode can be set to Ignore, in which case no action is taken.
  • In Query mode, by default the Organizational Identity Source will be re-queried for all email addresses, even those already attached to an Org Identity associated with the Source. This is to allow for the checking of additional records associated with the same email address. However, this can also create a large number of extra queries, if the Source is known not to create such records (or if such records are not of interest). To disable this behavior, set (tick the box for) Do Not Query for Known Email Addresses.
• Update: Update and delete (if appropriate) records that are already synced to Org Identities.
  • The syncorgsources task will skip any unchanged records, while the forcesyncorgsources task will process records even when they are unchanged. forcesyncorgsources is available as of Registry v3.2.0. As of Registry v4.0.0, it is accessed via the --force flag of the CoreJob Sync job.
  •  When the forcesyncorgsources task is run, the getChangeList() capability supported by some plugins cannot be used. This may result in significantly longer processing times. 
• Manual: Do not automatically sync records. Currently, manual syncing is only available on an individual record basis. (CO-1309)

...