Weave Code
Permissions Laravel Package
beartropy/permissions
A beautiful Livewire admin UI for spatie/laravel-permission. Manage roles, permissions, and user assignments with searchable tables, dark mode, i18n, and configurable routes and middleware.
Beartropy Permissions is a polished admin UI built on top of spatie/laravel-permission, the industry standard for role and permission management in Laravel. It is not a replacement—it's a Livewire-powered visual layer that makes managing your existing Spatie roles, permissions, and user assignments effortless.
- 🛡️ Role Management — create, edit, and delete roles intuitively
- 🔑 Permission Management — organize permissions with automatic grouping
- 👥 User Assignments — assign roles and direct permissions to users
- 📊 Data Tables — searchable, sortable tables with bulk actions
- 🌐 i18n & Dark Mode — English/Spanish support and seamless theming
Install with composer require beartropy/permissions.
Frequently asked questions about Permissions
- What is beartropy/permissions and how does it relate to spatie/laravel-permission?
- beartropy/permissions is a Livewire-based admin UI add-on for spatie/laravel-permission. Spatie remains the authorization engine and source of truth for roles, permissions, guards, and assignments, while this package provides screens to create, edit, delete, group, and assign them. It is not a replacement for Spatie and does not implement authorization by itself.
- How do I install beartropy/permissions in a Laravel app?
- Install Spatie first, publish its migrations, run them, and add the HasRoles trait to your user model. Then require beartropy/permissions with Composer, publish its config, define the manage-permissions gate, and visit the configured route such as /permissions. The README outlines the standard Blade and Livewire admin setup path.
- Which Laravel, PHP, Livewire, and Spatie versions are supported?
- The intended stack is PHP 8.2 or newer, Laravel 10 or 11, Livewire 3.7 or 4, and Spatie laravel-permission 6 or 7. Laravel 12 is not listed in the package context, so treat it as unverified until you test it. Spatie v5 and non-Livewire frontends are a poor fit.
- Do I need to replace spatie/laravel-permission to use this package?
- No. The package explicitly describes itself as a visual interface for spatie/laravel-permission, not a replacement. You install Spatie, configure roles and permissions through Spatie, and use this package to manage them through a UI. Removing the UI should leave Spatie and your authorization data intact if you plan a rollback.
- How do I configure routes, middleware, guards, and the manage-permissions gate?
- Configuration covers the route prefix, middleware, gate, user model, guards, default guard, display field, search fields, and dot-notation permission grouping. You must define and test the manage-permissions gate correctly because the default middleware and gate are only safe when the application enforces them. Route middleware and Livewire component access should both be checked before rollout.
- Is it safe to expose the permissions admin UI in production?
- The package controls a high-privilege admin surface, so production safety depends on your gate, middleware, and route protection rather than on the package alone. Test unauthorized route access and unauthorized Livewire component actions explicitly. If the manage-permissions gate is misconfigured, you could either expose permission management or block legitimate admins.
- Does beartropy/permissions support multiple guards, multi-tenancy, or audit trails?
- The package provides CRUD, user assignment, and sync error handling, but the assessment notes it does not appear to include approval workflows, detailed audit trails, or tenant scoping. Multi-guard and multi-tenant scenarios need verification against your requirements. For strict audit or per-tenant role scoping, plan additional application logic or a different tool.
- What are the beartropy/ui and beartropy/tables dependencies, and will they conflict with my app?
- beartropy/ui and beartropy/tables are first-class dependencies, so adopting this package means accepting a small single-vendor UI ecosystem. Check them against your design system and existing Composer constraints before rollout. If they conflict with your frontend stack or packages, architecture fit drops.
- Can beartropy/permissions handle large user tables and bulk role assignments?
- The UI includes searchable, sortable tables with bulk actions, which suits internal admin work. The context does not provide benchmark numbers for very large user, role, or permission counts, so test with production-like data. Multi-guard and bulk operation behavior should be validated in your environment.
- What are the alternatives to beartropy/permissions, and how maintainable is it?
- Alternatives include building a custom Livewire admin screen on top of Spatie, using another Spatie-compatible UI package, or managing roles through artisan and seeders. This package has 0 stars and 0 dependents and depends on other low-adoption Beartropy packages, so treat it as an accelerator with an internal ownership and fork plan. If the vendor stalls, your team should be able to patch or remove the UI while keeping Spatie intact.
Weaver
How can I help you explore Laravel packages today?