- What is rawilk/profile-filament-plugin used for?
- It is a Filament plugin that provides a ready-made user profile starter kit for Laravel applications. It handles boilerplate for multi-factor authentication, password management, session management, email changes, and account deletion. The plugin is opinionated by default but designed to be flexible and customizable, and it reuses your existing User model and Filament panel.
- How do I install rawilk/profile-filament-plugin in Laravel?
- Install it with composer require rawilk/profile-filament-plugin, then publish and run the migrations with php artisan vendor:publish --tag=profile-filament-migrations and php artisan migrate. Publish the config with php artisan vendor:publish --tag=profile-filament-config, then register the plugin in your Filament panel provider using ->plugin(ProfileFilamentPlugin::make()).
- Which Laravel and Filament versions does this profile plugin support?
- The available context confirms that the docs reference Filament 5.x configuration APIs, but it does not state a full Laravel/Filament support matrix or a support window. Check the package composer.json and README for the exact constraints before committing. Because the plugin is pre-release, pin an exact version and test upgrades carefully.
- Is rawilk/profile-filament-plugin production ready?
- The README says the plugin should be production ready but is still pre-release, and API and functionality may change without a major version bump until a stable release. For an auth-critical surface such as MFA, sessions, and password management, treat patch-level updates as not safe by default. Pin an exact version and test upgrades before deploying.
- What database schema changes does this Filament profile plugin require?
- Expect a real schema delta: MFA columns, session tracking, passkey/WebAuthn credential storage, and pending-email-change state on users or adjacent tables. The plugin publishes migrations, but the evaluation frames this as a schema decision that must be reconciled with existing auth, session, and MFA tables rather than a simple install step. Review the migrations before running them in production.
- Does the Sessions page require the database session driver?
- The provided evaluation does not confirm whether the Sessions page requires Laravel's database session driver or uses the plugin's own session-tracking tables. Because session management is in scope, verify the requirement in the docs and source before enabling the page. If the database driver is required, account for the extra database write load.
- Can I customize the profile pages without forking the plugin?
- You can adopt the default pages and progressively specialize them without forking. Customization includes page slugs, titles, nav labels/icons/sort/groups, component replacement or merge via components([...], true), and per-component schema overrides via configureComponents(). That keeps the plugin flexible despite its opinionated defaults.
- Does rawilk/profile-filament-plugin support passkeys and WebAuthn?
- The plugin's scope includes passkey/WebAuthn credential storage, and it cites spatie/laravel-passkeys as inspiration, but the excerpt does not fully document the current feature set. If you enable passkeys, plan for HTTPS, RP ID configuration, and added support burden. If passkeys are out of scope, disable that surface before launch.
- How does the plugin handle MFA recovery if a user loses their device?
- The evaluation lists MFA recovery as a key question, not a confirmed plugin behavior. Check the docs and source to verify whether recovery codes are generated and stored by the plugin. Before relying on it, test the lost-device flow end to end because MFA recovery is security critical.
- What alternatives exist, and what maintenance risk should I weigh?
- The package cites Jetstream, spatie/laravel-passkeys, and claudiodekker/laravel-auth as inspiration, so those are useful comparison points for auth and profile functionality. If you specifically need Filament-native profile pages, this plugin is the directly relevant option in the provided context. Weigh the maintenance risk: it has a single maintainer, thin adoption at 39 stars and zero dependents, and a pre-release API, so pin an exact version and be prepared to vendor or fork if upstream goes dormant.