DEV Community: Filament Mastery

Filament slow on large table? Optimize with Postgres partitions

yebor974 — Tue, 13 Jan 2026 07:20:56 +0000

When I started working on a client project, I ran into a familiar challenge: a Filament Resource managing millions of sensor measurements.

The table contained several years of historical data. Most users usually focused on the current month, but occasionally they needed to look back at older measurements for special cases.

At first, it looked like the resource was slow simply due to its sheer size, but profiling revealed a deeper issue. It became clear that Filament itself was not the bottleneck, the database was.

Identifying the problem

Filtering by date or sensor type took several seconds, even for just the current month. Sorting and pagination felt sluggish. It was a classic case of “everything works, but not fast enough for production.”

The goal was simple: allow fast access to current data while keeping historical queries possible, without rewriting the panel.

The example below has been simplified for clarity. In the real project, additional filters and performance optimizations were applied. Default dates focus on the current month, but older data queries remain fully supported. The project was built with FilamentPHP and PostgreSQL.

Partitioning the table by month

To solve the problem, I used PostgreSQL table partitioning, splitting the data by month. Here’s a simplified example:

// Parent table
CREATE TABLE sensor_measurements (
    id BIGSERIAL NOT NULL,
    sensor_id BIGINT NOT NULL REFERENCES sensors(id) ON DELETE CASCADE,
    value NUMERIC(10,2) NOT NULL,
    measured_at TIMESTAMP(0) NOT NULL,
      data JSONB
      created_at TIMESTAMP(0) DEFAULT now(),
    updated_at TIMESTAMP(0) DEFAULT now(),
      PRIMARY KEY (id, measured_at)
) PARTITION BY RANGE (measured_at);

// a month partition
CREATE TABLE IF NOT EXISTS sensor_measurements_2026_01 PARTITION OF sensor_measurements
    FOR VALUES FROM ('2026-01-01') TO ('2026-02-01');

CREATE TABLE IF NOT EXISTS sensor_measurements_2026_02 PARTITION OF sensor_measurements
    FOR VALUES FROM ('2026-02-01') TO ('2026-03-01');

The partition key need to be in the primary key.

Partitioning ensures queries for the current month only scan a small, relevant subset, keeping performance high. Historical queries still work efficiently by targeting older partitions.

I created a scheduled job to automatically create new year/month partitions. More information about PostgreSQL partitioning is available in the official PostgreSQL documentation

Adding indexes and optimizing queries

Indexes must be created on each partition, not on the parent table. For example:

CREATE INDEX idx_sensor_measurements_2026_01_data_gin
    ON sensor_measurements_2026_01(sensor_id)
      USING GIN (data);

CREATE INDEX idx_sensor_measurements_2026_01_measured_at 
    ON sensor_measurements_2026_02(measured_at)
      USING GIN (data);

This ensures that even with filters, the database can quickly find the relevant rows.

Adjusting the Filament Resource

Finally, I adapted the Filament Resource with default filters for the current month:

use Carbon\Carbon;

class SensorMeasurementResource extends Resource
{
      //...

    public static function table(Table $table): Table
    {
        $now = Carbon::now();

        return $table
            ->columns([
                TextColumn::make('sensor_id')->sortable(),
                TextColumn::make('value'),
                TextColumn::make('measured_at')->dateTime(),
            ])
            ->filters([
                Filter::make('date')
                    ->form([
                        DatePicker::make('from')
                            ->default($now->copy()->startOfMonth()),
                        DatePicker::make('to')
                            ->default($now->copy()->endOfMonth()),
                    ])
                    ->query(fn(Builder $query, array $data) => $query
                        ->when($data['from'], fn($q) => $q->where('measured_at', '>=', $data['from']))
                        ->when($data['to'], fn($q) => $q->where('measured_at', '<=', $data['to']))
                    ),
            ]);
    }
}

I didn't include the TableSchema file in this example for simplicity. One limitation is that the filter cannot be made mandatory without allowing users to remove it from the indicators toolbar. The goal is to always have a date range to optimize database loading.

Results

The impact was immediate:

Queries for the current month now return in under 300ms
Historical queries remain fast enough for occasional analysis
Users can explore both current and past data without frustration

Lessons Learned

Filament can handle large datasets, if the underlying database is optimized.
Partitioning by time periods is ideal for sensor or historical measurement data.
Proper indexes + pagination make huge tables usable in production.
Profiling queries first saves hours of wasted debugging in the admin panel.
Small tweaks in Filament (filters, lazy-loading) can dramatically improve UX.

If you enjoyed this kind of real-world experience and case study, don’t forget to like and share it!

📬 Join the community on filamentmastery.com

One year of Filament Mastery - A personal look back at 2025

yebor974 — Wed, 31 Dec 2025 08:13:03 +0000

About a year ago, I launched Filament Mastery with a pretty simple goal: create a place around FilamentPHP that I would genuinely enjoy reading myself.

No hype, no endless tutorials rewritten ten times, no over-engineered examples, just clear, useful content for developers building things with Filament.

As 2025 comes to an end, this felt like the right moment to pause for a bit and look back at what Filament Mastery has become over its first year.

Filament Mastery in numbers

I usually don’t obsess too much over metrics, but numbers can still tell part of the story.

After one year, Filament Mastery looks like this:

347 community members
274 newsletter subscribers
35 published articles
12 community links
4 partners supporting the project

They’re just numbers, but behind them are real people reading, learning, experimenting, and building things with Filament.

A community that goes beyond borders

One thing that surprised me early on was how international the audience became.

Looking at the dashboard, users are spread across many different time zones. Some of that data isn’t perfectly accurate (a lot of users are still grouped under UTC), but the overall trend is clear:

Filament Mastery is being read all over the world.

Different countries, different projects, different levels of experience — but the same interest in building solid back-offices with Filament.

What this year taught me

Working on Filament Mastery over the past year reinforced a few things I already suspected:

Developers value clarity more than complexity.
Not every problem needs a clever abstraction or a custom solution.
Filament works best when you lean into its conventions instead of fighting them.
Writing content that you would actually use is usually the right approach.

I intentionally kept Filament Mastery focused and calm. No rush to publish, no pressure to cover everything, just content that feels useful and honest.

A sincere thank you

Even though I’m writing this from a personal perspective, Filament Mastery wouldn’t exist without the people reading it and writing.

So thank you, whether you’ve read one article, subscribed to the newsletter, shared a link, wrote an article or simply bookmarked the site and come back from time to time.

Where to follow Filament Mastery

If you’d like to stay updated, share content, or help the community grow, you can also find Filament Mastery on:

X.com
Dev.to
Facebook
LinkedIn

Following and sharing helps more than you might think.

Looking ahead to 2026

I don’t have a big roadmap or ambitious promises for 2026 — and that’s very much on purpose.

Most of what I share on Filament Mastery comes directly from real client projects.

Things I actually use, patterns that work in practice, and decisions made under real-world constraints. I usually avoid diving too deep into heavy concepts like strict DDD or over-abstracted architectures, not because they’re wrong, but because they often add complexity and make articles harder to read and reuse.

My goal is to keep sharing practical ideas that you can adapt easily, without forcing a specific methodology or way of thinking.

I also want Filament Mastery to stay open and community-driven.

Anyone can write and publish content directly from their member area, and this will remain free. No paywalls, no hidden requirements, just useful content shared by people building real things.

On a more personal note, 2026 will also be a bit different for me. I’m planning to spend around six months in Europe, and if the opportunity comes up, I’ll try to attend local meetups or events. Nothing official or planned yet, just a chance to meet people from the community in real life.

For now, the direction stays simple: build, learn, share and keep things approachable.

Thanks for being part of this first year, and see you in 2026 🚀

📬 Join the community on filamentmastery.com

How to send Filament database notifications to a specific queue

yebor974 — Thu, 04 Sep 2025 10:10:16 +0000

When working with Filament\Notifications\Notification, sending database notifications with sendToDatabase() is super convenient. But what if you want to control which queue these notifications are dispatched to?

At first glance, this looks tricky, Filament doesn’t expose a queue configuration option directly. But the good news is: you can still take full advantage of Laravel’s queue system.

Default behavior for Filament notifications on database

The usual Filament way looks like this:

use Filament\Notifications\Notification;

Notification::make()
    ->title("Your request has been processed")
    ->body("Some details about the request")
    ->sendToDatabase($user);

What happens under the hood:

Filament calls $user->notify($this->toDatabase()).
toDatabase() creates a Filament\Notifications\DatabaseNotification, which extends Laravel’s Notification, implements ShouldQueue, and uses the Queueable trait.
That means the notification goes into the queue defined by your QUEUE_CONNECTION (database, redis, etc.), but you cannot specify which queue name this way.

How to control the queue: Using `toDatabase()` + `onQueue()`

Instead of sendToDatabase(), grab the notification instance with toDatabase() and apply onQueue():

use Filament\Notifications\Notification as FilamentNotification;

$databaseNotification = FilamentNotification::make()
    ->title("Your request has been processed")
    ->body("Some details about the request")
    ->toDatabase() // returns a DatabaseNotification (Laravel Notification)
    ->onQueue('notifications'); // from Queueable trait

$user->notify($databaseNotification);

Or, in a single line:

$user->notify(
    FilamentNotification::make()
        ->title("Your request has been processed")
        ->body("Some details about the request")
        ->toDatabase()
        ->onQueue('notifications')
);

This way you keep the simplicity of Filament’s fluent API and you get fine-grained queue control.

Multiple users example

If you need to notify multiple users on the same queue:

$notif = FilamentNotification::make()
    ->title("Your request has been processed")
    ->body("Some details about the request")
    ->toDatabase()
    ->onQueue('notifications');

foreach ($users as $user) {
    $user->notify($notif); // reuses the same notification instance
}

Conclusion

If you just want to send database notifications, Filament’s sendToDatabase() is perfect.

But if you need queue control , switch to toDatabase()->onQueue('...'). That way you stay fully in the Filament ecosystem, so your notifications are correctly stored and displayed in your Filament panels, while still taking advantage of Laravel’s queue flexibility.

🙏 Thanks to @obaume for reaching out on this topic. His question made me dive deeper into Filament notifications and discover this approach!

💡 Community Idea: Currently, sendToDatabase() doesn’t allow specifying a queue. If this article gets enough likes or shares, I’ll consider proposing a Pull Request to Filament to add this feature—making queue management even easier for everyone!

📬 Join the community on filamentmastery.com — it's free!

Filament Email Verification: Leveraging Laravel’s Event System

yebor974 — Wed, 20 Aug 2025 04:11:50 +0000

In this tutorial, we'll explore how to trigger an event when a user's email is verified in a Filament application. While this is primarily a Laravel concept, Filament fully supports and integrates with Laravel's powerful event and listener system. You'll see how to apply this to Filament projects seamlessly.

We’ll cover:

Creating a listener for the email verification event,
Triggering actions such as Stripe registration or newsletter subscription,
Testing the event with Event::fake,
Extending the logic to other events like user registration or login.

By the end, you'll understand how to leverage Laravel's event system in your FilamentPHP apps for advanced user workflows.

To set up your project for enabling email verification on panel, you can check the first step of this article.

Step 1: Create a Listener for the `Verified` Event

Laravel emits the Illuminate\Auth\Events\Verified event when a user successfully verifies their email. Here's how to hook into it.

1.1 Generate the Listener

Run the following command to create a new listener:

