Have laravel authetication and authorization setup so the logged in user can or cannot access whatever in nova.
The core is still laravel.
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hi, on our new project we want to use Nova, but I am still confused if it is a good idea to use it together with basic authentication set by php artisan make:auth. We mostly want just a few admin users who will have access to Nova to administer everything, and then have regular users who need to be logged in for some actions in the front-end of the application but without any access to Nova at all.
So I am wondering if I should do artisan make:auth first to handle standard users and then install Nova on top of that, or if Nova itself can replace all middleware provided by make:auth and having both would be duplicit / bad practice? Obviously I just want a single users table and stick to best practices, but as the roles won't be mixed, I would like to simply say that admins can access nova, regular users cannot and don't worry about it much anymore. What setup would be most appropriate? Thanks a lot
Please or to participate in this conversation.