Reporting and exports

Reporting and export basics

Reporting help should explain what numbers mean without creating a second source of truth or fuzzy export expectations.

Who this is for: Admins evaluating reports, dashboards, and export posture.

Last reviewed 2026-04-29 · Source of truth: launch shell · Languages: en, es

Product area: reporting and exports

Owner: Reporting truth

Parity reviewer: Bilingual launch review

Retrieval-ready: Yes

Use help for explanation, then verify live system state in the actual product when that surface exists.
Escalate if a definition-sensitive question could change a financial or operational decision.

What reporting help can do

Help articles can explain definitions, report purpose, and export posture.

They should not pretend to replace the system’s canonical reported values or future reporting registry.

Exports should be described as governed handoff paths, not casual data dumps with unclear meaning.

Definition-sensitive terms should stay tied to their canonical meaning when reporting help is written.

If the question could affect a real financial or reporting decision, escalate instead of relying on fuzzy interpretation.