Filament intercepting regular user registration flow?
I'm building an admin panel to supplement a Laravel app. Users currently go through a regular login/registration flow using Breeze auth.
Now that I have added Filament, it seems to intercept a user registration so that, when the user clicks on the email verification link, it takes them to a 403 unauthorised error page - this is because they do not have permission to access the Filament admin panel (using the canAccessPanel method in the User model, only users with an admin role can access Filament, by design).
So I'm confused. I don't want Filament to interfere with regular users, but I don't see why this is happening. Can anbody help?
Now that I have added Filament, it seems to intercept a user registration so that, when the user clicks on the email verification link, it takes them to a 403 unauthorised error page - this is because they do not have permission to access the Filament admin panel (using the canAccessPanel method in the User model, only users with an admin role can access Filament, by design).
So I'm confused. I don't want Filament to interfere with regular users, but I don't see why this is happening. Can anbody help?
