Reporting & Analytics overview
Reporting combines cross-pillar materialized data into dashboards, reusable report templates, report runs, schedules, AI-query APIs, insights, and browser-side DuckDB exploration.
The current web application has uneven route maturity. The dashboard, report catalog/templates/runs, and Data Explorer call Reporting API. AI Analyst, Saved Views, Schedules, Exports, and Settings are fixture or local-state screens and must not be treated as production workflows.
The Reporting API uses internal plan labels free, pro, team, and enterprise. These are resolved by the shared AI plan-tier service; the web UI must not infer a direct customer-tier mapping. Limits govern rows, timeout, schedules, dashboards, templates, Ask InBlack, DuckDB, and cross-organization access.
The shell currently passes a fixed display user to shared navigation rather than resolving the signed-in principal in app.tsx. Keep Reporting documentation available for review, but treat publication of user-specific account behavior as dependent on completing that auth integration.