Laravel Users documentation
| Guide | What it covers |
|---|---|
| Artisan commands | Installation, updating, runtime/CSS choices, optional package setup, publishing, backups, and rollback. |
| Routes and authorization | Route names, middleware, access rules, and optional user/account pages. |
| User settings | Global defaults, live avatar previews, individual appearance, access rules, Toast controls, package progress, and worker verification. |
| Navigation components | Standalone theme toggle and user menu in an application-owned layout. |
| Configuration | Configuration keys, environment variables, UI controls, layouts, and defaults. |
| Roles and permissions | Optional Laravel Roles, Spatie, custom models, guards, teams, and middleware. |
| Emails | Templates, previews, bulk recipients, expiration, welcome mail, and deleted-account links. |
| Avatars | Global sources, per-user preferences, migration, inheritance, and safe fallbacks. |
| Login activity | Latest login, browser/device/IP information, online sessions, storage, and cleanup. |
| Impersonation | Optional role-restricted sessions, verification, expiration, middleware and activity behavior. |
| Optional integrations | Optional UI and host services with explicit setup. |
| Upgrading | Version transitions, published overrides, opt-in migrations, deployment checks, and rollback. |
| Testing | PHP and browser suites, CI matrix, accessibility, and isolated preview fixtures. |
| Changelog | Every published version and historical tag, linked to the canonical release notes. |
| Roadmap | Current release scope and deferred CSS frameworks and application runtimes. |
Start with upgrading for an existing application. New applications should run the installer after setting up their user model and authentication. No package command creates administrator accounts or silently enables optional tracking, account links, or role integrations.
Detailed release entries are maintained in the root CHANGELOG.md.