Weave Code
Filament Notification Center Laravel Package
prodstarter/filament-notification-center
Replaces Filament's flat notification drawer with categorized tabs, each with its own unread badge. Fully drop-in: keep sending notifications exactly as before and simply add ->category(...) so users can scan orders, billing, and system alerts in separate tabs.
Extend Filament's notification drawer with customizable tabs and notification categories for a cleaner, more organized user experience
Frequently asked questions about Filament Notification Center
- What is prodstarter/filament-notification-center used for?
- It is a Laravel package that replaces Filament's flat notification drawer with categorized tabs, each with its own unread badge. It is aimed at Filament v5 admin panels where notifications come from many areas such as orders, billing, CRM, and system alerts. You keep using Filament's existing notification APIs and add ->category(...) so users can scan categories separately.
- How do I install filament-notification-center in a Laravel Filament app?
- Install it with Composer using composer require prodstarter/filament-notification-center, then follow the README installation steps to register it with your Filament panel. Your app must already run PHP 8.3 or newer, Filament v5, and Livewire ^4.1. Validate Composer resolution in a branch or staging environment before promoting it to production.
- Which Laravel, PHP, Filament, and Livewire versions does filament-notification-center support?
- The package targets Filament v5 admin panels and depends on Livewire ^4.1, with PHP ^8.3 required in v1.1.0. It is not suitable for Laravel apps on PHP 8.2 or older Filament/Livewire lines. Pin and validate PHP, Filament, and Livewire constraints together in CI because the dependency matrix is narrow.
- Do I need to change how I send notifications to use categorized tabs?
- No. The package is designed as a drop-in replacement for Filament's notification drawer, so existing calls like Notification::make()->title(...)->sendToDatabase($user) keep working. You only add ->category(...) to the notification chain when you want that notification to appear in a specific category tab.
- How do I configure notification categories and tabs?
- You register the categories you want the drawer to show, and the package renders an All tab plus one tab per registered category with unread counts. Then add ->category(...) to the relevant Notification::make() chains. The README's usage section is the source of truth for the exact registration syntax in your panel.
- Does filament-notification-center persist notifications in the database or require migrations?
- The package is a UI layer over Filament notifications, so database persistence comes from Filament's database notification support, such as sendToDatabase($user). If you use database notifications, your host app needs the standard notifications table migration. The provided release notes do not describe package-specific migrations, so confirm migration requirements in the README and your staging install.
- Can I use filament-notification-center on PHP 8.2 or with an older Filament version?
- No, v1.1.0 formally requires PHP ^8.3, Filament v5, and Livewire ^4.1. The PHP 8.3 requirement matches the actual dependency graph and removes a prior install-resolution trap on PHP 8.2. If your app is on PHP 8.2, upgrade PHP first or defer adoption.
- Is filament-notification-center safe for production?
- Runtime risk is low for v1.1.0 because it contains no package behavior changes and is stated safe to update from v1.0.1. Compatibility risk is moderate due to the narrow PHP 8.3, Filament v5, and Livewire 4.1 dependency matrix. Install it in staging, run your host app's tests, exercise notification creation and read/unread flows, and pin the package version before production use.
- What are alternatives to filament-notification-center for organizing Filament notifications?
- The main alternative is Filament's built-in notification drawer, which is a flat chronological list and needs no extra package. You can also build a custom Livewire notification center tailored to your panel if you need different grouping, authorization, or delivery behavior. Evaluate the package when you specifically want categorized tabs with unread badges as a drop-in Filament v5 enhancement.
- How is filament-notification-center maintained and what upgrade concerns should I watch?
- Maintenance depends on the package maintainer plus the upstream Filament and Livewire communities, so confirm license, issue responsiveness, and release cadence before using it in a business-critical workflow. Future Filament or Livewire major releases may force package upgrades because the current dependency matrix is narrow. Assign an internal owner for Composer updates and panel smoke tests, and keep the package version pinned.
Weaver
How can I help you explore Laravel packages today?