Use cases
Board packs, holds, signatures, inbound files: the afternoons Casewelt is built for.
Each of them gets the version you approved, and nothing else. In two weeks it stops. If it needs to stop sooner, you end it without changing a staff password.
What to check: that you can tell the two auditors apart, that they are pinned to the version you meant, that ending their access leaves your own people untouched, and that “who opened version 3?” still has an answer after the share has gone.
Explore secure sharing →They keep the access they legitimately need. The riskier action (sending it outside) is refused on the same file, for the same person.
What to check: read allowed, external share refused, and a refusal that clearly says “policy said no” rather than leaving the director wondering whether their login is broken.
Explore policy →You answer it that afternoon, from the record: the share being made, each recipient proving who they were, every time it was opened, the moment it was revoked, and anyone who tried afterwards.
What to check: that staff and outside recipients are distinguishable, that events come back in order, and that an attempt made after revocation is recorded as refused.
Explore auditability →The label and the retention period are already on the file. You add a hold, and from that moment deletion simply does not work (not for anyone, not by accident) until someone entitled to lift it does so deliberately.
What to check: the hold visible on the file itself, a real delete attempt refused with the reason named, and a record of that refusal afterwards.
Explore governance →You send an envelope from the file you already hold. The signer never sees the workspace. The completed document files next to the draft, and usage shows the signature was spent.
What to check: the bound version, the public ceremony, the new version after signing, and a create that fails cleanly when the monthly allowance is used up.
Explore signatures →You issue a file request into one folder. They prove the mailbox, upload, and the door closes. Quota still applies. You know who you asked.
What to check: no workspace navigation for the supplier, expiry, and the file landing where you intended.
Explore inbound requests →Personal is the shared portal, one user, administration in the menu. Recipients are still named. Firm SSO and legal hold wait until there is a firm.
What to check: no organisation slug in the address, no second admin site, and a clear line when you later join a Casewelt organisation.
Explore Personal →A script times out and tries again, as scripts do. You should end up with one folder, and no mysterious duplicate for someone to clean up next quarter.
What to check: the retry returning the original folder rather than making a second one, no doubled-up history, and errors that tell your developers whether it was bad input, a policy refusal or a genuine conflict.
Explore the API →A channel credential creates the customer’s organisation. It cannot then list their files. Their own API user does the daily work.
What to check: create succeeds, a second create does not invent a twin firm, and a files call with the channel token is refused.
Explore selling Casewelt →Where your content lives is a decision your organisation made, not something that follows whoever happens to be travelling this week. A write that would break that rule is stopped and reported.
What to check: the write actually fails rather than succeeding somewhere else, your administrators and your developers both see why, and moving region stays a deliberate decision someone signs off.
Explore regional control →Your workflow
Tell us the workflow you currently handle with a spreadsheet, a shared mailbox and a bit of hope. We will turn it into a walkthrough and be straight with you about what Casewelt does and does not solve.
