> ## Documentation Index > Fetch the complete documentation index at: https://docs.jaantonio.com/llms.txt > Use this file to discover all available pages before exploring further. # Analytics overview > Org-scoped reporting Postgres for SQL, Power BI, and long-term shipment visibility. Analytics is Lambda’s reporting module. CargoWise shipment data lands in a read-only Postgres schema named `reporting`, which you query with SQL, Power BI, or any Postgres client — for dashboards, recurring reports, and historical analysis. Your login only sees your organization’s rows. Day-to-day reporting does not need a custom API. ## What you get * Long-term storage scoped to your organization * A stable schema named `reporting` * Curated business tables for everyday questions * A discovery path for fields that are not curated columns yet * Credentials you create and revoke in Lambda (up to two active) ## What this is not Analytics does not invent curated columns. If CargoWise is not sending a value on the Analytics feed, that value will not appear in `reporting` until the feed includes it. ## Who this is for Most report consumers never open SQL. Someone on your team connects Power BI once, publishes a model, and everyone else uses reports. People who already use a database client can connect with the same credentials and run read-only queries against `reporting`. Admins create and revoke credentials on the **Analytics** page in the workspace sidebar. ## Start here Follow the path from CargoWise into reporting. Create credentials and open Power BI or any Postgres client. Everyday tables: reporting.shipments and reporting.quotes. Full list of views, columns, and known gaps.