- How do I install niladam/filament-auto-logout in a Laravel app?
- Install it with Composer using composer require niladam/filament-auto-logout. Because it is a standard Laravel package, service provider auto-discovery should register it without manual wiring, and any optional config file can typically be published with the vendor:publish command. After that you register the plugin on your Filament panel, as shown in the README. Check the package's composer.json constraints first, since v3.0.0 targets Filament v5.
- Does this package support Filament v5, v4, or v3?
- Version 3.0.0 of the package was released specifically to allow Filament v5, so it is the version to use on Filament v5 applications. The jump from 2.0.0 to 3.0.0 is a major version bump, which strongly suggests a breaking compatibility change rather than a drop-in patch. If your app is still on Filament v3 or v4, stay on the earlier package major version unless you are already migrating to v5. Always confirm the exact Filament constraint in composer.json before adopting.
- How do I configure the inactivity timeout before users are logged out?
- The inactivity timeout is configurable, either through the package's published config file or per panel depending on how the plugin is registered. Set the timeout to a value that fits your security policy but is longer than typical form-filling time, so users are not logged out mid-task. Because a major version bump may have changed config keys, compare your published config against the current README after upgrading. Test the value in a non-production environment before rolling it out.
- Can I customize the warning modal and countdown shown before logout?
- The package shows a warning modal with a countdown before the user is logged out, then redirects to the login page. The countdown length and modal behavior are intended to be configurable, but the exact options can change between major versions. Review the README and the plugin source for the current configuration keys rather than assuming v2 settings still apply. If the defaults do not fit your UX, the modal views may be publishable for customization.
- Does it work with multiple Filament panels and custom auth guards?
- The plugin is designed to be configurable per panel, which makes multi-panel setups feasible when each panel registers it with appropriate settings. Custom guards and non-default authentication setups are less certain, because the package follows the standard Laravel session and auth model. Test explicitly with each guard and panel you use, and verify that the redirect target sends users to the correct login page. The release notes are minimal, so behavior in unusual auth configurations should be validated rather than assumed.
- How does auto logout behave with Livewire polling and background browser tabs?
- The plugin tracks user idleness on the client side and is built to work alongside Filament's Livewire-driven panels, but Livewire requests and background tabs are a common source of edge cases. A tab left open in the background may behave differently from an active tab, and frequent polling could affect how idle state is detected. The safest approach is to test real scenarios in your app, including multiple tabs and long-running Livewire components. If behavior does not match your expectations, review the package source, since it has a small code footprint.
- Do I need to publish a config file or register the plugin manually?
- You will need to register the plugin on the Filament panel where you want auto logout enabled. A config file is optional and can usually be published if you want to override defaults, though the package should work with sensible defaults out of the box. If you are upgrading from v2 to v3, re-check registration and config keys, since the major version may have changed them. Follow the current README for the exact steps rather than relying on older tutorials.
- What Laravel and PHP versions does filament-auto-logout require?
- The package follows Filament v5's own requirements, so your Laravel and PHP versions must satisfy Filament v5 first. The precise constraints are defined in the package's composer.json, and those are the authoritative source. Check them with composer why-not or by reading the constraint block before installing, especially if your application is pinned to older Laravel or PHP releases. Do not assume the constraints are identical to those of the previous package major version.
- How can I test that idle users are actually logged out?
- Set a short timeout in a staging environment and leave a panel page idle while watching the session. Confirm the warning modal appears, the countdown runs, the user is logged out, and the redirect lands on the login page. Also test interacting with Livewire components, opening several tabs, and using remember-me sessions to make sure active users are not logged out prematurely. Because this is a small community package, treat this manual verification as part of your upgrade checklist.
- Is this package actively maintained, and what are the alternatives?
- It is a small community-maintained package from a single author, with support handled through GitHub issues rather than a commercial vendor. Releases are coupled to Filament's release cadence, so major bumps tied to Filament majors should be expected and planned for. For alternatives, you can rely on Laravel's native session lifetime and auth session controls, or implement a lightweight client-side idle timer yourself. Either way, keep an eye on issue activity and be prepared to fork or replace the package if maintenance stalls.