Sign
Consent and field evidence
E-Signature
Send the document. Keep the evidence.
Prepare protected documents, authenticate signers, capture consent and signatures, and retain the completed PDF with its evidence.
- 01Template
Published document and signer fields
- 02Request
Invitation and authentication policy
- 03Sign
Consent and field evidence
- 04Finalize
Signed PDF and evidence manifest
Give coordinators and signers one clear path.
The coordinator controls the request. Each recipient sees only the document, checks, and fields assigned to them.
Published template or prepared PDF
Frozen signer order
- 01Published template or prepared PDF
- 02Frozen signer order
- 03Email invitation
- 04Expiry and authentication policy
One request, from protected source to signed result.
Nexia keeps the document revision, signer sequence, authentication policy, consent, signature fields, and final evidence on one durable lifecycle.
- 01
Prepare the document
Start from a published template or prepared source and freeze the document revision used by the request.
- 02
Authenticate each signer
Apply the request's frozen authentication policy before the recipient can enter the signing session.
- 03
Record consent and fields
Keep consent, signer identity, and each completed signature field connected to the same request.
- 04
Finalize protected evidence
Protect the completed PDF, evidence manifest, and checksums as terminal artifacts.
The signature returns to the work that required it.
E-Signature is Platform-owned infrastructure. Apps keep the business record, and Business Process may wait for a terminal outcome without sharing models or files.
The App owns the business record
An employment contract or another domain record stays with its App, including the action that starts signing.
The Platform owns the signature request
The Platform freezes the document revision, participants, authentication, consent, field evidence, artifacts, and request lifecycle.
The outcome advances the next work
The owning App reauthorizes before applying the outcome, while Business Process can wait on the same terminal result.
E-Approval decides. E-Signature records the signature.
E-Approval routes an accountable business decision. E-Signature authenticates signers, records consent, and protects the completed document and evidence.
Questions teams ask before the first request.
Keep the product boundary and retained evidence clear before moving a document into E-Signature.
Is E-Signature the same as E-Approval?
No. E-Approval records an accountable business decision. E-Signature authenticates recipients, captures consent and signature fields, and protects the completed document and evidence.
What remains after signing?
Nexia retains the completed PDF, evidence manifest, checksums, consent snapshot, request lifecycle, and governed retention state on private product storage.
How does a recipient prove identity?
The invitation creates a tenant-bound session. A request can require email OTP or a request password before consent or any signature field action.
Can signing continue a Business Process?
Yes. Business Process can optionally wait for a completed, declined, expired, cancelled, or failed result and advance exactly one outcome branch.
