Documents & Collaboration · Signatures
E-signature with an evidence chain — signed documents freeze; the work forks forward.
Included with EdgeLex
The problem
Most e-signature tools can tell you a document was signed. Few can prove which version was executed, under what policy, and that nothing changed afterward.
Capabilities
What it does
Signing sessions
Field placement, filling, and validation for each signer, tied to a specific document version.
Eligibility that fails closed
Signer eligibility is checked before signing is offered — if the system can't establish a signer is eligible, it refuses rather than assumes.
Freeze-on-signature
Once signed, the version freezes permanently. Further edits fork to a new document — the executed instrument can never drift.
The evidence chain
Signer consent, the policy applied, and the committed version are recorded as a signature evidence chain attached to the document.
Signature Studio
Per-identity signature management — each signing identity carries its own studio-configured signature.
Works where sharing happens
Signature routing runs inside Data Rooms too: signature-required documents block package publication until they're executed.
In your control
The executed version is frozen, the evidence chain is attached, and both live in your DMS — not a vendor's archive.
Related
Works with
EdgeDocs
Native document drafting and a full DMS: versioning, redlines, clause library, e-signature with an evidence trail, and freeze-on-signature.
Data Rooms
Version-locked documents, verified external participants, per-room permission policy, an immutable activity ledger, and close/archive controls — native to the matter.
Matters
Matter lifecycle, conflict checks, risk scoring, related-proceeding tracking, and a matter workspace the AI understands.
See EdgeLex on your own terms.
We'll walk through self-hosting, model control, and your firm's workflows.