Reporting

See how the organisation is using Casewelt.

Administrators get a usage dashboard covering storage growth, external shares, signature envelopes, files sent in through file requests, outbound mail and webhook deliveries. When someone else needs the numbers, take them away as a written PDF summary, a CSV for your spreadsheet, or JSON for another system.

Portal charts for recent activity, storage used and signature mix.
Activity, storage and signature mix sit on the portal. Organisation usage reports and the audit chain are separate screens.

What the dashboard measures

What you can actually see.

Storage

How much you are storing and how quickly it is growing, for each workspace and for the organisation as a whole, day by day.

Sharing and signatures

How many external shares were created, what signature work is open or finished, and whether the notification emails actually reached people.

Inbound work

Files sent in through file requests, holds placed, comments raised, and whether your webhooks were delivered successfully.

Capacity

Your storage allowance, your seats and the work currently open, so you can see pressure building before an upload starts failing.

Your organisation only

Reports are built inside your organisation’s own boundary. There is no shortcut that lets one customer’s figures appear in another customer’s report.

Separate from the audit record

Reports are for running the service day to day. The audit record stays the evidence trail, and reporting never rewrites or replaces it.

Export

Take a document away. Leave the console on screen.

The PDF is a written summary: the current snapshot, what is still open, and the totals for the range you picked. It is meant to go in front of a board or an auditor, not to be a screenshot of a dashboard. CSV opens in a spreadsheet. JSON is the same data the API returns, so another system can pick it up without anyone retyping figures.

If you need the underlying rows rather than the summary, storage and activity detail can be exported as a table too. Assistance credits, signature allowances and seats sit next to storage so you see pressure before an upload or an envelope fails.

When you try it

  1. Open reports and audit side by side. They must not be the same screen with a different title.
  2. Export PDF, open it without the product running, and check the period and the organisation name.
  3. Ask whether grouping live audit events is how the dashboard is built. It is not.
How audit differs → Usage on the API →

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