Download the PHP package kukux/digital-signature without Composer

Digital Signature for Filament

A Laravel Filament plugin for capturing signatures, issuing X.509 certificates, and embedding cryptographically signed stamps into PDF documents.

Supports: Filament v3, v4 and v5 — Laravel 12 and 13 — PHP 8.2+ (8.3+ on Laravel 13)

Documentation

📖 Read the documentation — the same pages as below, with navigation and search.

Requirements

• PHP 8.2+ with ext-openssl and ext-gd
• Laravel 12 or 13 (Laravel 13 needs PHP 8.3+)
• Filament 3, 4, or 5

Quick Install

The installer asks once, then sets up the config, .env, assets and migration, and registers the plugin and a signature policy on your panels. Every step is logged and safe to rerun. See Installation for the flags and the manual steps.

Re-run php artisan filament:assets after every composer update of this package.

Register the plugin in your panel provider:

This registers:

• A floating launcher — a button on every panel page whose slide-over shows what's awaiting the signed-in user, with Sign / Decline on each row
• Signatures — a full admin resource for registering reusable signature images and viewing signature records
• Sign Document — header actions inside the Signatures resource for signing with a registered signature

The floating launcher

Signing is an interruption, not a destination. Rather than adding sidebar items a signatory has to go looking for, the plugin pins a button to every page of the panel; clicking it slides over the documents waiting on them.

While the launcher is on, the inbox page and the Signatures resource stop claiming navigation items — both stay routable, and the slide-over links to them. Keep the launcher and the sidebar entries with SIGNATURE_LAUNCHER_REPLACES_NAV=false.

It won't land on your own floating button. A plugin doesn't own the corner it's dropped into, so before settling the launcher measures what the host app already has pinned there — a FAB, a chat widget, a cookie bar — and stacks itself clear, re-measuring on resize and when widgets mount late. Sidebars and other full-height layout are floated over rather than stacked above. Where the detector guesses wrong, name the widget in launcher.avoid / launcher.ignore; where you already know the answer, set launcher.offset and turn avoid_overlap off.

Position, icon, label, brand colour, offsets, z-index and badge poll interval are all config; see Configuration.

Preparing a Signable Model

Any model whose PDF can be signed must implement Signable and use HasSignatures.

Adding the Sign Action to Your Own Resource

First let the signer register a reusable signature from the built-in Signatures resource. Then add SignDocumentAction to any resource whose model implements Signable.

For controller-driven or custom page flows, see Ad-hoc Signing.

Built-in Signatures Admin Resource

When the plugin is registered, a Signatures resource appears in the sidebar automatically.

Register SignaturePlugin::make() on every Filament panel that should use the package. If a panel discovers or registers SignatureResource without the plugin, Filament can report Plugin [signature] is not registered for panel [admin].

List page: a table of all signature records with thumbnail, signer, status and method. Each row has View (a slide-over with the details), Download and Revoke.

There is no separate View page. Manage signatures in the launcher drawer widens the drawer to show every signature's details, download, revoke, usage history and the PDF templates it can be applied to, without leaving the current page.

Customize appearance:

Multi-Signatory Documents

When a document is signed by roles rather than by whoever opens it — an Accomplishment Report with Prepared by, Attested by and Noted by — declare the roles on the template and let the plugin find the people:

Each person registers their signature once in their own panel. Being tagged on a record is then enough for the document to reach them — the plugin resolves the person, finds their signature, pre-fills the placement, and lists the document in their Awaiting my signature inbox.

If your records tag people who aren't User rows (Personnel, Employee), bind how they become logins once, and slots can name them directly:

Documents generated from a person and a period (a report, a DTR), and any document with its own preconditions, are defined once as a SignableDocument and routed by the package. Once routed, View and Download serve the document of record: every signed version is kept, and each signatory can reopen the exact copy they signed. See Integrating documents.

On consent. By default the plugin never signs for anyone: the signature is always produced in the signatory's own authenticated request, with their own certificate. Truly hands-off signing requires that person to grant a scoped, expiring, revocable authorisation from their own account — and every use of it is audited and notified. See Signatory Routing.

Security Highlights

For full details see docs/security.md.

Queue

Signing runs asynchronously. Start a queue worker:

To sign synchronously (no queue required):

The action calls embedAndFinalize() directly unless you opt in to queued signing: