Product documentation

The whole platform, documented.

Plain-language, capability-level documentation of every module in Lumos — what it does, what users see and do, and where the boundaries are. Written from the actual codebase for high-touch, relationship-led businesses.

Updated 2026-06-2314 modulesWritten from the codebase
The system

One request becomes an event, a vendor brief, an invoice, and a payment — without ever leaving the system.

Everyone lands on the Dashboard. From there, work moves through four hand-offs — searchable, reportable, exportable, and notified throughout, governed by Access Control and Settings on the shared Platform.

01
Serve

Every job starts from a client and stays traceable to one.

02
Source

Suppliers earn their scores from delivered work — never from a form.

03
Collect

The full quote-to-cash path, settled by signed webhooks.

04
Retain

One governed home for everything sensitive, linked to its entities.

01
Serve
ClientsRequestsEvents

Every job starts from a client and stays traceable to one.

02
Source
RequestsVendorsEvents

Suppliers earn their scores from delivered work — never from a form.

03
Collect
ClientsInvoicesPayments

The full quote-to-cash path, settled by signed webhooks.

04
Retain
FilesDocument Vault

One governed home for everything sensitive, linked to its entities.

The modules

Fourteen modules, one product.

Grouped the way the business thinks about them. Every doc follows the same shape: one sentence, who it's for, the core idea, then screen-by-screen depth.

Themes

What runs through every module.

Lumos's consistent selling points — true across the product, not module-specific.

01

Compliance-first

GDPR lawful basis, immutable consent and audit records, KYC/AML, classification levels, and encrypted sensitive fields are built into the foundation — not bolted on.

02

Earned, not entered

Key numbers — vendor ratings, engagement counts — are derived from real activity, so they can't be fudged.

03

Locked when it counts

Issued invoices, recorded consents, performance scores, and audit logs are immutable. Corrections happen through proper, traceable mechanisms.

04

Least privilege

Granular permissions plus per-user data scoping mean people see exactly what their role allows — enforced on both backend and frontend.

05

One coherent system

Shared People records, global search, entity pickers, and a consistent UI shell make the modules feel like one product.

Docs read. Now see it run.

The customer-facing view of these modules lives in Features — or book a private demo and watch them work on real requests, vendors, and reporting.