Skip to main content
Stay up to date with the latest changes to Firma. This page documents platform-wide updates including new features, UI improvements, and expanded language support.

March 26, 2026

MCP Integration for AI Assistants

You can now connect Firma to AI assistants like Claude using the Model Context Protocol (MCP). Once connected, you can manage templates, create and send signing requests, configure workspaces, and more through natural language conversations.
  • Works with Claude Code, Claude Desktop, and Claude.ai
  • Authenticate with your existing API key or via OAuth sign-in
  • Full access to workspaces, templates, signing requests, webhooks, and company settings
  • Switch between workspaces during a conversation
  • Each tool call maps to one API request, subject to standard rate limits
See the MCP Integration guide for setup instructions and the API changelog for details.

March 19, 2026

File Upload Fields

A new file field type lets you collect file attachments from signers. Add a file upload field to any template or signing request, and signers can upload documents directly during the signing flow.
  • Accepts images (JPG, PNG) and/or PDF files depending on your configuration
  • Files are validated by content (magic bytes), not just file extension
  • Maximum file size of 10MB per upload
  • Configure accepted file types per field: images only, PDF only, or both
  • Upload limit warnings shown in the template editor
See the API changelog for the FileFormatRules schema and field configuration details.

Anchor Tags

Automatically place fields on documents using text markers. Embed anchor strings like {{SIGN_HERE}} or {{DATE}} in your PDFs, and Firma will find them and convert them into positioned fields during signing request creation. The anchor text is removed from the document after processing.
  • Up to 100 anchor tags per signing request
  • Control offset, size, and matching behavior per anchor
  • Target specific occurrences or all matches of an anchor string
  • Optionally skip missing anchors without errors
  • Works alongside manually positioned fields
See the API changelog for the full AnchorTag schema and properties.

Field Background Colors

Fields now support a background color property. Set a hex color (e.g., #FFFDE7) on any field to visually highlight it — useful for drawing attention to fields that need signer action or distinguishing field groups.

March 10, 2026

Conditional Fields

Fields on documents can now be conditionally visible and conditionally required based on what a signer enters in other fields. For example, a “Spouse Name” field can appear only when a signer checks “Married,” or an address block becomes required only when “Ship to different address” is selected. Conditions use a flexible nested logic system (AND/OR groups) and evaluate in real-time as signers fill out the document. All conditions are enforced server-side on submission, so they can’t be bypassed. Available in the template editor, signing request editor, embedded editors, and the full REST API. See the API changelog for schema details.

DOCX Document Support

Templates and signing requests now accept simple .docx files in addition to PDFs. Documents are automatically converted to PDF on upload — no extra steps needed. This works across the UI editors and the API (the document field accepts base64-encoded DOCX or PDF).

Signature Verification Frames

Completed documents can now display a visual signature verification frame — a small purple pill overlay on each signature showing a truncated signer ID. This makes it easy to visually verify which signer placed each signature. The feature is on by default and can be toggled per-workspace or per-company in settings. Signers who visit an expired, completed, or invalid signing link now see a clear, branded error page explaining what happened, rather than a generic error message. Works in both standalone and embedded contexts.

Additional Improvements

  • Thicker drawn signatures — pen width increased 25% for better legibility on completed documents
  • Signing request detail view — new detail sheet accessible from the dashboard table

March 5, 2026

Passkey Sign-In

Sign in faster with biometric authentication. Register a passkey from your profile using Face ID, Touch ID, Windows Hello, or a hardware security key — then log in with a single tap.
  • Register up to 10 passkeys per account
  • Rename, manage, and remove passkeys from your profile
  • Synced passkey support (iCloud Keychain, Google Password Manager)
  • Device type indicators show whether a passkey is local or cloud-synced
  • Tracks when each passkey was last used

Signer Email OTP Verification

Add identity verification to your signing flow. When enabled, signers must enter a one-time code sent to their email before viewing or signing a document.
  • Enable at the workspace or individual signing request level
  • 6-digit codes with auto-submit, 10-minute expiry, and max 5 attempts
  • Resend button with 60-second cooldown
  • Email address is masked for privacy on the verification screen
See the API changelog for the require_otp_verification setting details.

Template Document Replacement

Swap the PDF on an existing template without losing your work. Upload a new version and all fields, signer assignments, and settings stay in place.
  • Supports PDF and Word (.doc, .docx) uploads with automatic conversion
  • Page count and dimension validation to keep fields aligned
  • Works in both the main template editor and the embedded editor
  • 60MB file size limit
See the API changelog for the POST /templates/{id}/replace-document endpoint.

Custom Email Templates

Customize the emails Firma sends on your behalf. Edit the subject and body for each notification type with dynamic variable support.
  • Five customizable templates: signing invite, next signer notification, expired, cancelled, and declined
  • Insert variables like signer name, document name, signing link, expiration date, and workspace branding
  • Badge indicates whether you’re using a custom or default template
  • Reset to default at any time
  • Warning when a signing invite is missing the signing link variable

Workspace Language Settings

Set a default language per workspace that controls which language system emails are sent in.
  • Supported languages: English, Spanish, Italian, Portuguese, French, German, Greek
  • Language cascades: signing request > workspace > company
  • Affects all outgoing email notifications

Auto-Purchase addition

Enhanced auto-recharge configuration with better credit management and a refreshed UI.

February 24, 2026

Hand-Drawn Only Signature Setting

You can now require hand-drawn signatures via the API by setting hand_drawn_only: true in your signing request settings. When enabled, signers cannot use typed or font-based signatures and must draw their signature directly. See the API changelog for details.

February 18, 2026

Hand-Drawn Signatures

Firma now supports hand-drawn signatures in the signing view. Signers can draw their signature directly using a mouse, trackpad, or touchscreen in addition to the existing typed signature option.

Localization Guide

A new Localization guide is now available in the documentation. It covers Firma’s full multilingual support including the 3-tier language detection system, URL-based language overrides via the ?lang= parameter, per-user language persistence, and localization behavior in embeddable components.

February 17, 2026

Embedded Editor Close Controls

Both the Template Editor and Signing Request Editor now support a built-in close button and programmatic close, giving you full control over the editor lifecycle within your application.
  • Close button — Enable showCloseButton to display a close button in the editor header. When clicked, your onClose callback receives { hasUnsavedChanges: boolean } so you can prompt users to save before navigating away.
  • Programmatic close — Call triggerClose() on the editor instance to close it from your own UI (e.g., a navigation event or “back” button). It checks for unsaved changes automatically.
These options are available on both FirmaTemplateEditor and FirmaSigningRequestEditor. See the embeddable template editor and embeddable signing request editor guides for full details.

February 11, 2026

Multi-Script Signature Support

Firma now supports 5 international writing systems for typed signatures with automatic script detection and curated signature fonts. Supported scripts:
ScriptLanguagesSignature Font
Latin/WesternEnglish, Spanish, French, German, Portuguese, Italian, Polish, CzechDefault signature fonts
CyrillicRussian, Ukrainian, Bulgarian, SerbianMarck Script
GreekGreek (including accented characters like ά, έ, ί, ό)Zen Kurenaido
JapaneseHiragana, Katakana, KanjiZen Kurenaido
KoreanHangulNanum Pen Script
Each script family includes multiple signature style options with hand-picked fonts. The system automatically detects the signer’s script based on their typed name, though signers can manually switch if needed. All signatures render correctly in completion certificates and final PDFs.

Greek Language Support

The Firma interface is now fully available in Greek, bringing the total to 7 supported languages:
  • English
  • Spanish
  • Portuguese
  • French
  • Italian
  • German
  • Greek (new)