Crove Docs
Crove Docs
Crove Documentation

Getting Started

IntroductionQuick StartKey Concepts

Templates

Templates OverviewTemplate EditorVariablesExpressionsForm Builder

Documents

Documents OverviewCreating DocumentsFilling DocumentsE-SignaturesPDF Generation

API Reference

API OverviewAuthenticationTemplates APIDocuments APIRate Limits

Webhooks

Webhooks OverviewOutgoing WebhooksIncoming WebhooksWebhook Events

Integrations

Integrations OverviewZapier IntegrationAPI Keys

Account & Billing

Account OverviewTeam ManagementBilling & PlansWorkspace Settings

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

  1. Open your template in the editor
  2. Add a Signature variable where you want the signature to appear
  3. Assign the variable to a role (e.g., "Client")
  4. 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 Rep

Signing workflow

1. OTP verification

Before signing, the recipient verifies their identity via a one-time password (OTP):

  1. The system sends a 6-digit OTP to the signer's email
  2. The signer enters the OTP on the signing page
  3. Once verified, a signing session is created (valid for 10 minutes)
  4. If the session expires, a new OTP can be requested

2. Capture signature

After OTP verification:

  1. The signer chooses their preferred method (draw, type, or upload)
  2. They create their signature
  3. They review the consent statement
  4. 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:

  1. Set signing order in the document settings (Order 1, 2, 3...)
  2. Only the current signer receives an invitation
  3. When they complete signing, the next signer is automatically notified
  4. 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 + sign

Parallel signing

All signers receive invitations simultaneously:

  1. Set all respondents to the same order (or Order 0)
  2. Everyone can sign at their own pace
  3. 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:

FieldDescription
Signer emailWho signed
Signature typeDraw, type, or upload
OTP verifiedWhether identity was verified
Consent givenExplicit consent flag
TimestampExact date and time (UTC)
IP addressSigner's IP address
User agentBrowser 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?

  1. Intent to sign — The signer explicitly clicks "Sign" after reviewing
  2. Consent — A clear consent statement is presented and recorded
  3. Identity verification — OTP verification links the signature to an email address
  4. Audit trail — Complete record of who, when, where, and how
  5. Tamper evidence — Signatures and documents are stored securely
  6. Record retention — All data is preserved and accessible

Best practices

  1. Always enable OTP — It provides strong identity verification
  2. Use sequential signing — For documents that require review before approval
  3. Add a consent clause — Include a paragraph above the signature stating what the signer agrees to
  4. Download audit trails — Keep a copy of the audit trail PDF alongside the signed document
  5. Set clear roles — Make sure each signer knows exactly which fields they're responsible for

Filling Documents

How recipients fill forms and submit responses in Crove documents.

PDF Generation

Generate pixel-perfect PDFs from your Crove documents with custom fonts, branding, and formatting.

On this page

E-SignaturesSignature methodsDrawTypeUploadAdding signatures to templatesSigning workflow1. OTP verification2. Capture signature3. Record and storeMulti-party signingSequential signingParallel signingSignature declineAudit trailLegal complianceWhat makes a Crove signature legally binding?Best practices