- What is rickdbcn/filament-email used for?
- It is a Filament plugin that adds email management to a Laravel admin panel. You can compose and send emails, build reusable templates, and keep track of outgoing mail from a native Filament interface. It sits on top of Laravel's mail abstractions rather than replacing your mail transport.
- How do I install filament-email in a Laravel project?
- Install it with Composer using composer require rickdbcn/filament-email. Laravel package discovery should register the service provider automatically. Then publish the config, migrations, and assets as documented, run migrations, and register the Filament plugin in your panel provider.
- Does filament-email support Laravel 13?
- Yes, version 2.3.0 is a Laravel 13.x compatibility release. It does not add new features, breaking changes, or deprecations according to the release assessment. Check the package composer.json for the exact PHP, Laravel, and Filament constraints before upgrading.
- Which Filament versions are supported by filament-email?
- The supported Filament version depends on the package release and its composer.json constraints. Version 2.3.0 is aligned with Laravel 13, so verify that your Filament major version matches what the package requires. Also confirm that the plugin registration API is compatible with your Filament panel version.
- Is filament-email a mail transport or does it replace Laravel mail configuration?
- It is not a core mail transport and does not replace Laravel's mail configuration. It manages templates and outgoing mail records on top of Laravel's existing mail abstractions. You should keep using your normal mail driver and configure the package only for template management and logging.
- Do I need to run migrations or publish assets after installing filament-email?
- A typical install requires publishing the config, migrations, and front-end assets, followed by running migrations. The v2.3.0 release notes do not indicate schema changes, but an initial installation still needs the package tables. Check whether previously published views or assets need republishing when upgrading.
- Can I use filament-email for customer-facing transactional emails?
- It is designed primarily for admin and back-office email management inside Filament. Avoid making customer-facing mail flows depend on it without explicit rendering and send tests. Keep application-triggered transactional mail in Laravel's normal mail layer unless you have validated the package's send path in staging.
- Does filament-email support multi-tenant or role-based access for template management?
- Multi-tenant and role-based access behavior is not clearly documented in the available package assessment. In practice, isolate the plugin to admin routes and use Filament's authorization and policy features to restrict access. Review the package documentation and test permissions before relying on it in a multi-tenant setup.
- How should I upgrade filament-email from v2.2.0 to v2.3.0?
- Treat v2.3.0 as part of a Laravel 13 upgrade rather than a standalone package bump. Work in a branch, upgrade Laravel and Filament, install filament-email v2.3.0, then publish config or assets only if required. Test template CRUD, variable interpolation, preview, actual sending, and admin permissions before deploying.
- Is filament-email actively maintained and safe for production use?
- It is an open-source community package with no commercial SLA indicated. The v2.3.0 release appears to include community compatibility work for Laravel 13. For production, pin the version in composer.json, review releases alongside Laravel and Filament upgrades, and keep internal ownership of template governance and upgrade validation.