Data import

The data import admin area is the organization’s control point for bringing data into the platform. Where the Import & export section covers how a person runs an import, this is the administrative view — the imports available and the record of what’s been brought in.

Provenance is the reason import deserves administrative oversight rather than being a purely user-level convenience. When a record originates outside the system, an auditor may reasonably ask where it came from and when it entered — and “someone imported it at some point” is not an answer. Keeping a governed import path with a recorded history means every imported record can be traced back to its source file and its moment of entry, so data that wasn’t authored natively is no less accountable than data that was.

Importing into the platform

Data import handles the sources the platform can ingest — the spreadsheets, documents, requirements interchange files, and SBOMs described in Import & export. Administering this centrally means imports follow a consistent, governed path into your governed records, rather than data arriving through ad-hoc side channels.

Import history

A history of imports is kept, so you can see what was brought in, from what source, and when. For regulated data this matters: when records originate from an import, being able to point to that import — its source and its timing — is part of the provenance an auditor may ask about. The history turns import from an invisible event into a traceable one.

Governed data in

The throughline is that data entering the platform becomes controlled records subject to the same governance as anything authored natively. The admin view ensures that path is overseen and recorded. The mechanics of mapping fields and previewing an import before it commits are covered in Requirements import and ReqIF & field mapping.