- How do I install tapp/filament-auditing in a Laravel Filament app?
- Run composer require tapp/filament-auditing:^4.0 after Laravel Auditing is already installed and configured. Optionally publish the config, views, and translation files with the vendor:publish tags, then add the relation manager to your resources and register the panel plugin. For Filament 4.x or 5.x use plugin 4.x, and do not mix major versions.
- Which Filament and Laravel versions does tapp/filament-auditing support?
- The README compatibility table maps plugin 4.x to Filament 4.x and 5.x, plugin 3.x to Filament 3.x, and plugin 2.x to Filament 2.x. That table is major-level only and does not document a full PHP, Laravel, or Laravel Auditing support matrix. Pin the plugin major exactly and verify release metadata and tags against your own Filament, Laravel, and PHP versions before relying on it.
- Do I need to install Laravel Auditing before using this plugin?
- Yes. This package is a Filament UI adapter over Laravel Auditing and provides little standalone value on its own. Install and configure Laravel Auditing, instrument your models, and confirm audit rows exist before adding the plugin. The audits schema and model instrumentation remain the application's responsibility.
- How do I add the audits relation manager to a Filament resource?
- Add the AuditsRelationManager provided by the package to the resources where you want audit history visible on the view and edit pages. Then register the FilamentAuditingPlugin in your panel provider so the global audit resource and actions are available. Keep the change scoped to selected resources so you control which records expose old and new values.
- How does restoring previous versions work in tapp/filament-auditing?
- The audits table includes grouped actions that let an authorized user restore a previous version of the record from a view or edit page. Treat restore as a write operation and decide permissions, approval steps, and whether a restore itself creates a new audit entry before enabling it broadly. Test restore behavior on a low-risk model in a non-production environment first.
- How do I register the FilamentAuditingPlugin in a Filament panel?
- Register the FilamentAuditingPlugin in your Filament panel provider, usually inside the plugins array of the panel configuration. After registering it, rebuild your frontend assets so the plugin views and styles are compiled. Clear cached config with php artisan optimize or your usual cache refresh command whenever plugin config changes.
- Why is the audits table unstyled or broken after installing the plugin?
- Most styling problems come from the Filament Tailwind theme not including the plugin's vendor views. Add the vendor source path to your theme CSS using the @source directive and rebuild assets. Also publish views only if you intend to own them, since published Blade files take precedence over the package defaults.
- Does tapp/filament-auditing support multi-tenancy?
- Multi-tenancy is not automatic. Enable the tenancy option in the plugin config before running migrations, publish and run the tenant column migration, backfill existing audit rows, and verify the tenant resolver scopes audits correctly. Add data isolation tests before exposing audit history to tenant users.
- How do I customize the audits table columns, sorting, or views?
- Sorting, lazy loading, and grouped table actions are configured in the published config file, and you can add extra columns through the config-driven column extension. Publish the views or use a custom audits view override only when the default table genuinely cannot meet your needs, since that shifts maintenance to your team. Refresh config caches after changing audit settings.
- Is tapp/filament-auditing production-ready and actively maintained?
- It is a narrow, useful admin UX accelerator rather than an audit system of record, so production readiness depends on your governance around restore permissions, PII exposure in old and new values, retention, and query latency. Adoption signals are modest, with a single-vendor package path and no dependents, so plan a fork or replacement contingency. Run a one-model non-production spike first and harden over one to two weeks if tenancy and redaction are in scope.