Request a demo
Menu

Walkthrough

Follow one file through the decisions that matter.

The live development cell uses a governed workspace named Secure Room 1. The steps below are the control points a demo should prove. They are not a named customer story.

Create the board pack

The file exists as a known object and version in a governed workspace. Staff work under organisation membership and policy. Bytes never leave Casewelt servers as a customer-facing object-storage URL. Comments stay on that version; inbound file requests can land objects in the same folder without exposing the rest of the workspace.

Look for a stable object and version identity, rather than an ambiguous “latest copy”.

PDFA governed PDFSecure Room 1 · GOVERNED · version boundGoverned

Walkthrough of control points. The screenshot is the live Files surface (tokens removed).

Live Files list in Secure Room 1: search, Icons/List/Grid switch, folder actions and Upload, with size, added date and a Hold badge on one file.

Share with two auditors

Create a time-bound external share for two named recipients. Bind it to the approved version so a later internal edit does not silently change what they receive.

Look for distinguishable recipients, verification before bytes, and revoke without touching staff credentials.

Secure sharing →

Prove that policy is more than login

The same valid user can be allowed to read while being denied create-share on a more sensitive file.

Look for a deny labelled as policy, distinct from an authentication error.

Policy controls →
DENIED

Create external share

Policy does not permit this file to be shared externally. The session remains valid.

Query audit evidence

Share creation, recipient verification, open, revoke. The record remains useful after the share has ended.

Look for actor, object, version and outcome — including a later denied attempt. The live Audit table shows login names in Who when the membership has stored preferred_username.

Auditability →
Live organisation-admin Audit: hash-chain tip, Who column with login names, tenant-scoped events.

Opened v3External recipient · ALLOW

Share createdTwo named recipients

Open after revokeDENIED

Apply legal hold

Classification and retention stay on the object. Hold blocks deletion while the file remains usable under policy.

Look for hold as object state and a deletion that fails closed.

Content governance →
PDF
Supplier agreementHold on · delete blocked
Classification
Confidential
Retention
Contract term + 7 years
Legal hold
On
Delete
BLOCKED

Automate without silent relocation

Retry an idempotent API create without duplicates. A regional placement conflict stops the write instead of quietly moving the object.

API → Region →
POST /v1/files
Idempotency-Key: 8f2a…

200 same object on retry

placement conflict → REJECTED

What a good demo proves

Success is useful. Safe failure is more revealing.

Ask to see the moments where access ends, policy denies an action, deletion is blocked, a retry is deduplicated or a placement conflict is surfaced. Those behaviours expose the product’s control model far better than a tour of navigation labels.

They also create concrete questions for security and operations teams: what is logged, which identifier links the events, who can change the policy and what recovery path exists after the failure.

Your objects

Use this walkthrough with your own objects.

We can replace the board pack and supplier agreement with a workflow from your organisation and focus the evaluation on the controls you actually need.

Request a demo