Walkthrough
Follow one file through the decisions that matter.
Seven decisions on one board pack: create, share, a policy refusal, audit, hold, signature, then the API. The workspace shown is a Casewelt demonstration tenant.
Create the board pack
The document goes into a governed folder and picks up a version number of its own. Comments stay attached to the version they were made against. Someone outside can be asked to send a file into the same folder without seeing anything else in the workspace. And at no point is anyone handed a raw storage link. Files are always served by Casewelt.
Ask to see: a specific version you can point at, rather than a vague “latest copy”.
Share with two auditors
Create a share for two named people that expires on a set date, pinned to the version you approved. If the delivery includes several documents, send them as one fixed package with individual download limits and an optional ZIP.
Ask to see: the two recipients recorded separately, mailbox verification before anything is shown, and access ending without a staff password change.
Sharing & file requests →Prove that signing in is not the whole story
The same person, properly signed in, can be allowed to read a sensitive file and still be refused when they try to send it outside.
Ask to see: the refusal recorded as a policy decision, clearly different from “your login failed”.
Policy controls →Create external share
Policy does not permit this file to be shared externally. The session remains valid.
Answer the audit question
The share being created, the recipient being verified, the file being opened, the share being revoked. All of it still answerable months later, long after the share itself has expired.
Ask to see: who did it, to which file and version, and what the answer was, including someone trying again after access was taken away.
Auditability →
Opened v3External recipient · ALLOW
Share createdTwo named recipients
Open after revokeDENIED
Day-to-day numbers (storage, inbound uploads, mail) live on the Reports dashboard instead, so routine questions never touch the evidence record. Usage reports →
Apply legal hold
A dispute starts. The document is frozen: people who were allowed to read it can carry on reading it, but nobody can remove it, deliberately or by accident.
“Contract term + 7 years” on the card is your retention rule for that record: how long your organisation must keep it. Casewelt enforces it while you have an active subscription; it is not a promise that we host the file for free after you stop paying.
Ask to see: the hold visible on the file itself, and a real attempt to delete it being refused.
Content governance →- Classification
- Confidential
- Retention
- Contract term + 7 years
- Legal hold
- On
- Delete
- BLOCKED
Send it for signature
The same board pack becomes an envelope, bound to version 3. The signer opens a ceremony, not your folders. The completed file returns as version 4. Usage shows a standard signature was spent.
Ask to see: the bound version, no workspace navigation for the signer, and the signed copy sitting next to the draft.
Signatures →Automate without nasty surprises
A script times out and retries. You should end up with one folder, not two. And if a write would land the file in the wrong region, it should stop and say so rather than quietly move it somewhere you did not agree to.
File API → Region →POST /v1/workspaces/{ws}/folders
Idempotency-Key: 8f2a…
200 same object on retry
placement conflict → REJECTEDWhat a good demo proves
Anyone can demo the happy path.
Insist on the awkward moments: access ending, an action being refused, a deletion being blocked, a duplicate that never happens, a write that stops at a regional boundary. You learn more from those five minutes than from a tour of every menu in the product.
They also give your security and operations people something specific to push on. What was written down? Which identifier ties the events together? Who is allowed to change the rule? And what does someone actually do next when they hit the wall?
Your documents
Run this with your own documents.
Swap our board pack and supplier agreement for something real from your organisation, and we will point the evaluation at the controls you actually care about.