Standard electronic signature
For internal and commercial paperwork. Monthly allowances scale with paid seats on organisation plans; Personal has a fixed monthly allowance.
Signatures
The signature stays on the same file you already govern.
You do not export a PDF to a separate signing website and hope the signed copy finds its way home. In Casewelt a signature envelope is made from a version you already hold. Signers prove who they are. The finished file comes back as a new version, with a record of who signed and when.
How it feels
Prepare, send, wait, file. All in one place.
01
Pick the version
The envelope is bound to a specific file version. An internal edit tomorrow does not silently become what the signer sees.
02
Name the signers
Each signer is a person with a mailbox. They do not get a staff account. They open a ceremony built for signing, not for browsing your workspace.
03
They sign
Standard electronic signatures on Personal, Core and Business. EU Qualified signatures where your plan includes them — for the documents that need that bar.
04
It files itself
The completed document returns as a new version. The dashboard shows what is waiting on you. The audit record already knows.
EU Qualified
When the document needs a qualified signature under EU rules, Casewelt can run that ceremony. It is a separate allowance on Core and Business, and a contracted quantity on Enterprise.
Your branding on the ceremony
Signers see your organisation’s appearance, not a generic third-party page. They still never see your folders.
Waiting on you
The portal dashboard lists envelopes that need your signature. You do not hunt through mail to find out what is outstanding.
Policy still applies
If this file must not leave, or this person must not send it, the envelope is refused like any other outbound action — and recorded as a policy decision.
Visible in usage
Administrators see how many standard and qualified signatures the organisation has used this month, next to storage and shares.
Why it lives here
A signed copy that wandered off is not a record.
If the signed PDF lives in someone’s downloads folder, you have lost the version history, the classification, the retention rule and the answer to “who saw the unsigned draft?”. Casewelt keeps the unsigned and signed versions in the same governed file.
Developers create envelopes on the same API as files and shares. Recipients still use the public signing door — your automation token never becomes their login.
An afternoon
The NDA cannot live in three inboxes.
You already have the draft as version 6 in the matter folder. You make an envelope from that version — not from a PDF you exported last week. Two signers, two mailboxes. They open a page that looks like your organisation. They do not get a folder tree.
The first signer finishes in the morning. The dashboard shows one waiting. The second finishes after lunch. Version 7 appears beside version 6: the completed document, still classified, still under the same retention rule, still in the same file.
If this file must not leave, the envelope never goes out. If the monthly allowance is spent, the create fails with a usage reason — it does not send a half-signed ceremony and hope someone notices.
In a walkthrough
- Name the version on the envelope. Edit the file afterwards. Confirm the signer still has the bound version.
- Complete the ceremony and find the signed copy as a new version, not as an attachment in mail.
- Ask what happens when the allowance is used up. You want a refusal, not silence.
- Confirm a signer cannot walk into the workspace from the ceremony.
Try a real envelope
Bring a document you actually need signed.
We will bind a version, send it to a named signer, and show you the completed file sitting next to the draft.