php artisan make:listener HandleUserEmailVerified

This command will create a file in App\Listeners folder:

namespace App\Listeners;

use Illuminate\Auth\Events\Verified;

class HandleUserEmailVerified
{
    /**
     * Handle the event.
     *
     * @param \Illuminate\Auth\Events\Verified $event
     * @return void
     */
    public function handle(Verified $event)
    {
        ///
    }
}

1.2 Implement the Listener

Update the listener to perform actions after email verification, for example :

namespace App\Listeners;

use Illuminate\Auth\Events\Verified;

class HandleUserEmailVerified
{
    /**
     * Handle the event.
     *
     * @param \Illuminate\Auth\Events\Verified $event
     * @return void
     */
    public function handle(Verified $event)
    {
        $user = $event->user;

        // Example: Create a Stripe account
        if (!$user->stripe_id) {
            $this->createStripeAccount($user);
        }

        // Example: Subscribe to a newsletter
        $this->subscribeToNewsletter($user);
    }

    protected function createStripeAccount($user)
    {
        // Logic to integrate with Stripe API
    }

    protected function subscribeToNewsletter($user)
    {
        // Logic to integrate with a mailing list API
    }
}

Step 2: Register the Listener for the `Verified` Event

If you're using Laravel 10 or later, Laravel can auto-discover event-listener mappings. So this step may not always be required, but keeping it explicit helps with debugging.

namespace App\Providers;

use Illuminate\Auth\Events\Verified;
use App\Listeners\HandleUserEmailVerified;

class EventServiceProvider extends ServiceProvider
{
    protected $listen = [
        Verified::class => [
            HandleUserEmailVerified::class,
        ],
    ];
}

Step 3: Test the Listener with `Event::fake`

Before using this in production, ensure everything works as expected. Laravel provides a helpful testing utility to fake events and assert their behavior.

Here’s a test example:

namespace Tests\Feature;

use Illuminate\Auth\Events\Verified;
use Illuminate\Foundation\Testing\RefreshDatabase;
use Illuminate\Support\Facades\Event;
use Tests\TestCase;
use App\Models\User;

class EmailVerificationTest extends TestCase
{
    use RefreshDatabase;

    /** @test */
    public function it_dispatches_verified_event_after_email_verification()
    {
        Event::fake();

        $user = User::factory()->unverified()->create();

        $user->markEmailAsVerified();

        // Assert the Verified event was dispatched
        Event::assertDispatched(Verified::class, function ($event) use ($user) {
            return $event->user->is($user);
        });
    }
}

Step 4: Applying the concept in FilamentPHP

Why This Matters in Filament

Filament is built on Laravel, meaning you can use Laravel's event system in your Filament-powered applications. For example, when managing a User Resource , you can leverage the same listener to perform actions after email verification.

You could:

Add custom hooks in Filament tables or forms,
Use Filament notifications to display messages when an event is triggered,
Extend user workflows directly within the Filament admin panel.

Step 5: Extending the Principle

Event: `Registered`

The Illuminate\Auth\Events\Registered event fires after a new user is created. This is useful for:

Sending a welcome email,
Assigning default roles,
Creating a related profile or team entry.

Example listener:

namespace App\Listeners;

use Illuminate\Auth\Events\Registered;

class HandleUserRegistered
{
    public function handle(Registered $event)
    {
        $user = $event->user;

        // Assign a default role
        $user->assignRole('default');
    }
}

Event: `Login`

The Illuminate\Auth\Events\Login event fires upon user login. Use it to:

Log user activity,
Update a "last login" timestamp,
Sync data with an external system.

Example listener:

namespace App\Listeners;

use Illuminate\Auth\Events\Login;

class HandleUserLogin
{
    public function handle(Login $event)
    {
        $user = $event->user;

        // Update last login time
        $user->update(['last_login_at' => now()]);
    }
}

Conclusion

By using Laravel's event system into your Filament projects, you can create robust workflows tailored to user actions. Whether it's email verification, registration, or login, the possibilities are endless.

📬 Join the community on filamentmastery.com — it's free!

Laravel Filament Multipanel Starter - Build your app fast

yebor974 — Wed, 13 Aug 2025 11:20:37 +0000

Looking for a ready-to-use admin and member panels for your Laravel projects? Meet Laravel Filament Multipanel Starter — a clean, opinionated starter kit designed to help you ship faster with Laravel 12 and Filament PHP v4.

What’s included?

Setting up a secure and well-structured backend can take hours. With this starter, you get:

Dedicated admin panel accessible via path or subdomain
Dedicated member panel accessible via path or subdomain
Secure authentication with:
- Email invitation system on user creation
- Password renewal required on first login (via Filament Renew Password)
- Multi-factor authentication with App authentication (not required)
User management (Filament Resource) with:
- Spatie Laravel Permission for roles & permissions
- Default roles and policies pre-seeded
User profile management (email, name, password, timezone)
Light & Dark theme switch + empty custom theme ready to be extended
Database notifications (Filament native support)
Logs Viewer integration (opcodesio/log-viewer) — protected by auth & backend role
Laravel Horizon — queued jobs management — protected by auth and backend role
Timezone management from user profile - Custom registration for member panel with timezone auto-detect.
Centralized date display settings (TextColumn, DateTimePicker)
Default password policy (min 12 characters, mixed case, numbers, symbols)
Fully localized , default to 🇬🇧 english. Extends with your own languages
Dev-friendly tools:
- Laravel Debugbar
- PHPStan for static analysis
- Pint for consistent code formatting

Instead of reinventing the wheel every time you need a secure backend panel and a secure member panel , this template gives you a solid, scalable foundation —with the best practices already in place.

Tech stack highlights

Laravel 12
Filament PHP v4
Tailwind CSS v4
PHP 8.2+
PostgreSQL / MySQL
Redis & Laravel Horizon

