1In one sentence#

The Export Centre is LumosCRM's central data-export pipeline — request an export of clients, requests, vendors, invoices, events, or other datasets as PDF, Excel, or CSV; the job runs in the background with the requester's own access scope, lands as a secure, downloadable file, and every export is logged for compliance.

It's the safe, governed way to get data out of the CRM — into a spreadsheet, a board pack, or an auditor's hands.

2Who it's for#

Role	What they get
Anyone with export rights	A simple way to pull a dataset into PDF/Excel/CSV without blocking the UI.
Finance & leadership	Data for spreadsheets, reporting, and board materials.
Compliance	A logged, access-scoped, governed export trail — no uncontrolled data leakage.

3The core idea: governed, scoped, asynchronous#

Exports are treated as jobs, not instant downloads, for three good reasons:

   Request export ──▶  Background job runs AS the requester (their data scope)
                              │
                    File generated (PDF / Excel / CSV)
                              │
                 Stored securely (encryption per data classification)
                              │
              Requester downloads · every export is audit-logged

Scoped to the requester: the job runs as the person who asked, so an export can never contain records that person isn't allowed to see. Self-scoping and permissions carry through.
Asynchronous: large exports run in the background and don't freeze the app; the user is notified when their file is ready.
Governed: files are stored with encryption appropriate to their sensitivity, and every export is recorded.

4Capabilities at a glance#

Capability	What it means
Multi-format export	PDF, Excel, and CSV outputs.
Multiple datasets	Export across the core business datasets (clients, requests, vendors, invoices, events, and more).
Background processing	Exports run as queued jobs; the UI stays responsive.
Scoped to requester	Output contains only what the requester is entitled to see.
Secure storage	Generated files are stored encrypted, by classification.
Download & manage	View export status, download the result, and cancel jobs.
Audit log	Every export is recorded for compliance.
Single permission	A clear, dedicated permission to create exports.

5The Export Centre screen#

A list of export jobs with their status, plus a New export action. Creating an export lets the user pick the dataset and format; the job is queued and its status updates as it runs. When ready, the file can be downloaded; in-flight jobs can be cancelled.

6Security & compliance#

Access-scoped generation: the export job executes with the requester's identity and data scope — it physically cannot include records they can't access.
Permission-gated: creating exports requires the dedicated export permission.
Encrypted storage: output files are stored with encryption matched to the data's classification.
Tamper-evident delivery & audit: exports are recorded in an audit log, and delivery uses signed/verifiable mechanisms.
Housekeeping: old export files are purged on a schedule so sensitive data doesn't linger.

7Use cases & scenarios#

Use case A — A client list for a campaign#

A manager exports their clients to Excel. Because the job runs as them, it includes only their own clients — not the whole book.

Use case B — An invoice export for finance#

Finance exports issued invoices for the quarter to CSV to reconcile in their accounting tool; the job runs in the background and pings them when it's ready.

Use case C — A compliance request#

An auditor asks for an export. Compliance generates it, downloads it, and the audit log records exactly what was exported, by whom, and when.

8Glossary#

Term	Meaning
Export job	A queued request to generate a data file, with a status.
Dataset	The kind of data being exported (clients, invoices, etc.).
Scoped to requester	The export contains only records the requester may see.
Classification-based storage	Encryption tier applied to the output file based on sensitivity.

This document describes the Export Centre as currently built: background PDF/Excel/CSV exports of core datasets, generated under the requester's access scope, stored securely, and fully audit-logged.