Secure Share
The usual path. The recipient proves they control the mailbox with a one-time code, then opens the version you pinned. You still set expiry, revoke, and download limits.
Sharing & file requests
Send the approved files, with control over every recipient.
Choose the version, recipient, expiry and download limit. Send one file or a package. Recipients see only what you shared, and access can be revoked without changing anybody’s staff account.
A practical example
The board pack needs to reach two auditors for fourteen days.
Finance carries on working as normal. The two auditors see one thing: the version of the board pack that was approved. Each of them proves they control the mailbox the invitation went to before anything is shown. In fourteen days it stops on its own, or you end it this afternoon, without changing a single employee password.
Afterwards you can still tell the two auditors apart, still say which version they had, and still see what each of them opened and when.
Inbound collection
Ask for files without opening the workspace.
Sometimes you need a document from someone outside: a supplier, a candidate, a client’s accountant. A file request gives them a way to send it straight into the right folder, and nothing else. They get no view of your workspace and no account. They prove their mailbox before uploading, the request expires, and you always know who you asked, where it was going to land, and when the door closed.
How a share can leave
Secure by default. Direct when your organisation allows it.
Direct Download
An optional organisation setting for when a one-time code is the wrong fit. Anyone with the link can download (with tighter limits) and only if your administrators turn that lane on.
Watermark, your call
Public downloads are watermarked by default so a leaked copy still points back to the share. Your organisation can allow unmarked shares when the work requires it. Staff downloads inside Casewelt stay unmarked.
Multi-file packages
One controlled delivery for the whole pack.
Select between two and fifty files and send one link with one recipient check and one expiry. Each item keeps its own download limit; when policy allows, the recipient can also take the package as a ZIP.
The package is not a shared folder. It is a fixed list of approved file versions, served through Casewelt and covered by the same revoke and audit rules as a single-file share.
Control after sending
The share remains a managed record.
Recipient identity
Secure Share checks the invited mailbox before showing content. Forwarding the link is not enough.
Approved versions
Each item is pinned to the version you selected. Later edits in the workspace do not change the delivery.
Expiry and scheduling
Set when access ends, revoke it earlier, or schedule the invitation for later.
Download limits
Organisation policy sets the default and ceiling. Packages track limits for each file.
Internal sharing
Send to a colleague or group inside the organisation without creating an external link.
Searchable history
Recipient verification, opens, downloads and revoke attempts remain available after access ends.
When you try it
- Two named recipients, two rows in audit, not one anonymous link.
- Edit the file after the share. Confirm they still have the bound version.
- Send a package and confirm that each file keeps its own download count.
- Download as the recipient: the copy is watermarked. Download as staff: it is not.
- Revoke, then try the link again. The attempt is refused and recorded.
- Send a file request into one folder and confirm the uploader sees nothing else.
See the flow
Try it with a share you actually need to send.
Bring a real recipient, a document where the version matters, and a deadline. We will walk the whole path with you.