Who is it for?

✅ SaaS admin and member panels
✅ Internal dashboards
✅ Intended for public-facing user portals (for a simple backend panel without member panel you can see Laravel Filament Backend Starter).

Compare Starter Templates

Feature / Module	Backend Starter	Multipanel Starter
Laravel version	Laravel 12	Laravel 12
Filament version	v4	v4
Backend Panel	✅	✅
Member Panel (User Portal)	❌	✅ User panel with login, registration, profile
Panel-Specific Middleware & Routes	✅	✅ Per panel config & middleware
Subdomain or Path Routing	✅	✅ (separate for each panel)
Authentication via Email Invitation	✅	✅
Password Reset on First Login	✅	✅
Multi-factor authentication	✅ (App authentication)	✅ (App authentication)
Roles & Permissions (Spatie)	✅	✅
Timezone Management	✅	✅
User Profile Management	✅	✅
Logs Viewer (Opcodes)	✅	✅ (protected backend user)
Laravel Horizon	✅	✅ (protected backend user)
Dark Mode & Theme Ready	✅	✅
Multi-language Support	✅	✅
Dev Tools (Debugbar, PHPStan, Pint)	✅	✅
Ready for SaaS Admin Panel	✅	✅
Ready for Public-Facing User Portal	❌	✅ (ideal for memberships)
Use Case	Internal tools, dashboard.	Full-stack app (admin + users)

Get it now

👉 Get Laravel Filament Multipanel Template

Register or connect to your panel and get 10% off from the offers page

You will receive your ZIP template by mail. Your purchase grants you the right to use this starter template on unlimited personal or client projects. Reselling or redistributing the code as a standalone product is not allowed.

Visual overview

What’s next?

I'm working on more Filament templates and plugins to make your life easier.Register to Filament Mastery for updates and new releases.

👉 Get Laravel Filament Multipanel Template

Like this article if you'd like me to share more starter kits!

Laravel Filament Backend Starter – Build your admin panel fast

yebor974 — Wed, 13 Aug 2025 11:19:28 +0000

Looking for a ready-to-use admin panel for your Laravel projects? Meet Laravel Filament Backend Starter — a clean, opinionated starter kit designed to help you ship faster with Laravel 12 and Filament PHP v4.

What’s included?

Setting up a secure and well-structured backend can take hours. With this starter, you get:

A fully functional backend panel — accessible via subdomain (backend.yourdomain.com) or path (yourdomain.com/backend).
Secure authentication — with email invitations and password renewal on first login (using Filament Renew Password) and multi-factor authentication with App authentication (not required).
User management out of the box — powered by Spatie Laravel Permission, with roles, permissions, and policies pre-seeded.
User profile management (email, name, password, timezone)
Light & Dark theme switch + empty custom theme ready to be extended
Database notifications (Filament native support)
Logs Viewer integration — protected by auth & backend role
Laravel Horizon — queued jobs management — protected by auth and backend role
Timezone management from user profile
Centralized date display settings (TextColumn, DateTimePicker) on AppServiceProvider
Default password policy (min 12 characters, mixed case, numbers, symbols) on AppServiceProvider
Fully localized , default to 🇬🇧 english. Extends with your own languages
Dev-friendly tools with Laravel Debugbar, PHPStan for static analysis and Pint for consistent code formatting

Instead of reinventing the wheel every time you need a secure admin panel , this template gives you a solid, scalable foundation —with the best practices already in place.

Tech stack highlights

Laravel 12
Filament PHP v4
Tailwind CSS v4
PHP 8.2+
PostgreSQL / MySQL
Redis & Laravel Horizon

Who is it for?

✅ SaaS admin panel
✅ Internal dashboard
❌ Not intended for public-facing user portals (for a double panels, backend and member, you can see Laravel Filament Multipanel Starter)

Compare Starter Templates

Feature / Module	Backend Starter	Multipanel Starter
Laravel version	Laravel 12	Laravel 12
Filament version	v4	v4
Backend Panel	✅	✅
Member Panel (User Portal)	❌	✅ User panel with login, registration, profile
Panel-Specific Middleware & Routes	✅	✅ Per panel config & middleware
Subdomain or Path Routing	✅	✅ (separate for each panel)
Authentication via Email Invitation	✅	✅
Password Reset on First Login	✅	✅
Multi-factor authentication	✅ (App authentication)	✅ (App authentication)
Roles & Permissions (Spatie)	✅	✅
Timezone Management	✅	✅
User Profile Management	✅	✅
Logs Viewer (Opcodes)	✅	✅ (protected backend user)
Laravel Horizon	✅	✅ (protected backend user)
Dark Mode & Theme Ready	✅	✅
Multi-language Support	✅	✅
Dev Tools (Debugbar, PHPStan, Pint)	✅	✅
Ready for SaaS Admin Panel	✅	✅
Ready for Public-Facing User Portal	❌	✅ (ideal for memberships)
Use Case	Internal tools, dashboard.	Full-stack app (admin + users)

Get it now

👉 Get Laravel Filament Backend Template

Visual overview

What’s next?

I'm working on more Filament templates and plugins to make your life easier.Register to Filament Mastery for updates and new releases.

👉 Get Laravel Filament Backend Template

Like this article if you'd like me to share more starter kits!

Handle authorization in Filament: Policies, Roles & Guards

yebor974 — Tue, 05 Aug 2025 08:32:29 +0000

If you're building an admin panel with FilamentPHP and wondering:

“How can I control what each user can access or modify?”

You're asking the right question, and you're about to get a clear, updated answer.

In this guide, we’ll explore how authorization works in Filament , how it integrates with Laravel policy system , and how you can control user access with clarity.

🧱 What is authorization in Filament?

Filament builds on top of Laravel's native authorization layer , mainly using:

