Laravel Filament Activity Log Laravel Package

Product Decisions This Supports

• Audit/history UX in Filament admin: v0.0.3 strengthens the package as a lightweight activity-log UI for Filament, supporting decisions to add change history, accountability, and record-level traceability without building a custom admin surface.
• Support and debugging workflows: Linked subjects in the activity table and view page let support/ops users jump from an activity entry to the affected record’s edit page, reducing context switching during investigations.
• Nested/child model traceability: The HasCustomActivityResource trait lets resource-less child models map activity links onto a parent resource, supporting domains where changes happen on sub-entities but admins manage the parent aggregate.
• Change review in-product: The new “Changes” diff section on the view page exposes old → new values directly, supporting QA, customer support, and operational review without exporting logs or querying the database.
• Admin information density: The “Changes” column is now visible by default, with resources.hide_properties_column_by_default available to restore the prior hidden-by-default behavior. This supports per-product decisions about audit visibility versus table clutter.
• Localization readiness: The changes translation key now ships in all locales, supporting rollout to non-English admin audiences.
• Build vs. buy: For Filament-based internal tools that need readable activity history quickly, this package is likely a “buy/use” candidate over custom audit UI. For compliance-grade audit requirements, treat it as a starting point or UI layer and evaluate additional controls.

When to Consider This Package

• You are building a Laravel + Filament admin panel and need an activity/history view for operational users.
• You already capture activity records and want a Filament-native table/view experience rather than a custom audit screen.
• You need linked drill-down from activity to subject record, including child models that should link to a parent resource.
• You want diff visibility on activity detail pages with a configurable default for the table column.
• You value quick time-to-value and are comfortable adopting a v0.0.x package, including pinning versions and reviewing upgrade notes.
• Look elsewhere or plan to extend if you need immutable/tamper-evident audit logs, legal hold/retention policies, PII redaction, advanced access controls, alerting, exports, non-Filament UIs, or enterprise compliance guarantees.
• If the newly visible “Changes” column creates noise for high-volume activity tables, use the config option; if you need deeper diff customization or resource-link rules beyond the trait, assess extension effort.

How to Pitch It (Stakeholders)

For executives: This release improves the admin audit trail by making activity entries actionable—users can jump to the affected record and see exactly what changed. It reduces investigation time for support/ops, improves accountability, and adds localization coverage with minimal custom build. The package remains early-stage (v0.0.x), so adoption should be scoped and version-pinned.

For engineering: v0.0.3 adds linked subjects in the activity table/view, a dedicated Changes diff section, parent-resource mapping for child models via HasCustomActivityResource, and broader translation coverage. Link rendering is guarded when no subject can be resolved, and tests cover that case. The Changes column is now visible by default, controlled by resources.hide_properties_column_by_default (default false). Treat this as a Filament-native audit UI layer; confirm retention, permissions, and compliance requirements before relying on it as a system of record.