Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

The Data Import page (/settings/data-import) is a central hub for initiating CSV-based bulk imports across the platform and reviewing the history of previously completed imports.

​
Overview

The page is gated by system.organizations.admin at the route level. It provides a grid of Start an Import cards — one per importable entity type — each of which navigates to the relevant module page where the actual import dialog lives. Entity types include employee roster, contacts, credentials, clinical oversight sessions, and custom object records. A Recent Imports section below uses useImportBatchesList to render a DataTable of pf_import_batches rows showing date, type, filename, row count, and created/skipped/failed counts. Deleting a history row removes the record from pf_import_batches only; imported records are unaffected.

​
Who it’s for

Requires permission system.organizations.admin.

​
Before you start

  • You must hold system.organizations.admin to access this page.
  • Individual import actions on module pages may require additional module-level permissions (e.g., hr.employees.create).

​
Steps

1

Open Data Import

Navigate to /settings/data-import. The page shows import shortcut cards and your organisation’s recent import history.
2

Start an import

Click a card in the Start an import section to navigate to the corresponding module page. Cards are disabled (dimmed) if you lack the required module permission.
3

Complete the import on the module page

Use the Import dialog on the destination page to upload a CSV file and map columns. Return to /settings/data-import afterward to see the result in history.
4

Review recent imports

The Recent imports table shows each batch with row counts for created, skipped, and failed records.
5

Remove an import from history

Click the trash icon on a history row to remove it. This does not delete the records that were imported.

​
Key concepts

Each start-import card is conditionally enabled based on a module-level permission check via useHasPermission. Cards for permissions you lack appear dimmed and non-interactive.
The history table records metadata about each import run. Deleting a history row only removes the metadata; the underlying imported records remain in their respective module tables.

Platform Foundation

Platform Foundation overview.

Governance & parity

Documentation coverage and governance.
This page documents shipped product behavior. It is not medical, legal, or billing advice. Verify against your organization’s policies and applicable regulations before using it for clinical, compliance, or billing decisions. Protected health information (PHI) shown in the product is governed by your tenant’s access controls and is never exposed in this documentation.
  • src/routes/platform.tsx
  • src/platform/settings/pages/DataImportPage.tsx
  • src/platform/import-batches/hooks/useImportBatchesList.ts