The FilamentUser interface to control access to the admin panel
Laravel Policies to control permissions on resources
Optional integration with Spatie Permissions or Filament Shield for roles

Let’s dive into each layer.

Step 1: Granting access to the Admin Panel

To prevent unauthorized users from accessing your admin interface, Filament requires your User model to implement the FilamentUser interface.

use Filament\Models\Contracts\FilamentUser;

class User extends Authenticatable implements FilamentUser
{
    public function canAccessPanel(Panel $panel): bool
    {
        return $this->is_admin; // Or check for roles/permissions here
    }
}

You can check any logic you want — roles, teams, email domains, etc.

If you forgot to implement FilamentUser and to define canAccessPanel() method, your panel may be exposed to all authenticated users.

Step 2: Using Policies in Laravel

Since Laravel 11+ , policies are auto-discovered — you don't need to register them manually.

Create a policy:

php artisan make:policy PostPolicy --model=Post

Then define your authorization logic:

public function update(User $user, Post $post): bool
{
    return $user->id === $post->author_id;
}

Filament will automatically apply these methods in the UI (buttons, actions, forms) — no extra setup needed.

Supported policy methods in Filament

Filament checks for a wide set of policy methods, depending on the action and the state of your model:

Basic Actions:

viewAny(User $user)
view(User $user, Post $post)
create(User $user)
update(User $user, Post $post)
delete(User $user, Post $post)
deleteAny(User $user)

Soft Delete support:

restore(User $user, Post $post)
restoreAny(User $user)
forceDelete(User $user, Post $post)
forceDeleteAny(User $user)

Filament doesn't call these soft delete policies unless the corresponding actions are explicitly enabled in the resource.

If no policy is registered for a model, Laravel allows the action. But if a policy exists and the required method is missing, Laravel will deny access.

Step 3: Overriding permissions directly in a Filament Resource

For quick use cases, you can override permission methods directly in your Resource class instead of defining a full policy:

public static function canCreate(): bool
{
    return auth()->user()->is_admin;
}

public function canEdit(Model $record): bool
{
    return $record->author_id === auth()->id();
}

But be careful:

This is great for simple logic.
For consistency, prefer policies in production apps with more than one resource.

Step 4: Add roles & permissions management

If you need a full role/permission system , you can integrate:

What Laravel Spatie Permission gives you?

Spatie Laravel Permission is a powerful package that adds role and permission management directly to your Laravel app. It doesn’t depend on Filament but integrates nicely.

Create and assign roles (e.g. admin, editor, user)
Define granular permissions (e.g. edit post, delete user)
Attach permissions to users or roles
Use Laravel’s native can() and @can directives
Built-in artisan commands for role/permission management
Supports multiple guards (e.g. web, admin)

Example usage:

$user->assignRole('editor');
$user->hasPermissionTo('edit articles');

In Filament, you can check these with:

return auth()->user()->can('edit articles');

Spatie Laravel Permission is a solid foundation if you want to control access but don’t need a full UI like Filament Shield.

What Filament Shield give you?

Filament Shield Plugin is based on Spatie Laravel Permission and adds a full UI and auto-permission system for Filament with:

Role/permission UI inside your Filament panel
Auto-generated permissions for each resource/action
Seamless integration with Laravel policies

Once installed, you can assign permissions like view_user, create_post, delete_order, etc., per role or user.

About auth guards in Filament

Filament uses the guard defined in your panel configuration under auth.guard. This might be web, or any other name you choose.

If you're using Spatie Laravel Permission (or any other permission system based on guards), you must specify the correct guard when checking for permissions.

Example with `hasPermissionTo()` of Spatie and Filament's guard:

public function delete(User $user, Team $team): bool
{
    return $user->hasPermissionTo('delete team', filament()->getAuthGuard());
}

Without specifying the guard, hasPermissionTo() may look at the default guard. Make sure your permissions and roles are created for the same guard you're using in your checks.

If you're unsure how guards work or how to configure them, check out our dedicated article:

👉 How Auth Guards Work in Filament

Final thoughts

Filament makes authorization much easier by staying close to Laravel’s standards — but with a few important extras.

✅ Use FilamentUser to control access to the admin panel

✅ Use Laravel policies for clean, scalable access control

✅ For role-based systems, consider Filament Shield Plugin or Spatie Laravel Permission (my favorites)

✅ Mind the guards, soft deletes, and policy naming

Get your authorization right early — it’s a foundation your app’s integrity will depend on.

🙏 If this article helped you, share it with your team, give it a like , and consider registering to Filament Mastery — your go-to resource for mastering Laravel Filament.

Don’t start from scratch!

My new Filament Backend Template is the fastest way to start your next Laravel + Filament admin panel.

Pre-configured roles, permissions, Horizon, and more.

Start building faster

Introducing Community Links: Share your favorite resources

yebor974 — Sun, 03 Aug 2025 06:35:56 +0000

We’re excited to introduce a brand-new feature: Community Links — a simple yet powerful way to share your favorite plugins, articles and resources with the rest of the community.

Whether you stumbled upon a helpful blog post, launched your own side project, or discovered a time-saving tool, you can now submit it directly to the community — and we’ll help spread the word.

How to share your link

Not registered yet? 👉 Create your account here
Ready to share? 👉 Submit a new Community Link
Browse all shared links 👉 See public Community Links

We’ve made it quick and easy, with a simple form to add your title, URL, and a short comment.

📬 Featured in the Newsletter

Selected Community Links are featured in our newsletter , giving your submissions the visibility they deserve. Each link is automatically tracked, so you can see how many clicks your shared resource received.

Whether you're a content creator or just want to support cool stuff, Community Links is the easiest way to contribute.

📈 Real-Time click tracking

Want to know if your link is getting attention? You’ll find a simple dashboard that tracks the number of clicks on your links — perfect for measuring engagement and visibility.

