Identity
Distinguish staff, automated systems and outside recipients.
Platform
A working home for sensitive documents.
Teams use familiar folders, versions, comments and browser editing. Casewelt adds precise controls for outside sharing, retention, administration and audit without turning daily file work into a compliance exercise.
What the platform looks like
A workspace people recognise. Controls that stay with the file.
Search, upload, inbound requests and storage sit next to the folders your team already understands. The file never leaves Casewelt as a storage link someone could forward.
Governed workspaceOpen PDF or text without downloadingServed by Casewelt, never a storage URL
Controls around the file
Each decision has a clear owner and outcome.
Identity establishes who is asking. Policy decides what they may do. Sharing, retention and audit then record the specific version and action involved.
Policy
Check the requested action against the person and file at that moment.
Sharing
Deliver one file or a fixed package to verified recipients.
Governance
Apply classification, retention and legal hold to the content.
Audit
Search the product record and export evidence when needed.
API
Automate with scoped credentials and signed events.
Workspace
Folders your team understands. Versions your auditors can point at.
Folders are for people. Version numbers are for everything that comes afterwards. When you share a document, apply a rule to it, or look it up two years later, all of those refer to a specific version you can name, never to a vague “latest copy”.
Workspaces & folders
A permanent home for ongoing work. The folders remain after the deal closes.
File versions
Every revision is kept and numbered, so you can always say exactly which one someone was shown.
Open without downloading
PDF opens read-only in the browser. Text, JSON and similar files open in a light editor when policy allows: useful when you need to check a file, not ferry a copy around.
Labels and rules
Your classification and retention rules travel with the file, ready for the next decision that needs them.
Inbound file requests
Ask someone outside for a document and have it land straight in the right folder. The link expires, and they prove their mailbox before anything is accepted.
Activity and inbox
Your team sees what changed, who commented and what arrived, without anyone having to send a chasing email.
Purpose-built access
Staff, administrators and recipients see the tools they need.
Staff work with files. Administrators manage organisation-wide settings. Outside recipients open only the delivery or signing ceremony addressed to them.
Keeping these surfaces distinct limits what each route can expose.
Staff workspaceAuthenticated work with files and folders
AdministrationOrganisation, policy and security controls
External sharingVerified, time-bound recipient access
A lasting workspace
The record remains useful after access ends.
Files stay versioned and classified after a share expires. Retention, holds and regional rules continue to apply to the workspace record.
Your team keeps the familiar folder structure while the important decisions remain available for later review.
Casewelt Desktop
A folder on your computer that stays matched with the portal.
Bind one local folder. Upload and changes sync through Casewelt, never as a storage URL you could forward. You approve each computer in the portal before sync starts. Large files show transfer progress; quarantine clears when the seal finishes.
On Business and Enterprise, Crypt keeps a sealed store on the device: plaintext only inside Casewelt, not handed to the OS as an ordinary file. Mail add-ins put Secure Share and File Request into compose. Packages download only after portal sign-in, not from this website.
Desktop syncLocal folder ↔ portal Desktop: portal is source of truth
Machine approvalApprove or exclude each computer before bytes move
CryptSealed local store on Business and Enterprise
TransferUpload and download through Casewelt: progress on the status line
Durability
Choose how resilient copies are arranged.
Writes complete on the main store first. Casewelt can then copy sealed objects to an online replica for failover and to a separate disaster archive.
Organisations using their own object storage can attach replica and disaster endpoints or choose Casewelt’s disaster vault. If no secondary copy is configured, the organisation accepts responsibility for durability and recovery.
MainPrimary write path: users wait only here
ReplicaOnline second site: failover if main does not answer
DisasterArchive copy: your endpoint, or Casewelt vault if you opt in
ClientsCasewelt moves the bytes through its gateway
Explore further
Go deeper where your work demands it.
Sharing & file requests
Verified recipients, fixed multi-file packages, expiry, revoke and controlled inbound upload.
Governance
Classification, retention, legal hold, policy decisions and regional placement.
Audit & reporting
Investigations and evidence for formal questions; usage reporting for day-to-day operations.
Desktop & mail
Approved folder sync, a sealed Crypt store and share tools in Thunderbird and Outlook.
Administration
People, roles, identity, storage, mail, quotas and organisation settings.
API & partners
Scoped automation, signed events and safe tenant provisioning for channel products.
Evaluate the platform
Use a real piece of work.
Bring the documents, people and controls involved. We will run the workflow from first upload to final record.