- What does jhonoryza/filament-simple-role-permission do?
- It is a Filament plugin that adds straightforward role and permission management to your admin panel, letting you assign roles and permissions to users from the Filament UI without extra complexity. It is distributed as the Composer package jhonoryza/filament-simple-role-permission. The overview describes it as plugin scaffolding, so treat it as a starting point to review and extend rather than a fully documented domain layer.
- Does this package support Laravel 12, and which PHP versions are supported?
- The release note confirms Laravel 12 support, which is a positive compatibility signal for modern Laravel applications. Supported PHP versions, first-party Laravel component constraints and tested CI coverage are not documented in the supplied metadata. Verify Composer resolution in a clean Laravel 12 skeleton on your target PHP version before planning adoption.
- How do I install jhonoryza/filament-simple-role-permission with Composer?
- Install it with composer require jhonoryza/filament-simple-role-permission and pin an explicit version for reproducibility. After that, follow standard Laravel conventions: register the service provider if the package is not auto-discovered, publish any config and migrations, then run migrations. Detailed install instructions were not included in the supplied context, so confirm the exact commands in the package README.
- Do I need to publish config or run migrations after installing it?
- Filament plugin packages commonly ship publishable configuration and migrations, so run the vendor:publish command documented in the README and then php artisan migrate. Check during your install spike whether the migrations create role and permission tables or assume existing ones from another package. Pin the migration set to a specific package version so schema changes and rollbacks stay predictable.
- Can I still use this package on Laravel 10 or Laravel 11?
- Laravel 12 support is confirmed in the release note, but the metadata does not state whether Laravel 10 and 11 remain supported or whether this is a forward-only compatibility change. Treat backward compatibility as unverified and test your actual framework version on a branch. If you still run Laravel 10 or 11, inspect the composer.json constraints before committing to adoption.
- Is this a replacement for spatie/laravel-permission?
- Both address role and permission management in Laravel, but Spatie's laravel-permission is a mature, widely adopted package with extensive documentation and caching support, while this plugin focuses on delivering simple role and permission management inside a Filament admin panel. The supplied context does not describe whether it uses its own tables or builds on another package. Compare the schema, extension points and permission caching behaviour before choosing between them.
- How are roles and permissions enforced in my application after assigning them in the panel?
- The plugin's documented scope is assigning roles and permissions to users in the Filament admin panel; how those checks are enforced elsewhere (gates, policies, middleware, Blade directives) is not described in the provided metadata. Plan to wire the package's role and permission data into your existing authorization layer during the install spike. Review the package source to confirm which middleware or helpers it ships with.
- How should I test this package before rolling it out to production?
- Run a time-boxed install spike on a Laravel 12 branch: resolve dependencies, publish config, run migrations, create roles and permissions, and exercise the core use cases in the admin panel. Then run your full application test suite and static analysis, and pilot in a non-production environment. Document a version pin and a rollback path before any production rollout.
- What risks should I check before adopting this package in production?
- Unverified areas include PHP version constraints, transitive dependency conflicts, Laravel 12 test coverage, and backward compatibility with Laravel 10 and 11. Security posture, license, maintainer activity and abandonment risk are also undocumented in the supplied context. Treat "supports Laravel 12" as possibly only a widened Composer constraint until you confirm CI matrix coverage and release notes.
- Who maintains this package, and how often is it released?
- Maintenance details are not available in the provided context; Laravel 12 support suggests active compatibility tracking, but release cadence, semantic versioning discipline, issue responsiveness and whether it is a single contributor or an organisation remain unknown. Pin the Composer version and monitor upstream releases for behavioural changes. Define a rollback path, since there is no evidence either way about data migrations or breaking API changes.