Why it matters

No need to write long articles — just share a cool link
Get visibility through our newsletter
Help others discover useful tools, insights, and projects
Track performance with click counts

If you enjoyed this feature, don’t forget to give this article a like and share it with your network — let’s grow the community together! 🚀

Customizing Filament User Model

yebor974 — Tue, 29 Jul 2025 12:34:30 +0000

Filament offers significant flexibility for tailoring the User model to meet the specific needs of your application. Below are some commonly used configurations.

Managing Avatar with the `HasAvatar` Trait

To associate an avatar with each user, you can use the HasAvatar trait. This trait simplifies avatar management by providing ready-to-use methods.

use Filament\Models\Concerns\HasAvatar;

class User extends Authenticatable
{
    use HasAvatar;

    // ...
}

The HasAvatar trait assumes that your User model has an avatar image path like avatar_url attribute. You can customize the getFilamentAvatarUrl() method to define the logic for retrieving the avatar URL:

public function getFilamentAvatarUrl(): ?string
{
    return $this->avatar_url ? asset('storage/' . $this->avatar_url) : null;
}

A quick tip for removing an already registered avatar on a user is to define a setter on the avatar_url attribute (you have to specify your storage path / disk):

protected function avatarUrl(): Attribute
{
    return Attribute::make(
        set: function (?string $value) {
            if (!empty($this->avatar_url) && (is_null($value) || $value !== $this->avatar_url)) {
                Storage::disk('public')->delete($this->avatar_url);
            }

            return $value;
        },
    );
}

This code will delete previous avatar file for the updated user.

Managing Name with the `HasName` Trait

To handle user name, the HasName trait can be used. It allows you to easily define and retrieve the user's full name.

use Filament\Models\Concerns\HasName;

class User extends Authenticatable
{
    use HasName;

    // ...
}

By default, Filament use the name attribute. If your model uses different attributes, you can override the corresponding method to adapt the logic to your database structure:

public function getFilamentName(): string
{
    return $this->username;
}

Controlling Access with the `FilamentUser` Interface

To restrict access to Filament panels, implement the FilamentUser interface in your User model. This allows you to define specific rules to determine which users can access different sections of the admin panel.

use Filament\Models\Contracts\FilamentUser;
use Filament\Panel;

class User extends Authenticatable implements FilamentUser
{
    // ...

    public function canAccessPanel(Panel $panel): bool
    {
        // Logic to determine if the user can access the panel
        return $this->hasRole('admin');
    }
}

In this example, only users with the admin role can access the Filament panel. Adjust the logic in the canAccessPanel() method according to your application's needs.

Multi-Tenant Configuration

Multi-tenant management enables your application to serve multiple clients from a single instance, isolating each client's data. Filament provides tools to facilitate this configuration, but it's essential to understand the security and structural implications for your application.

For a detailed implementation of multi-tenant configuration in Filament, you can read this article.

This article provides step-by-step instructions to configure a multi-tenant application with Filament.

Conclusion

Customizing the User model in Filament is crucial to tailoring your application to the specific needs of your users. By leveraging appropriate traits and interfaces, you can efficiently manage avatars, names, panel access, and more.

You can view some of these configurations directly in the Filament Mastery back office, such as modifying your avatar in your profile.

📬 Join the community on filamentmastery.com — it's free!

Enforcing password updates for admin-created user accounts

yebor974 — Wed, 23 Jul 2025 16:25:09 +0000

Managing user accounts in web applications often involves administrators creating accounts for users. In such cases, ensuring account security is paramount. One effective measure is to force users to reset their password upon their first login. This practice not only reinforces security but also allows users to set a password they prefer.

This article uses the Filament Renew Password Plugin.

Step 1: Install and register the plugin on panel

composer require yebor974/filament-renew-password

Publish default plugin migration that will add two columns to users table : last_password_renew_at and force_renew_password

php artisan vendor:publish --tag="filament-renew-password-migrations"
php artisan migrate

use Yebor974\Filament\RenewPassword\RenewPasswordPlugin;

public function panel(Panel $panel): Panel
{
    return $panel
        ->plugin(
            (new RenewPasswordPlugin())
                ->forceRenewPassword() // activate the force renewal process
                ->timestampColumn() // activate last_password_renew_at column, updating it with each password renewal.
        )
    );
}

Step 2: Setup User Model

Implement RenewPasswordContract on User Model, add default RenewPassword trait and declare fillable attributes.

For example, we just declare a name and email attributes for user.

use Illuminate\Foundation\Auth\User as Authenticatable;
use Yebor974\Filament\RenewPassword\Contracts\RenewPasswordContract;
use Yebor974\Filament\RenewPassword\Traits\RenewPassword;
//...

class User extends Authenticatable implements RenewPasswordContract
{
    use RenewPassword;

    protected $fillable = [
        'name',
        'email',
        'force_renew_password'
    ];

    //...
}

If force_renew_password attribute is set to true, the user will be automatically redirect to the renewal password process.

Step 3: Create UserResource

php artisan make:filament-resource User


class UserResource extends Resource
{
    protected static ?string $model = User::class;

    protected static ?string $navigationIcon = 'heroicon-o-users';

    public static function form(Form $form): Form
    {
        return $form
            ->schema([
                Forms\Components\Section::make()
                    ->schema([
                        TextInput::make('name')
                            ->required(),
                        TextInput::make('email')
                            ->required()
                            ->unique(ignoreRecord: true)
                    ])->columns(2)
            ]);
    }

