Filament Spatie Laravel Activitylog Laravel Package

Product Decisions This Supports

• Admin/ops visibility features: Adds a ready-made Filament resource for browsing Spatie Activity Log entries, so "who changed what, when" becomes a shipped capability in the admin panel rather than a custom build.
• Audit trail and compliance roadmap items: Supports decisions to adopt spatie/laravel-activitylog as the audit backbone and expose it to internal users (support, ops, compliance reviewers) without bespoke UI work.
• Build vs. buy on internal tooling: Replaces an estimated custom Filament resource (model, table, filters, detail view, permissions wiring) with a small, maintained dependency — typically days of engineering saved per admin surface.
• Filament v3 upgrade planning: This release unblocks teams standardizing on Filament v3; it becomes a gating dependency in the panel-upgrade plan rather than a blocker requiring a fork.
• Support and incident workflows: Enables a self-serve "activity history" tab on record detail pages, reducing engineering interrupts for "what changed on this record?" requests.

When to Consider This Package

Adopt when all of the following hold:

• The stack is Laravel + Filament and the app already uses (or is committing to) spatie/laravel-activitylog as its audit log — this package is a UI layer, not an audit implementation.
• You need internal, read-oriented visibility into activity records, not end-customer-facing timelines or exported compliance reports (those usually need custom querying/retention work anyway).
• You are on Filament v3 (v0.7.0) or can pin to v0.6.x for Filament v2. Note this is a 0.x package — expect breaking changes between minor versions, and budget for upgrade work at each Filament major.
• The team accepts a thin, single-maintainer community plugin for a non-critical-path admin screen, with the fallback of vendoring or forking the resource (it is small) if maintenance lags.

Look elsewhere when:

• You need audit logs for regulated compliance (tamper-evidence, long retention, signed exports) — build or buy a dedicated solution.
• You are not on Filament, or are on Filament v2 with no upgrade path yet.
• You require vendor SLAs, security review guarantees, or guaranteed Laravel/Filament version support windows.
• Your activity volume is very high and you need custom partitioning/indexing — the default resource queries will need tuning regardless of package.

How to Pitch It (Stakeholders)

To executives: This is a small, free UI add-on that turns the audit data we already collect into a visible, searchable history inside our admin panel. It converts a recurring "what changed?" support burden into a self-serve feature and closes out an audit-visibility roadmap item at near-zero build cost. Risk is low and contained: it is an admin-only screen, easily replaced, and its new v0.7.0 release keeps us current with our Filament v3 platform.

To engineering: v0.7.0 adds Filament v3 support (the v0.6.x line serves v2), so pin the version that matches your panel and treat this as a hard dependency in the v3 upgrade sequence. It provides a resource over spatie/laravel-activitylog — no new data model, no migrations of its own — so the integration surface is a panel registration plus policy/gate configuration. Caveats to flag: it is a pre-1.0, effectively single-maintainer package, so isolate the registration behind a service provider and keep an eye on the changelog; if maintenance stalls, the resource is small enough to vendor in a day. Net recommendation: adopt for internal audit visibility, do not extend it on the critical path, and re-evaluate at each Filament major release.