- What is joaopaulolndev/filament-edit-profile used for?
- It is a Filament plugin that adds a ready-to-use profile page to a Filament panel. Authenticated users can update their name, email, password, and optionally upload or remove an avatar without you building a custom page. It is aimed at Laravel applications already using Filament for admin or back-office surfaces.
- How do I install filament-edit-profile in a Laravel app?
- Install it with Composer using composer require joaopaulolndev/filament-edit-profile, then register the plugin on the Filament panel provider where the profile page should appear. The package does not ship extra migrations beyond your existing users table and does not introduce queues, caches, or external services. Most setup is Composer plus panel registration.
- Which Filament and Laravel versions does filament-edit-profile support?
- Compatibility is primarily pinned to Filament's major version line, so check the package's Composer constraint before adoption. Version 1.0.48 is explicitly scoped to Filament 3, which is a signal to confirm the Filament 4 or next-major story in release notes before committing. Laravel support follows the Filament version you run, so verify both constraints together.
- Can I customize the profile form fields?
- Yes, the plugin exposes fluent configuration for expected customizations such as which fields appear, avatar disk and directory, and password rules. That means most product-specific tweaks are configuration rather than forking the package. Check the config surface for your installed version before assuming a field is supported.
- Does it handle avatar upload and removal?
- Yes, avatar upload and removal are part of the package's profile page. Uploads write to a configured disk, so review the disk and directory settings for public visibility and cleanup behavior. In multi-tenant apps, avoid shared paths that could expose one tenant's avatar to another.
- How does filament-edit-profile handle password changes and other sessions?
- Version 1.0.48 ports driver-independent logout of other browser sessions, so a password change can invalidate sessions on other devices without custom session-invalidation code. Confirm in your app whether that behavior is enabled by default or opt-in, that it runs on the password-change path, and that it preserves the current session. Test it under your configured session driver and behind your load balancer or HTTP cache.
- Does changing email reset Laravel email verification?
- The package edits the email field directly, so you should verify how it interacts with Laravel's MustVerifyEmail contract in your application. Confirm that an email change marks the address unverified and fires the standard Laravel events you rely on. The package overview does not document a separate email-verification workflow, so treat this as an integration check.
- Is filament-edit-profile safe for multi-tenant production apps?
- It is a profile page, not an identity platform, and it has no opinion on multi-tenancy boundaries, roles and permissions, MFA, or audit logging. The main production risks are avatar storage paths and any optional account-deletion toggle, which must be reconciled with soft deletes, GDPR erasure, and foreign-key cascades. Use tenant-scoped avatar disks and make a deliberate decision before enabling deletion.
- How should I test the profile page?
- There is no dedicated testing API called out for this package; test it through your normal Laravel and Filament test suite. Cover profile updates, avatar upload and removal, password changes with session invalidation, and email-change verification behavior. Because it reuses Filament forms and auth, feature tests at the panel level are usually the right level.
- What are alternatives to filament-edit-profile?
- If you only need a simple Filament profile page, this package is the lowest-friction option because it reuses Filament's form builder, notifications, auth guard, and storage conventions. If you need MFA, role and permission editing, audit logging, or tenant-aware identity workflows, consider a broader auth package or a custom Filament page. A custom page is also reasonable when you need exact control over verification, session, and deletion behavior.