    public static function table(Table $table): Table
    {
        return $table
            ->columns([
                Tables\Columns\TextColumn::make('name')
                    ->searchable(),
                Tables\Columns\TextColumn::make('email')
                    ->searchable(),
                Tables\Columns\IconColumn::make('force_renew_password')
                    ->boolean()
            ])
            ->filters([
                //
            ])
            ->actions([
                Tables\Actions\EditAction::make(),
            ])
            ->bulkActions([
                Tables\Actions\BulkActionGroup::make([
                    Tables\Actions\DeleteBulkAction::make(),
                ]),
            ]);
    }

        //...
}

Step 4: Generate a default password and send it with email notification

Now, need to generate default password and invite user to connect and renew password. On CreateUser.php page we have to override the mutateFormDataBeforeCreate and handleRecordCreation functions like that:

class CreateUser extends CreateRecord
{
    protected static string $resource = UserResource::class;

    protected string $password;

    protected function mutateFormDataBeforeCreate(array $data): array
    {
        $this->password = Str::password(12); // generate a default password with length of 12 caracters
        $data['password'] = bcrypt($this->password);
        $data['force_renew_password'] = true; // to force user to renew password on next login

        return $data;
    }

    protected function handleRecordCreation(array $data): Model
    {
        /** @var User $user */
        $user = parent::handleRecordCreation($data); // handle the creation of the new user

        $user->notify(new NewAccount($this->password)); // notify the new user with account details

        return $user;
    }
}

The NewAccount notification class is:

namespace App\Notifications;

use Illuminate\Bus\Queueable;
use Illuminate\Database\Eloquent\Model;
use Illuminate\Notifications\Messages\MailMessage;
use Illuminate\Notifications\Notification;
use Illuminate\Support\HtmlString;

class NewAccount extends Notification
{
    use Queueable;

    /**
     * Create a new notification instance.
     */
    public function __construct(protected string $password, protected ?Model $tenant = null)
    {
        $this->afterCommit();
    }

    /**
     * Get the notification's delivery channels.
     *
     * @return array<int, string>
     */
    public function via(object $notifiable): array
    {
        return ['mail'];
    }

    /**
     * Get the mail representation of the notification.
     */
    public function toMail(object $notifiable): MailMessage
    {
        $appName = config('app.name');

        return (new MailMessage)
            ->subject("Your account has been created on $appName")
            ->line("Here are your login details:")
            ->line(new HtmlString("<strong>Email</strong> : {$notifiable->email}"))
            ->line(new HtmlString("<strong>Temporary password</strong> : {$this->password}"))
            ->line("You will be prompted to change this temporary password at your next login.")
            ->action('Go to app', filament()->getUrl($this->tenant));
    }

    /**
     * Get the array representation of the notification.
     *
     * @return array<string, mixed>
     */
    public function toArray(object $notifiable): array
    {
        return [
            //
        ];
    }
}

That's all!

Screenshots

Create user

Receive notification (with smtp mailpit mailer)

📬 Join the community on filamentmastery.com — it's free!

Filament hiding records in table until filtered or searched

yebor974 — Mon, 21 Jul 2025 05:24:02 +0000

If you have too many records in a single table to show immediately, you can hide them until a filter/search is applied.

->modifyQueryUsing(function (Builder $query, $livewire) {
    $hasFilters = collect($livewire->tableFilters)
        ->filter(fn($filter) => !empty($filter['values']))
        ->isNotEmpty();
    return ($livewire->hasTableSearch() || $hasFilters) ? $query : $query->whereRaw('1 = 0');
})

Thanks to @ASSEM909_ for this nice tip!

Want to share or discover more tips? Join Filament Mastery, it's free!

Quick installation and configuration of a Filament panel

yebor974 — Sun, 20 Jul 2025 12:54:09 +0000

Filament PHP is a modern and powerful library that makes creating administration panels for Laravel applications seamless. This article will guide you through the steps to install Filament, configure a panel, and allow an admin user to log in.

What is a Filament panel?

A Filament panel is a user interface designed to manage your Laravel application data. It’s ideal for dashboards, CRUD tools, and advanced administrative features.

Key advantages of Filament:

Modern and responsive interface built with Tailwind CSS.
Quick setup and developer-friendly commands.
Customizable and extendable with plugins and advanced configurations.

Step 1: Set Up a Laravel project

Before installing Filament, you need a working Laravel project. Create a new project using the following command:

composer create-project laravel/laravel your-project-name

This command:

Install a new Laravel app instance
Sets up a default .env config file with sqlite
Run the default migrations with tables like users

Step 2: Install Filament PHP

To add Filament to your Laravel project, follow these steps:

Install the package via Composer:
Set up the Filament panel:

You’ll be prompted to enter a panel name (default: admin) and encouraged to star the Filament repository on GitHub. Go ahead and do it! 😊 This command:

Generates a new Service Provider app/Providers/Filament/AdminPanelProvider.php or with your panel name alias.
Sets up panel routes (default: /admin).
Installs necessary CSS and JavaScript files.

Your new Service Provider looks like that :

class AdminPanelProvider extends PanelProvider
{
    public function panel(Panel $panel): Panel
    {
        return $panel
            ->default()
            ->id('admin')
            ->path('admin')
            ->login()
            ->colors([
                'primary' => Color::Amber,
            ])
            ->discoverResources(in: app_path('Filament/Resources'), for: 'App\\Filament\\Resources')
            ->discoverPages(in: app_path('Filament/Pages'), for: 'App\\Filament\\Pages')
            ->pages([
                Pages\Dashboard::class,
            ])
            ->discoverWidgets(in: app_path('Filament/Widgets'), for: 'App\\Filament\\Widgets')
            ->widgets([
                Widgets\AccountWidget::class,
                Widgets\FilamentInfoWidget::class,
            ])
            ->middleware([
                EncryptCookies::class,
                AddQueuedCookiesToResponse::class,
                StartSession::class,
                AuthenticateSession::class,
                ShareErrorsFromSession::class,
                VerifyCsrfToken::class,
                SubstituteBindings::class,
                DisableBladeIconComponents::class,
                DispatchServingFilamentEvent::class,
            ])
            ->authMiddleware([
                Authenticate::class,
            ]);
    }
}

