- What Laravel and PHP versions does jeremykenedy/laravel-users require?
- The package targets Laravel 8 or newer on PHP 8.1 or newer, and its UI is built for Bootstrap 4 or Bootstrap 5. If your application runs a newer Laravel major than the documented baseline, verify compatibility in a staging branch before adopting it. The 6.x line is the current release track, with 6.0.1 as a maintenance patch.
- How do I install jeremykenedy/laravel-users in a Laravel app?
- Install it with Composer using composer require jeremykenedy/laravel-users, then publish the package views, configuration, and assets and run the migrations. Clear cached configuration and compiled views afterward so the new routes and admin screens render correctly. If you are upgrading an existing install rather than starting fresh, run php artisan laravelusers:update --unattended instead of a plain publish.
- Does jeremykenedy/laravel-users work with Bootstrap 5?
- Yes, the package ships views for both Bootstrap 4 and Bootstrap 5. Version 6.0.1 fixed a Bootstrap 5 container mismatch that appeared when the host application stylesheet was not reliably loaded, so make sure your app's CSS is present. Teams should confirm which Bootstrap version their layout uses before publishing views, since the markup differs between the two.
- Does this package include roles and permissions out of the box?
- Roles and permissions are provided through an optional integration rather than being hard dependencies, and the package overview describes roles and permissions as part of its user management feature set. In practice you enable the companion roles package and follow the documented setup steps. If you already have your own authorization model, treat the integration as optional and keep your existing guards.
- How do I upgrade from version 5.x to 6.x?
- Follow the 6.0.0 upgrade guide, which covers runtime requirements, published overrides, optional migration tags, account features, package setup, and rollback. Back up your published views, configuration, and assets first, then update Composer, clear config, and run php artisan laravelusers:update --unattended. Effort is higher than a patch upgrade, so plan for a verification pass over the key account, settings, and confirmation pages.
- Does it support soft deletes, search, and sorting on user listings?
- Yes, the package provides searchable and sortable user listings along with soft deletes for the users table. These features come wired into the published admin views and routes, so you get a working dashboard without building the tables yourself. If you customize the listing queries, check that soft-deleted records and search scopes still behave as expected.
- Is this package a good fit for a Tailwind or SPA-heavy application?
- It is a weaker fit. The package is Blade-based and coupled to Bootstrap 4 and Bootstrap 5 markup, so Tailwind, custom design-system, and heavily client-side rendered applications would need substantial view overrides. Treat support for other CSS frameworks as deferred roadmap scope and only adopt the package if you accept that override maintenance.
- How do updates affect my customized published views?
- The package preserves application-owned published views during updates, which prevents your customizations from being overwritten. The tradeoff is that upstream changes are not applied automatically, so you must manually merge things like notification JavaScript and CSS or Bootstrap 5 container rules into your copies. Keep published overrides under version control and review release notes on every upgrade.
- Which optional integrations should I plan for before installing?
- The documented optional integrations are Laravel Toast, Roles, UI Kit, Darkmode Toggle, IP Capture, and Seedster, while Laravel Notifications is a companion package rather than an automatic dependency. Each one is modular, so enable only what your application actually needs. If you use Toast, validate its behavior separately, since 30 optional Toast cases were skipped during core installation testing.
- Do I need a queue worker to run this package in production?
- A monitored queue worker is only required if you enable the optional Composer package management operations, which rely on documented permissions as well. Core user management, account settings, avatars, and admin views do not depend on queue processing. If you do enable package operations, make sure the worker is supervised and that failures are visible to your team.