- What is lizhineng/nova-permission-tool used for?
- It is a Laravel Nova tool that adds an admin interface for managing roles and permissions on top of spatie/laravel-permission. It provides Nova resources and UI for assigning roles and permissions to users, so access-control administration happens inside your Nova panel instead of custom-built screens. It is a lightweight package with low adoption, so weigh it against your own risk tolerance.
- Which Laravel and PHP versions does nova-permission-tool v2 support?
- Version 2.0.0 targets Laravel 5.8 through 6.x on PHP 7.2 and above. That is a legacy window: it does not support Laravel 5.7 or older, and there is no stated support for Laravel 7 or later. Treat the upper bound as unverified and test before assuming compatibility.
- How do I install lizhineng/nova-permission-tool with Composer?
- Install it with Composer, for example composer require lizhineng/nova-permission-tool, pinning to ^2.0 if you want the release that requires Laravel 5.8 or 6.x and PHP 7.2+. Then register the tool in your Nova service provider and run any publish or migration steps documented in the README. Because it is built on spatie/laravel-permission, that package must also be installed and configured.
- Does nova-permission-tool work with Laravel 9, 10, or 11?
- The v2.0.0 release states a ceiling of Laravel 6.x, so Laravel 9, 10 and 11 are not supported by declaration. The release notes publish no roadmap for Laravel 7+ or PHP 8 support. If you are on a modern Laravel line, this package currently offers no forward path and you should evaluate alternatives.
- Does nova-permission-tool require spatie/laravel-permission?
- Yes. The package is described as a Nova tool based on the Spatie permission package, so spatie/laravel-permission supplies the underlying roles and permissions storage and API. Your application must already have that package installed with its migrations run. The v2 platform floor is attributed to the upstream package, so its release cadence constrains which Laravel and PHP versions you can use.
- Is v2.0.0 a breaking change from 1.x?
- It is a major version bump that drops Laravel 5.7 and older, which is a hard break for applications that cannot move. The release notes describe platform constraints only and do not enumerate renamed methods, changed config keys, or altered defaults. Plan for at least some breaking changes and compare the 1.x and 2.0 code or changelog before upgrading.
- How do I assign roles and permissions to users with this Nova tool?
- The tool provides Nova resources and UI for managing roles and permissions and for assigning them to users. In practice you handle access control from inside the Nova admin panel rather than writing custom screens. The exact fields and screens depend on the package version, so review the README and the tool's resource definitions.
- Does nova-permission-tool run on PHP 8?
- The stated v2.0.0 requirement is PHP 7.2 and above, with nothing said about PHP 8 compatibility. Given the Laravel 6 ceiling, PHP 8 sits outside the declared support envelope. Test in staging before relying on it, and treat it as unsupported until the maintainer states otherwise.
- Is nova-permission-tool actively maintained, and what are the alternatives?
- It is a lightweight, low-adoption package, and the v2.0.0 notes focus on platform constraints rather than new features or a roadmap. If you need current Laravel support, consider building Nova resources directly against spatie/laravel-permission or choosing a more actively maintained Nova permission tool. Check recent commits and issue activity in the repository before committing.
- How should I roll out the v2 upgrade across multiple Laravel apps?
- Inventory every application and internal package depending on the library and record its Laravel version, PHP version and current constraint. Partition them into already-eligible apps on Laravel 5.8 or 6.x with PHP 7.2+, PHP-blocked apps, and Laravel-blocked apps; pin the blocked cohorts to the last 1.x release and record that as technical debt. Upgrade one low-traffic, well-tested eligible application first, run the full suite plus a smoke pass, then fan out to the rest.