Of course, you can create multiple panels. For example, you could have an admin panel for administration with a specific guard and a member panel for users. The Filament Mastery blog uses a similar setup with two panels. 😊

To create an other panel:

php artisan make:filament-panel your-new-id-panel

This command:

Generates a new Service Provider app/Providers/Filament/MemberPanelProvider.php if your new id panel parameter is member.

If you plan to work with two or more panels, consider refactoring your default AdminPanelProvider to organize your code into subdirectories and segmented modules for better maintainability.

class AdminPanelProvider extends PanelProvider
{
    public function panel(Panel $panel): Panel
    {
        return $panel
            ...
            ->discoverResources(in: app_path('Filament/Admin/Resources'), for: 'App\\Filament\\Admin\\Resources')
            ->discoverPages(in: app_path('Filament/Admin/Pages'), for: 'App\\Filament\\Admin\\Pages')
            ..
            ->discoverWidgets(in: app_path('Filament/Admin/Widgets'), for: 'App\\Filament\\Admin\\Widgets')
            ...
    }
}

Step 3: Configure the `User` model

To allow login access to the Filament panel, update the User model as follows:

Open app/Models/User.php.
Add the FilamentUser interface and implement the canAccessPanel method:

<?php

namespace App\Models;

use Illuminate\Foundation\Auth\User as Authenticatable;
use Filament\Models\Contracts\FilamentUser;

class User extends Authenticatable implements FilamentUser
{
    public function canAccessPanel(): bool
    {
        return str_ends_with($this->email, '@yourdomain.com');
    }
}

This example restricts panel access to users with a specific email domain. You can update it with your own rules or simply have it return true.

Step 4: Create an user

Run the following command to create an admin user who can log in:

php artisan make:filament-user

You’ll be prompted to enter a name, email, and password. If you prefer not to be prompted, you can pass parameters directly in the command line:

php artisan make:filament-user --name=name --email=email@domain.tdl --password=xxxxxxxxxx

Step 5: Access the panel

The setup is now complete. Start the Laravel server:

php artisan serve

Visit the panel in your browser at:

http://localhost:8000/admin

Next Steps: Customize and extend filament

With the panel running, you can:

Build CRUD resources to manage your Laravel models.
Customize the UI by modifying views and forms.
Install third-party plugins for advanced features like role management and analytics.

Conclusion

Filament PHP makes it easy to integrate a modern, functional admin panel into a Laravel application. With just a few commands, you’ll have a powerful tool ready for customization.

Don’t start from scratch!

My new Filament Backend Template is the fastest way to start your next Laravel + Filament admin panel.

Pre-configured roles, permissions, Horizon, and more.

Start building faster

DEV Community: Filament Mastery

Filament slow on large table? Optimize with Postgres partitions

Identifying the problem

Partitioning the table by month

Adding indexes and optimizing queries

Adjusting the Filament Resource

Results

Lessons Learned

One year of Filament Mastery - A personal look back at 2025

Filament Mastery in numbers

A community that goes beyond borders

What this year taught me

A sincere thank you

Where to follow Filament Mastery

Looking ahead to 2026

How to send Filament database notifications to a specific queue

Default behavior for Filament notifications on database

How to control the queue: Using toDatabase() + onQueue()

Multiple users example

Conclusion

Filament Email Verification: Leveraging Laravel’s Event System

Step 1: Create a Listener for the Verified Event

1.1 Generate the Listener

1.2 Implement the Listener

Step 2: Register the Listener for the Verified Event

Step 3: Test the Listener with Event::fake

Step 4: Applying the concept in FilamentPHP

Why This Matters in Filament

Step 5: Extending the Principle

Event: Registered

Event: Login

Conclusion

Laravel Filament Multipanel Starter - Build your app fast

What’s included?

Tech stack highlights

Who is it for?

Compare Starter Templates

Get it now

Visual overview

What’s next?

Laravel Filament Backend Starter – Build your admin panel fast

What’s included?

Tech stack highlights

Who is it for?

Compare Starter Templates

Get it now

Visual overview

What’s next?

Handle authorization in Filament: Policies, Roles & Guards

🧱 What is authorization in Filament?

Step 1: Granting access to the Admin Panel

Step 2: Using Policies in Laravel

Create a policy:

Supported policy methods in Filament

Basic Actions:

Soft Delete support:

Step 3: Overriding permissions directly in a Filament Resource

But be careful:

Step 4: Add roles & permissions management

What Laravel Spatie Permission gives you?

Example usage:

What Filament Shield give you?

About auth guards in Filament

Example with hasPermissionTo() of Spatie and Filament's guard:

Final thoughts

Introducing Community Links: Share your favorite resources

How to share your link

📬 Featured in the Newsletter

📈 Real-Time click tracking

Why it matters

Customizing Filament User Model

Managing Avatar with the HasAvatar Trait

Managing Name with the HasName Trait

Controlling Access with the FilamentUser Interface

Multi-Tenant Configuration

Conclusion

Enforcing password updates for admin-created user accounts

Step 1: Install and register the plugin on panel

Step 2: Setup User Model

Step 3: Create UserResource

How to control the queue: Using `toDatabase()` + `onQueue()`

Step 1: Create a Listener for the `Verified` Event

Step 2: Register the Listener for the `Verified` Event

Step 3: Test the Listener with `Event::fake`

Event: `Registered`

Event: `Login`

Example with `hasPermissionTo()` of Spatie and Filament's guard:

Managing Avatar with the `HasAvatar` Trait

Managing Name with the `HasName` Trait

Controlling Access with the `FilamentUser` Interface

Step 3: Configure the `User` model