- How do I install pxlrbt/filament-activity-log in a Laravel Filament app?
- Install it with Composer, publish and run the Spatie activity log migration if it is not already present, add the LogsActivity trait to the models you want to track, and register the activity log page or resource in your Filament panel provider. You also need to configure authorization for who can view the log. A mid-level Laravel developer can usually get a working read-only viewer running in under a day.
- Which Filament and spatie/laravel-activitylog versions does this package support?
- The release history maps to upstream majors: v2.0.0 targets Filament v4, v2.1.0 targets Filament v5, and v3.0.0 targets spatie/laravel-activitylog v5. The package tracks upstream majors promptly but does so with its own major releases. Confirm the exact compatibility matrix before pinning versions in a production app.
- Do I need to publish or run migrations for the activity log table?
- Yes, the activity_log table must exist, but the schema belongs to spatie/laravel-activitylog rather than this package. If your app is not already using Spatie's activity log, publish and run that package's migration before using this Filament viewer. This package is a thin UI layer over the records Spatie writes.
- How do I make my models show up in the Filament activity log?
- Add Spatie's LogsActivity trait to each model you want to audit, and configure logOnly or $logAttributes to control which attribute changes are recorded. The Filament package only renders records already written to the activity_log table by Spatie. If a model is not instrumented with the trait, no activity entries will appear for it.
- Can I restore or revert a change from the activity log viewer?
- Restore and revert capability ships in the package, with an authorization hook introduced in v1.1.0 so you can control who may undo changes. Before promising this to stakeholders, confirm the exact revert scope, because attribute restoration and soft-delete restoration are different behaviors. Treat undo as a configurable feature rather than a custom-built one.
- Is this package multi-tenant safe in a tenant-scoped Filament panel?
- There is no native multi-tenancy support. In a tenant-scoped admin panel, the viewer can surface activity across tenants unless you add a tenant column and a global scope to the activity model. Treat tenant scoping as a blocking design task, not a nice-to-have, because cross-tenant data leakage is a serious risk.
- How do I control who can view activity logs?
- Authorization is configured in the Filament panel, page, or resource layer, and the package provides an extracted authorization hook for restore and revert actions. You should define which roles can browse activity, inspect old and new attribute values, and perform undo operations. This matters because activity logs can expose sensitive model data and user actions.
- How do I prevent sensitive attributes from being stored in the activity log?
- Data hygiene is your responsibility, not the package's. Spatie stores old and new attribute payloads in the properties column, so anything not excluded via logOnly or $logAttributes can land in the table, including PII. Define a documented retention and GDPR policy because immutable audit trails can collide with erasure requests.
- Does pxlrbt/filament-activity-log support translations for non-English panels?
- Yes, the package has community translations for locales including de, fr, es, it, nl, pt_BR, tr, cs, fa, ar, ckb, id, and zh_TW. This removes a recurring localization backlog item for teams running non-English Filament admin panels. Check the current release for the exact set of supported locales.
- Is the package actively maintained, and what are the alternatives or exit costs?
- The project has around 232 stars, a single primary maintainer, and low reported Packagist dependents, so it is useful but not broadly production-proven. Expect to upgrade it in lockstep with Filament and Spatie major releases. The exit cost is low because the data layer is Spatie's and the schema is standardized; replacing the UI with a bespoke Filament resource is roughly one to three developer days of table and form work.