- What is alizharb/filament-activity-log used for?
- It is a Filament panel plugin that provides a dedicated resource, timeline views, and dashboard widgets for activity recorded by spatie/laravel-activitylog. It lets admins browse, filter, and inspect model changes and user actions inside Filament. It is a UI and control-center layer over Spatie, not a standalone audit capture library.
- How do I install alizharb/filament-activity-log in Laravel?
- Install it with Composer, publish and run the migrations, then run the package's backfill, verify-integrity, and doctor commands as part of setup. Register the plugin in your Filament panel configuration. Follow the release notes for the exact command sequence and configuration options.
- Does it support Filament 4 and Laravel 12?
- The v2.0.0 release notes list PHP 8.3 through 8.5, Laravel 12 through 13, Filament 4 through 5, and Spatie Laravel Activitylog 4 through 5. That breadth is a good sign, but confirm your exact combination is on the tested matrix. Filament 3 or Laravel 11 is outside the stated v2 support range.
- Is this package a replacement for spatie/laravel-activitylog?
- No. It wraps spatie/laravel-activitylog as the write path and adds a Filament resource, widgets, and operational guardrails on top. Spatie captures the activity records; this package gives you the admin control center for them. If Spatie is not already in your stack, adopting this package also means adopting Spatie's audit data model.
- Can users revert or restore changes from the activity log?
- Yes, v2 supports restore and revert actions, but destructive actions are disabled by default and mutations are gated behind authorization. Conflict detection and stale-revert blocking reduce the blast radius, but they do not remove the risk because revert is still a write-to-production path. Treat enabling it as a policy decision rather than just a configuration flag.
- How does multi-tenant scoping work in this plugin?
- The package treats tenant scoping as a security control, but the release notes do not fully document the assumed tenancy model or its configuration. Confirm with the maintainer which tenancy model is expected and configure scope boundaries explicitly. Add a negative test in CI so a misconfigured boundary cannot expose cross-tenant activity data.
- What are the HMAC integrity signatures and how do I rotate the key?
- v2 can sign activity records with HMAC signatures so you can verify that history has not been tampered with. The key lifecycle matters: keep the secret secure, maintain environment parity, and plan rotation because unsigned legacy rows may fail verification. The release notes do not document a rotation procedure, so clarify this with the maintainer before production use.
- How does backfill perform on large activity tables?
- Backfill is part of the installation path, but the release notes do not state duration, lock profile, or resumability at production scale. Time it against production-shaped data volume rather than a development seed. Verify that it is chunked and resumable before rolling out to a large activity table.
- How do I upgrade from v1 to v2?
- Treat the upgrade as a gated sequence: install and publish migrations in staging, migrate, backfill, run integrity verification, and capture doctor output as a configuration diff. Expect integrity failures on pre-v2 rows and decide explicitly whether that is an accepted baseline or requires re-signing. The breaking changes are behavioral as well as schema-related, with destructive actions off by default and authorization now required.
- Is this package production-ready and what alternatives should I consider?
- Production readiness depends on your audit consumer and operational policies. If you need an admin UI for Spatie activity logs in Filament, this package fits well; if your audit consumers are an API, BI tool, or SIEM, Spatie plus a custom backend may be a better fit. Check maintainer count, release cadence, security disclosure channel, and whether doctor validates your configuration or only package internals.