May 2026 Product Updates

Six updates shipped this month, covering branding, signing UX, and more granular API control over the signing experience. Here's what's new.

Company and Workspace Logo Upload

You can now upload your own logo to appear on signing certificates and notification emails. Upload a PNG or JPEG (up to 2MB) through Settings > Appearance, or manage logos programmatically via the API. Logos display at a maximum of 180x50px on certificates, maintaining their original aspect ratio.

The priority chain works the same way as other cascading settings in Firma.dev: workspace logo overrides company logo, which overrides the default. If you're running a multi-brand setup with Customer Workspaces, each workspace can carry its own branding. When no custom logo is set, certificates fall back to the Firma.dev default.

API endpoints: POST /company/logo and DELETE /company/logo for company-level branding. POST /workspaces/{id}/logo and DELETE /workspaces/{id}/logo for workspace-level branding. The icon_url field in GET responses returns a publicly accessible URL for email compatability. Full details in the API Changelog v1.19.0.

Guided Navigation Control

By default, Firma.dev automatically scrolls signers to the next required field after they complete each one. That works well for short forms, but it can be disorienting on longer documents where signers need to read content sequentially.

You can now disable this auto-scroll behavior with a single toggle. When guided navigation is turned off, signers move through the document at their own pace. The "Next Required Field" button is still available for anyone who wants it, so nothing breaks for signers who prefer the guided flow.

Like other Firma.dev settings, this cascades across four levels: company, workspace, template, and signing request. Each level overrides the one above it, giving you precise control over the signing experience per document or per client.

The new disable_guided_navigation parameter is available on POST/PATCH /signing-requests, POST/PATCH /templates, and workspace/company settings endpoints. Same cascading pattern as require_otp_verification. Full details in the API Changelog v1.20.0.

Guided Signing Flow

The signing view now walks signers through documents field by field. When a signer agrees to terms and the document loads, the first required field is automatically highlighted and scrolled into view.

After completing a field, the view auto-advances to the next one after a brief delay. A floating label above the active field tells the signer exactly what's needed: "Sign here," "Type text," "Select a date," or "Upload file." A progress bar at the top tracks how many required fields have been completed out of the total.

Keyboard navigation works too. Signers can Tab through fields in reading order and press Enter to advance, so the entire signing experience can be completed without touching a mouse. This is a meaningful improvement for documents with lots of fields, where signers previously had to scroll around and figure out what they'd missed.

Editable Prefilled Data Fields

Prefilled data fields can now be optionally editable by signers instead of always being locked. A new prefilledEditable toggle in the field's format rules controls whether signers can modify the prefilled value during signing.

This is available in the template editor, the signing request editor, both embedded editors, and the full REST API. In the editor UI, it shows up as an "Allow signer to edit this value" checkbox when prefilled data is selected.

The typical use case: contracts where form data pre-populates fields (name, address, employee ID) but signers may need to correct something before signing. Existing prefilled fields remain locked by default, so nothing changes unless you explicitly opt in.

Explicit Field Values via API

API consumers can now set an explicit value on any field when creating signing requests, independent of the prefilled data mechanism or read-only settings. Pass value on any field object in POST /signing-requests or POST /signing-requests/create-and-send, and it takes precedence over auto-populated recipient data.

This gives you a clean way to programmatically fill in contract-specific values like amounts, dates, or reference numbers at creation time without needing to configure prefilled data mappings. The API validates mutual exclusivity, so you'll get a clear 400 VALIDATION_ERROR if conflicting value sources are set on a single field.

Identity Editable Fields

Signers can now review and edit their identity details (name, company, title, phone, address) via a confirmation dialog before signing. A new identity_editable_fields setting accepts an array of field keys to make editable, or null to disable the feature entirely.

You can set different editable fields per recipient, so one signer might be able to update their title and company while another is locked. When a signer does modify their identity, Firma.dev can notify you via a new signing_request.signer_identity_changed webhook event and optional email notifications. Both are controlled through the notify_identity_change_webhook and notify_identity_change_email settings.

Disabled by default, fully backward compatible.

API Reference

Logo upload and guided navigation control are part of API v1.19.0 and v1.20.0 respectively. The other four features shipped in v1.18.0. If you're already integrated, update your API version to access the new endpoints and field properties.

Not using Firma.dev yet? Get started for free, no credit card required.