- How do I install jeffersongoncalves/laravel-admin?
- Install it with Composer by running composer require jeffersongoncalves/laravel-admin. Laravel's package discovery registers the service provider automatically, but you should still publish the package configuration and migrations with the vendor:publish command documented in the repository. After publishing, run php artisan migrate to create the admins table. Check the README for the exact publish tags and any additional setup steps.
- Which Laravel versions does jeffersongoncalves/laravel-admin support?
- Release 1.0.1 constrains laravel/framework to ^12.61.1|^13.12.0, so it targets patched Laravel 12.61.1+ and Laravel 13.12.0+ applications. Laravel 11 is not supported by that release. Because the minimum patch levels matter, run composer why-not laravel/framework before adopting it to confirm your lock file resolves cleanly.
- How is the Admin guard different from Laravel's default web guard?
- The package ships a dedicated Admin authenticatable model with its own guard, user provider, and password broker, so admin sessions and password resets are fully separate from your normal users. That means an authenticated admin is not authenticated on the web guard, and vice versa, which is useful when you want strict separation between the dashboard and the public application. The package also provides a migration, factory, and observer for the admin model.
- How do I configure the admin guard and provider?
- Configuration lives in the package config file plus your application's config/auth.php, where you define the admin guard, its provider, and the matching password broker entries. Publish the package config and review the guard name, model class, and table names before writing your own auth logic. If you rename the guard or model, update the password broker and any authorization checks that reference them.
- Can I customize the admins table migration or the Admin model?
- Yes. Publish the package migrations and edit them before running php artisan migrate, or publish and extend the Admin model in your own namespace and point the provider at it. The included factory and observer can also be overridden or replaced if you need custom password hashing, event handling, or additional profile fields. Keep in mind that future package releases may ship migration changes you would then need to reconcile.
- Does the package include a ready-made admin dashboard or login UI?
- The package is positioned as a starting point for an admin panel rather than a full dashboard product, and its core contribution is the separate Admin authenticatable model with its guard, provider, password broker, migration, factory, and observer. Check the repository for the currently available routes, views, and features, since the README excerpt is not included here. If you need a full CRUD panel, you will likely build it on top of the guard this package provides.
- Can I use this package alongside my existing User model and web guard?
- Yes. The whole point of a separate guard and provider is that the Admin model coexists with your existing User model and web authentication without collisions. Requests authenticated through the admin guard resolve to the Admin model, while the web guard continues to resolve to your User model. Just make sure route middleware, policies, and Blade checks explicitly reference the admin guard where appropriate.
- How do I write tests for admin authentication using this package?
- Use the included Admin factory to create admin records in your test suite, then authenticate against the admin guard explicitly rather than relying on the default guard. In Laravel feature tests you can pass the guard name to the actingAs helper, and assertions such as assertAuthenticated should likewise specify the admin guard. Cover login, logout, password reset through the admin broker, and access denial when a request hits admin routes as a normal user.
- Why did release 1.0.1 drop Laravel 11 support, and is that a breaking change?
- The 1.0.1 release is security-driven, referencing advisories GHSA-5vg9-5847-vvmq and GHSA-crmm-hgp2-wgrp, and it raises the framework minimum to patched Laravel 12 and 13 versions. Dropping Laravel 11 in a patch release is a compatibility break for existing consumers, so confirm the package's release policy and whether 1.0.0 remains safe and supported for Laravel 11. Applications still on Laravel 11 should plan a framework upgrade rather than bypassing the constraint with --ignore-platform-reqs.
- What alternatives exist if this package does not fit my Laravel version?
- You can implement the same pattern manually in minutes: add an Admin model extending Authenticatable, define an admin guard, provider, and password broker in config/auth.php, and create a migration for the admins table. If you want a broader admin panel, Laravel starter kits and packages such as Filament or Nova cover dashboards and resource management. This package is the lightest option when all you need is a cleanly separated admin authenticatable.