Skip to main content
A sample CSV showing the structure Lumos expects, with the required identity fields plus one custom attribute (Cost Center) and one permission (Role). Use the table below as the template for formatting your own exports: the header row is the structure, and the rows show valid values. You can also download the template.

​
Reading the template

Expected fields. Lumos expects Unique ID, First Name and Last Name, Email, and Status. Status values must be one of ACTIVE, INACTIVE, SUSPENDED, DEPROVISIONED, PENDING, or DELETED. Only email, or first and last name together, is strictly required. Custom attributes. Cost Center here stands in for any attribute column you add: department, location, employee type. Each mapped attribute column becomes a filterable attribute in Lumos. Permissions. The Role column demonstrates a permission mapping (Admin, Viewer, Helpdesk, User). Mapped permission columns become reviewable access in Lumos, which is what makes the file useful for Access Reviews rather than only a user list. Multiple entitlements. If an account holds several roles, either list them in one cell, separated by the connector’s Column Delimiter setting (a comma by default), or repeat the account across rows, one entitlement per row. With repeated rows, Lumos takes each account’s most recent Last Login and Last Activity across all its rows.

​
Preparing your data

  1. Export your account data from the source system.
  2. Map your existing column names to this template’s structure. Exact header names don’t matter, since you map columns to Lumos fields during import, but consistency does.
  3. Validate every row has a unique identifier and status values use the exact enumerations.
  4. Save as CSV UTF-8. From Excel: File > Save As, type CSV UTF-8 (Comma Delimited).
  5. Place the file in your S3 bucket or SFTP path and follow Connecting Flat Files with Lumos to connect and map it.

​
Common uses for flat file data

Contractor and supplier identity sourcing, where the flat file serves as the source of truth for account types your HR system doesn’t cover. Access reviews for legacy systems, since a mapped Role column is reviewable access. Bulk initial loads before a system moves to an API-based connector. And status monitoring across systems that only produce exports.

​
Keeping it healthy

Keep the status column current with employment status, keep formatting consistent for emails and IDs, and document any custom fields so future maintainers know what each column means. Regenerate the export on a schedule that matches how fresh you need the data, since Lumos reads the file daily by default and the data is only as current as the last export.