- How do I install misaf/vendra-permission in a Laravel app?
- Install it with Composer by running composer require misaf/vendra-permission, then publish the package config and migrations and run php artisan migrate. Add the package trait to your User model and seed your initial roles and permissions. Check the README for the exact publish tags and provider registration, since this repository is a read-only subtree split.
- Which Laravel and PHP versions does misaf/vendra-permission support?
- Because it is distributed through Composer, check the require block in its composer.json for the exact PHP and illuminate/support constraints before installing. Authorization packages commonly lag new Laravel majors, so confirm the constraint set covers your target framework and PHP versions. Run composer why misaf/vendra-permission and composer outdated against your full dependency graph to spot conflicts with other auth, SSO or tenancy packages.
- Does misaf/vendra-permission use Laravel gates, policies and middleware?
- Yes, it is designed around Laravel's native authorization layer. You define roles, assign permissions, and then enforce them through guards, middleware and policies or Gate checks so the same rules apply to routes, controllers and Blade views. That centralizes access control instead of scattering ad-hoc role string comparisons across the codebase.
- Is misaf/vendra-permission a good alternative to spatie/laravel-permission?
- Both store roles and permissions and expose comparable APIs, but this package belongs to the Vendra module ecosystem and targets Vendra and modular Laravel applications. If you are not using Vendra, compare feature depth, migration footprint and maintenance cadence against spatie/laravel-permission before deciding. Diffing the table schemas and public APIs for the specific features you need is the fastest way to choose.
- What changed between v1.11.0 and v1.12.3, and is upgrading safe?
- The only available evidence is a changelog pointer covering v1.11.0 through v1.12.3, with no release notes, migration guide or advisory notice. The range contains one minor bump, 1.12.0, which by semver convention is additive, plus three patches, 1.12.1 to 1.12.3, which are conventionally defect or security fixes. Read the linked diff for each release before adopting, and if you run 1.11.x, branch and test migrations forward and back on a production-like snapshot behind a config flag.
- Can I use misaf/vendra-permission with multiple guards, such as an admin panel guard?
- Guards and middleware are core parts of the package's authorization story, so checks can be scoped to a specific guard such as an admin panel. Confirm the exact middleware aliases and guard configuration keys in the published config file for your installed version. Test each guard explicitly, because a misconfigured guard can silently widen access or lock users out.
- Does misaf/vendra-permission support multi-tenancy or team-scoped roles?
- The package is described as suitable for Laravel and Vendra applications, but the supplied material does not document a multi-tenancy or team-scoping model. If you need tenant-scoped roles, verify whether the role and permission tables and the check API accept a tenant key, or plan to scope them yourself. Raise this with the upstream maintainers rather than assuming the behavior.
- Are the role and permission migrations reversible, and what tables does it create?
- Migrations are published and run with php artisan migrate, and they create the role and permission storage used by the package. Review the published migration files for the exact table names, indexes and reversibility in your version, and run php artisan migrate:rollback on a disposable database before relying on rollback in production. The 1.12 line may add new migrations, so re-check them during an upgrade.
- How do I test role and permission checks in my Laravel test suite?
- Use Laravel's standard testing tools: authenticate with actingAs, then assert Gate::allows and the HTTP response codes for guarded routes and policy-protected actions. Seed the roles and permissions each test needs through factories or a RefreshDatabase seeder so assertions stay deterministic. For upgrade work, run the new permission checks in shadow mode alongside your existing Gate logic and diff the decisions rather than assuming equivalence.
- Is misaf/vendra-permission actively maintained, and where do I report bugs?
- This repository is a read-only subtree split of the Vendra modules, so issues and pull requests belong in the main misaf/vendra repository rather than the split. Releases such as v1.12.x show activity, but maintainer count, release cadence and the declared Laravel support matrix are not visible from the changelog pointer alone. Review the upstream commit history and open issues before depending on it in production.