Filament Auto Logout Laravel Package

Product Decisions This Supports

• Filament v5 upgrade planning: 3.0.0 is the first release compatible with Filament v5 (PR #29). This is the gating dependency that lets a Filament v3/v4 admin panel move to v5 without losing idle-session auto-logout. Treat it as a line item in the platform upgrade epic, not an independent feature.
• Build vs. buy for session hygiene: The package provides a configurable idle timeout with a countdown/logout flow on Filament panels. That satisfies most compliance and shared-workstation requirements (e.g. "sessions terminate after N minutes of inactivity") without custom middleware work. Buying wins on effort; building wins on control (see below).
• Security and compliance posture: Auto-logout is a control commonly cited in SOC 2 / ISO 27001 access-control narratives and in internal policy for kiosk, clinic, or shared-terminal deployments. This gives you a defensible, configurable implementation to point auditors at.
• Roadmap sequencing: Because the package's major versions track Filament's majors, every Filament upgrade forces a coordinated bump here. Budget for that pairing in future roadmap planning rather than treating the admin framework and this utility as independent upgrade tracks.
• Scope check for product: This is a single-purpose utility. It should not be a reason to choose Filament, nor a differentiator in any customer-facing roadmap discussion.

When to Consider This Package

Adopt when:

• You run a Filament panel (v5, now that 3.0.0 exists) with authenticated users, especially on shared devices or in regulated/audited environments.
• You need idle timeout behavior with a visible countdown and warning before logout — the UX detail most in-house implementations skip.
• You want this configured per-panel via Filament's panel configuration rather than writing and maintaining middleware, JS timers, and Livewire event handling yourself.
• Your Filament version is already v5 or your upgrade is scheduled; 3.0.0 is the only release line that supports it.

Look elsewhere or build in-house when:

• You are still on Filament v3/v4 and not upgrading soon. Pin to 2.x and plan the jump. Verify the compatibility matrix before any partial upgrade — do not assume 3.0.0 is backward compatible, since the version bump aligns with a framework major.
• You need guarantees a single-maintainer, small-footprint community package cannot give. No vendor SLA, no security response commitment. If idle logout is a hard compliance control, either wrap it with your own tested fallback or implement it internally — the underlying logic is a middleware plus a JS countdown and is not a large build.
• You need behavior the package does not model: absolute session lifetime caps (independent of activity), multi-tab or cross-device coordination, server-side session invalidation across devices, or logout triggers tied to role/permission changes.
• Your panel is not Filament. The package is tightly coupled to Filament's panel lifecycle and offers nothing for other Laravel admin stacks.
• You have strong supply-chain constraints (allowlisted dependencies, mandatory maintainer-count or provenance review).

How to Pitch It (Stakeholders)

For executives: This is a small, free, open-source add-on for our admin panel that automatically signs users out after a period of inactivity, with a visible countdown so people aren't surprised mid-task. The new 3.0.0 release is the version that works with the admin framework upgrade we have on the roadmap — it unblocks that upgrade rather than adding new scope. Cost is engineering time to bump the dependency and re-test, not license spend. The main risk to flag is that it's maintained by a single volunteer, so if automatic logout is something our security or audit commitments depend on, we should plan a modest in-house fallback.

For engineering: 3.0.0 adds Filament v5 support via PR #29; the major version bump signals a compatibility break with the Filament v3/v4 line, so pin 2.x on current branches and take 3.0.0 only as part of the v5 upgrade. Integration surface is small — panel configuration plus the logout behavior — but validate the countdown, the timeout value, and the Livewire/Livewire-component behavior under a real session before shipping. Because it's a single-maintainer dependency in the auth path, keep a thin internal abstraction or middleware wrapper so a swap-out is a config change rather than a refactor, and add a regression test that asserts idle sessions actually terminate. Also confirm PHP and Laravel version floors implied by Filament v5 before scheduling the bump.