- What is tonystore/livewire-permission-manager used for?
- It is a Laravel package that provides a graphical Livewire interface for managing roles and permissions. You can create roles, assign permissions, and edit user access rights from your application dashboard without building the admin screens yourself. It fits best in server-rendered Laravel applications with an existing Blade or Tailwind admin area.
- Does it require Spatie laravel-permission?
- The package layers Livewire components over a role and permission backend, and the technical evaluation indicates it almost certainly relies on Spatie laravel-permission. Before adopting it, confirm the hard dependency and the supported Spatie major version in its composer.json. Pin exact versions for both packages because authorization behavior is security-relevant.
- Is it compatible with Livewire 3 and Laravel 11 or 12?
- Compatibility is not established by the provided package description, so verify the declared Livewire and Laravel constraints before installing. Livewire 3 was a breaking rewrite, and many Livewire 2-era packages were never updated. Also check whether the repository has a CI matrix covering the Laravel and Livewire versions you run.
- How do I install livewire-permission-manager in Laravel?
- The expected flow is composer require, service-provider auto-discovery, publishing config and views, registering the package routes behind auth middleware, and optionally running migrations. In a greenfield project, install and configure Spatie laravel-permission first, seed roles and permissions through code, then add this package as a management surface. Do not make this UI the foundation of your authorization setup.
- Is it safe to use in production?
- Treat it as a security-relevant dependency rather than a convenience package because its blast radius is authorization. Adoption signals are weak: 17 stars, zero dependents, and a single maintainer mean little third-party field testing. Review route gating, policy checks, cache invalidation, and guard handling before exposing it in production. The MIT license is a safety valve because you can fork and vendor the code if maintenance stops.
- How are the permission management routes protected?
- You need to confirm whether route protection comes from a publishable middleware or gate configuration value, or from hardcoded checks. There should also be a documented super-admin gate or equivalent authorization control. Register the package routes behind your own auth and authorization middleware, and test that non-admin users cannot reach the management screens.
- Does it support multiple guards, Spatie teams mode, and multi-tenancy?
- The provided material does not document support for multiple guards, Spatie teams mode, or tenant-scoped roles. Verify these before adoption if your application uses more than a single default guard or isolates data per tenant. A management UI that assumes one guard or leaks roles across tenants would be unsafe for multi-tenant deployments.
- Does the package ship its own migrations or use Spatie tables?
- Confirm whether it ships migrations for roles, permissions, and pivot tables or operates on Spatie's existing schema. If its migrations overlap Spatie's tables, do not run them against a database that already has Spatie installed. In a brownfield project, take a schema and data snapshot of the roles, permissions, and pivot tables before the first staging install.
- Can I use it with Filament, Inertia, or a React SPA admin?
- It is a poor fit for API-only backends, Inertia or Vue and React SPAs where admin UIs live in a separate front end, or teams already standardized on Filament. Filament has mature permission-management plugins, so evaluate those first in that stack. This package makes the most sense when your admin is already built with Livewire, Blade, and Tailwind.
- Is the package actively maintained and does it have tests?
- The evaluation reports weak adoption signals, including 17 stars, zero dependents, and a single maintainer. Check release history, open issues, and whether CI exists at all. Ask what the test coverage is for role CRUD, route protection, guard handling, and Spatie permission-cache flushing. If maintenance stalls, the MIT license allows you to fork and vendor it.