Users

User data is loaded into each organization from a CSV file. Each row becomes one user record; each column header becomes an attribute name stored in org_user_data.

CSV format

• UTF-8 encoding, comma-delimited
• First row: column headers. These become the attribute names referenced everywhere else in the configuration.
• Subsequent rows: one user per row, values in the same column order.

fullName,department,email,userName,upn
Anna Andersson,IT,[email protected],aanders,[email protected]

There are no required column names. The only constraint is that at least one column must be referenced by the displayName mapping in subject_template.

Attribute names are the link between layers

The column headers you choose here are the same names that appear in two other places in the configuration:

• organization_person_columns — controls which attributes are shown as columns in the admin user search UI. The key values must match column headers exactly.
• subject_template — maps attributes to VC claims using ${org_user_data.<columnHeader>} expressions.

Choose attribute names once and use them consistently across all three. See Credential content for a complete example.