E-Signatures
Collect legally binding electronic signatures with multi-party workflows, OTP verification, and audit trails.
E-Signatures
Crove provides built-in electronic signatures that are legally compliant with the ESIGN Act, UETA, and eIDAS regulations. Collect signatures from one or multiple parties with full audit trails.
Signature methods
Recipients can sign using three methods:
Draw
A digital canvas where the signer draws their signature using a mouse, trackpad, or touchscreen. This produces the most personal and traditional-looking signatures.
Type
The signer types their name, which is rendered in a signature-style font. Quick and convenient for simple signing scenarios.
Upload
The signer uploads an image of their handwritten signature. Useful for signers who have a pre-scanned signature image.
Adding signatures to templates
- Open your template in the editor
- Add a Signature variable where you want the signature to appear
- Assign the variable to a role (e.g., "Client")
- The form builder automatically creates a signature field
You can add multiple signature variables for multi-party signing:
Signature fields:
- {{Client Signature}} → Role: Client
- {{Witness Signature}} → Role: Witness
- {{Company Signature}} → Role: Company RepSigning workflow
1. OTP verification
Before signing, the recipient verifies their identity via a one-time password (OTP):
- The system sends a 6-digit OTP to the signer's email
- The signer enters the OTP on the signing page
- Once verified, a signing session is created (valid for 10 minutes)
- If the session expires, a new OTP can be requested
2. Capture signature
After OTP verification:
- The signer chooses their preferred method (draw, type, or upload)
- They create their signature
- They review the consent statement
- They click Sign to confirm
3. Record and store
When a signature is submitted, Crove records:
- Signature type (draw, type, or upload)
- Signature data (image)
- Typed name (if typed method)
- Consent flag and timestamp
- IP address of the signer
- User agent (browser/device info)
Multi-party signing
Sequential signing
Recipients sign in a defined order:
- Set signing order in the document settings (Order 1, 2, 3...)
- Only the current signer receives an invitation
- When they complete signing, the next signer is automatically notified
- The document is marked complete when all signers have finished
Example: Employment agreement
Order 1: Employee → Fill personal details + sign
Order 2: Manager → Review + sign
Order 3: HR Director → Final approval + signParallel signing
All signers receive invitations simultaneously:
- Set all respondents to the same order (or Order 0)
- Everyone can sign at their own pace
- The document completes when all have signed
Signature decline
Recipients can decline to sign a document. When declined:
- The document owner is notified
- The decline is recorded in the audit trail
- The document status reflects the declined signature
Audit trail
Every signature generates a comprehensive audit trail entry:
| Field | Description |
|---|---|
| Signer email | Who signed |
| Signature type | Draw, type, or upload |
| OTP verified | Whether identity was verified |
| Consent given | Explicit consent flag |
| Timestamp | Exact date and time (UTC) |
| IP address | Signer's IP address |
| User agent | Browser and device information |
The audit trail can be downloaded as a separate PDF for compliance and legal records.
Legal compliance
Crove e-signatures comply with:
- ESIGN Act (US) — Electronic Signatures in Global and National Commerce Act
- UETA (US) — Uniform Electronic Transactions Act
- eIDAS (EU) — Electronic Identification, Authentication and Trust Services
What makes a Crove signature legally binding?
- Intent to sign — The signer explicitly clicks "Sign" after reviewing
- Consent — A clear consent statement is presented and recorded
- Identity verification — OTP verification links the signature to an email address
- Audit trail — Complete record of who, when, where, and how
- Tamper evidence — Signatures and documents are stored securely
- Record retention — All data is preserved and accessible
Best practices
- Always enable OTP — It provides strong identity verification
- Use sequential signing — For documents that require review before approval
- Add a consent clause — Include a paragraph above the signature stating what the signer agrees to
- Download audit trails — Keep a copy of the audit trail PDF alongside the signed document
- Set clear roles — Make sure each signer knows exactly which fields they're responsible for