Work in folders
Workspaces, versions, search, comments, tasks, a calendar that knows when a share or signature is due, and Office files you can edit in the browser.
Daily work →Secure content management for regulated organisations
Keep sensitive content useful.
Keep control of what happens to it.
Your team can edit a file, send the approved version, collect documents back and request signatures from the same workspace. Recipient access, retention and audit stay attached to the work, ready when somebody needs a clear answer.
- Named external recipients
- Inbound file requests
- Signatures
- Browser editing
- Classification & retention
- Searchable audit
UK company Casewelt is built and run by Sial Networks Limited
Your own sign-in Single sign-on through your identity provider, on Business and above
API & signed webhooks Documented automation, on Business and above
Cookie policy Necessary cookies where needed: explained, not hidden
Explore Casewelt
Choose the view that fits your job.
Follow a working example, understand the platform, or go straight to the API.
See it in action
Follow one file through share, policy, signature and audit: in the order a working week usually goes.
Product walkthrough →Understand the platform
How storage, sharing, retention and evidence sit next to the folders your team already understands.
Platform overview →Read the API
Authentication, upload, shares, signatures and events: the same work as the console, over HTTP.
API reference →Product
Everyday file work, with the difficult decisions built in.
One workspace for staff, a focused page for recipients and a separate console for organisation controls.
Send one file or a package
Choose up to 50 files, set one expiry and send one mailbox-verified link. Recipients can download individual items or an optional ZIP.
Sharing & file requests →Ask for a file back
A supplier uploads into the right folder and sees nothing else. The request expires. Quota still applies.
Inbound requests →Get it signed
The envelope is the same file. Standard electronic signatures, and EU Qualified where the plan includes them. The signed copy files as a new version.
Signatures →Apply the organisation’s rules
Allow ordinary work, refuse an unsafe share, enforce retention and block deletion while a legal hold is active.
Governance →Answer who opened it
Search the product record. Open an investigation. Export a sealed evidence package when a screen is not enough.
Audit →Run the organisation
People, groups, roles, your sign-in, your hostname, your look, your storage or ours, mail, quotas, devices, billing.
Administration →Work independently
Personal gives one person a private workspace, file versions, controlled shares, signatures and activity history.
Personal →Ask a question of a file you may open
Assistance uses the same permission as download. Credits are visible. A blank document is still just a file.
Assistance →Plug other systems in
API users with scopes, signed events, no storage URLs. A separate credential if you sell Casewelt to your own customers.
API reference →The portal
Search, upload and inbound requests sit with the folders.
Favourites, recent files and storage sit in the same sidebar as the work. The interface can carry your organisation’s branding. Bytes always leave through Casewelt. Nobody is handed a storage link they could forward.
Governed workspaceAsk for files without opening the workspaceServed by Casewelt, never a storage link
Audit as a query
Person, file, version and outcome: answered from the system that made the decision.
A session you can end
Revoke takes effect in the product. Previously permitted work stops; the event stays in the record.
From file to evidence
The controls follow the work.
A file becomes a versioned record as soon as it enters the workspace. Sharing, retention and audit then refer to that same record.
01
Work
Create, edit and comment in a governed folder.
02
Share
Send the approved version to verified recipients.
03
Govern
Apply classification, retention and legal hold.
04
Answer
Search the record and export evidence when needed.
External collaboration
Give recipients the document, with no route into the workspace.
A Casewelt share is made out to a named person, points at the version you approved, expires on a date you set, and can be pulled back without touching anyone’s staff access. Recipients open it on a separate page. They never get an account, and they never see the rest of your workspace.
How secure sharing worksPolicy
Refusals are recorded next to the successes.
A blocked share, a delete under hold, a revoked session, a placement conflict: each is a named outcome. The person stays signed in. The audit line says why it stopped.
External share
This file is not allowed to leave the organisation, and the refusal is recorded as policy, not as a login error.
Delete under legal hold
Someone tried to remove a file under hold. The delete stops; the attempt stays visible.
Revoked session
You ended that person’s session. The next request fails immediately. They stay signed out of Casewelt until they sign in again.
Placement conflict
The write would put content in the wrong region. Casewelt stops it rather than letting it drift.
PDF
Q4 Board Pack.pdfGovernance stays on the object
- Classification
- Restricted
- Retention
- 7-year policy
- Legal hold
- Off
- Delete
- Allowed
Governance
Governance stays with the content.
Three different questions, three separate answers, all attached to the same file. Can this person do this right now? How long does this have to be kept? And is there a reason it must not be deleted today?
Lifecycle controlsWho opened this file?External recipient · v3 · ALLOW
Which policy allowed it?create-share evaluated
When was access revoked?Share ended · later open DENIED
Audit & evidence
Who opened it is a query.
Search by person, file, version and what was decided. The answer comes from the system that made the decision, so nobody has to reconstruct it from inboxes and server logs a month later.
Explore auditabilityIntegrations
Connect identity, automation and monitoring.
Use your identity provider over OIDC, call the HTTP API and verify signed webhooks. Plan availability is listed on the pricing page.
Sign-in
- Your own identity provider, over OIDC
- People keep the login they already have
Security monitoring
- Events your SIEM can consume
- Signed webhooks you can verify
Content protection
- Every file version encrypted with its own key
- Key context bound to the organisation
Automation
- Documented HTTP API
- Separate machine credentials, so scripts never borrow a person’s login
Use cases
Where teams tend to start.
Board & executive
Get the board pack to two external auditors for a fortnight, without giving them a way into anything else.
Legal
Freeze a contract the moment a dispute starts, send the same file for signature, and show later that nothing was removed while the hold was on.
One person, or a firm
Work alone on Personal, or as a team on an organisation host with SSO, roles and an API. See the scenarios →
Security architecture
Isolation, encryption, revoke, machine credentials, append-only audit.
Your organisation’s data is kept separate from every other customer’s. Each file version is encrypted with its own key. Sessions can be ended on the spot. Automation uses its own credentials. The audit record is appended, never rewritten.
Desktop & mail
Agents on the machine. Tools in the mailbox.
Casewelt Desktop keeps an approved computer matched with the portal Agents tree. Crypt seals sensitive files on device. Thunderbird and Outlook add-ins insert Secure Share and File Request into the mail you send. Installers are not on this website: sign in to your portal, then open Download.
Desktop & mail clientsDesktopLocal folder sync after machine approval
CryptSealed store on entitled plans
Mail add-insCompose-time share and file request
DownloadPortal sign-in required, not from www
Next step
See your own workflow in Casewelt.
Bring a real document and the controls around it. We will walk through access, sharing, retention and audit from start to finish.