Feature Request: Integrated e-Signature Field with QR Code Capture for Legal & Field Operations

[Sohail2949000]

Is your feature request related to a problem? Please describe.

Yes, it is related to two significant workflow and cost problems.

1. Cost & Workflow Silos for e-Signatures: We are forced to use and pay for a separate e-signature software (like DocuSign or Adobe Sign) to collect legally valid signatures from clients and partners. This requires constantly exporting data from Teable, sending it out, managing another platform, and then manually updating records back in Teable. It's expensive, slow, and creates a disconnected workflow.

2. Inefficient Field Data Collection: For operations like delivery confirmations or site inspections, we need to capture signatures and data from field staff (e.g., drivers). The current process is clunky—using paper, separate mobile apps, or insecure methods like emailing photos of signatures. We lack a way to directly link a secure, auditable signature to a specific Teable record from a field agent's device.

Describe the solution you'd like

We would like Teable to introduce a native "e-Signature" field type with two powerful modes:

Mode 1: In-App Signing

• A field where a signer can draw, type, or upload their signature directly within a Teable record (shared via a view or form).
• Critical Feature: It must automatically generate a legally robust audit trail stored with the record, including:
  • The signature image/data.
  • Timestamp (date & time).
  • Signer's IP address.
  • Device/browser metadata.
  • Email/identity verification if the signer is a Teable user or accesses via a secure link.

Mode 2: QR Code Field Signing (for field staff)

• The ability to generate a unique, secure QR code for a specific record (e.g., a delivery order).
• A field agent (like a driver) scans this QR code with their phone's camera. This opens a simple, mobile-optimized signing page in their browser—no app install required.
• On this page, they can sign. Upon signing, the system captures:
  • Their signature.
  • Device GPS coordinates (with permission).
  • Device timestamp & IP address.
  • This data is automatically saved back to the original Teable record, and can trigger field updates (e.g., setting a Status field to "Delivered & Signed").

Describe alternatives you've considered

• Using Separate e-Signature Software: This is our current, costly alternative. It creates workflow fragmentation and additional subscription costs.
• Using a Generic "Attachment" Field: Asking clients to print, sign, scan, and email a document back, then uploading it. This is not legally robust, is slow, and provides no audit trail.
• Using Other Database Platforms with Integrations: Some platforms have Zapier/Make integrations with e-sign services. These are complex to set up, remain costly, and still don't offer the seamless, direct capture from field staff via QR code that we envision.

Additional context

• This feature would be a game-changer for SMBs and self-hosted enterprise users, eliminating a major software category expense (e-signature subscriptions) by bringing it into the Teable ecosystem.
• The QR code field signing is particularly innovative for logistics, service businesses, and any operation with mobile staff. It turns any smartphone into a secure data capture device directly for Teable.
• The legal weight of an e-signature hinges on the audit trail (proof of who, when, and from where). Building this in natively would make Teable records themselves legally authoritative documents.
• Combining this with the previously requested "Bulk Export with Attachments" feature would make Teable an unparalleled platform for managing complete document lifecycles—from creation and signing to archiving.