The File Organizational Identity Source Plugin is designed to integrate using CSV files.


Org Identity Source ModeSupport
Manual Search and LinkingSupported
Enrollment, AuthenticatedNot supported
Enrollment, ClaimNot supported
Enrollment, SearchSupported
Enrollment, SelectSupported

Org Identity Sync ModeSupport


This is a non-core plugin, see Installing and Enabling Registry Plugins for more information.


The path specified in File Path must be readable by the COmanage Registry web server.

Archive Directory

As of Registry v3.1.0, FileSource supports an Archive Directory. If specified, this directory must be writeable by the COmanage Registry web server, and FileSource will maintain two previous copies of the source file (using the basename of the file, appended with .1 or .2). This allows FileSource to perform a diff in order to determine changed records, which performs significantly better for larger files.

(info) Use of this configuration option is especially recommended for source files containing more than a few hundred sync'd records.

Change Threshold

As of Registry v4.0.0, FileSource supports a Warning Threshold, which can prevent processing if an unexpectedly large number of changes (including new records) are detected. The threshold is expressed as a percentage (integer).

If a large number of changes are expected, the Warning Threshold Override can be enabled to skip the threshold check. The override will be automatically unset after processing. Note the first time a source is processed, the threshold check is automatically skipped. (The Core Job Plugin Sync job force parameter will also skip threshold checking, but the override is the recommended mechanism.)

File Format

As of Registry v4.0.0, multiple file formats are supported:

For earlier versions, the only supported version is CSV v1.

CSV, or comma-separated value format, is not consistently implemented everywhere. While there is an RFC defining the format, a given implementation may or may not support it fully. For the avoidance of doubt, FileSource uses PHP's CSV parsing functions, and so for any particular inconsistency PHP's behavior should be considered normative.

CSV v2

The first line of the file is a header documenting which columns are present in the file:

Remaining lines in the file each represent one inbound record, with columns as specified by the header.

Example files are attached to this page.

(info) CSV v2 format can be used with Pipeline Relationship Syncing by using the column names OrgIdentity.manager_identifier and OrgIdentity.sponsor_identifier.

CSV v1 (Legacy)

The file format is fixed, with the following columns:

1Unique Record KeyYes


4Given NameYes

6Family Name

7Street Address




11Postal Code


13Email Address

14Telephone Number

15Telephone Country Code

16National Identifier



19Match Reference Identifier

20Valid From
Any format supported by strtotime(), expected in UTC
21Valid Through
Any format supported by strtotime(), expected in UTC
22Personal URL
Added in v3.1.0

Affiliation corresponding to values of AffiliationEnum (Extended Types not supported)

Added in v3.2.0


Semi-colon (;) separated list of identifiers of the form type[+login]:value, where type corresponds to the values of IdentifierEnum (Extended Types not supported), the literal +login denotes that the identifier may be used for logging in, and value is the actual identifier

Added in v3.2.0

25Date of Birth
YYYY-MM-DD format. Added in v3.3.0.
26Ad Hoc Attributes

A JSON encoded list of ad hoc attributes, as tag/value pairs. The JSON document cannot contain linefeeds, and must be appropriately escaped for CSV. For example:


Note the comma is handled by the outer quotes.

Added in v3.3.0

See Also