Reporting

See how the organisation is using the platform — without scanning the audit chain.

Organisation administrators get a usage dashboard: storage over time, shares, signatures, inbound file-request uploads, outbound mail and webhooks. Operators see the same facts rolled up per tenant under that organisation’s own row-level security. Export is a written summary (PDF), a spreadsheet (CSV) or machine JSON — not a printout of the screen.

What the dashboard measures

Facts from product tables, snapshotted for the range you choose.

Storage

Daily organisation and workspace snapshots of bytes and file counts. Today is captured when the dashboard opens.

Sharing and signatures

Shares created, envelope mix, and mail sent or failed on share deliveries.

Inbound work

File-request uploads, holds, comments and webhook delivery outcomes for the selected window.

Capacity

Organisation cap, seats and open work — so pressure is visible before uploads fail.

Platform view

Operators loop tenants with a GUC per organisation. There is no cross-tenant SQL session and no BYPASSRLS.

Not the audit chain

Dashboards do not GROUP BY live audit events. The hash-chain remains the evidence surface; reports are operational.

Export

Take a document away. Leave the console on screen.

PDF is a titled summary: snapshot, open work, range totals, workspaces or tenants. CSV is for Excel. JSON is the same payload the API already returns. Organisation admins export their tenant; platform operators export the fleet roll-up.

Catalog queries (storage or activity grain) can be exported as a table. Ad-hoc SQL stays behind a guard: SELECT or WITH only, tenant GUC still applies.

How audit differs →

Evaluate reporting

Walk through a real usage question.

Storage pressure, inbound uploads, mail failures or open envelopes — answered from the product, then exported.

Request a demo