- What is rivalex/clearance and how does it relate to spatie/laravel-permission?
- Clearance is a drop-in Livewire 4 and Flux UI admin panel for Laravel that sits on top of spatie/laravel-permission. It manages permissions, roles, guards and settings, and adds role ceilings and contextual authorization without replacing Spatie or altering its tables. Existing Spatie role and permission data and Gate/can() calls keep working.
- How do I install Clearance in a Laravel app?
- Install it with Composer and then run the package's single artisan install command, which publishes what the panel needs. The package targets PHP 8.3+, Laravel 12–13, Livewire 4 and Flux UI, so confirm those are present first. Review what the installer publishes and whether it is idempotent and re-runnable before rolling it out.
- Does Clearance modify spatie/laravel-permission tables?
- No, the package explicitly does not alter any Spatie table and acts as a presentation and policy layer on top of spatie/laravel-permission. Ceilings and contexts may still add their own migration surface, which your team would own and need to roll back if you remove the package. Verify where those definitions persist before committing.
- What are role ceilings in Clearance?
- A ceiling role declares a parent role whose permission set acts as a hard upper bound, so a child role can never exceed its parent. Clearance enforces this automatically on every save, which helps prevent delegated admins from escalating their own privileges. The ceiling model, not the UI, is the main reason to evaluate the package.
- How does contextual authorization work in Clearance?
- Clearance lets you grant a role or permission scoped to a specific model instance such as a Store, Tenant or Project. You can check it with $user->canIn(), the @canin and @hasrolein Blade directives, or ContextService outside the User model. Confirm in a spike that context checks are enforced server-side in policies or Gate, not only in the Livewire UI.
- Which Laravel, PHP, Livewire and Flux UI versions does Clearance support?
- Clearance targets PHP 8.3+, Laravel 12–13, Livewire 4 and Flux UI. It is not aimed at Laravel 10 or 11 estates, and Flux UI is a commercial component library, so licensing and procurement are part of the decision. Pin versions carefully because Livewire 4 and Laravel 13 are relatively young.
- Is rivalex/clearance production-ready?
- At the time of evaluation the package had 0 stars, 0 dependents and no third-party production usage, so it is effectively a single-maintainer package with an unproven blast radius. Treat it as a timeboxed spike candidate until you verify semver discipline, server-side enforcement and audit behavior. Forking a Livewire 4 and Flux UI panel is possible but carries real engineering cost.
- Can I use Clearance without mounting the Livewire admin panel?
- The README says you can use pre-built routes or embed individual Livewire components, but the assessment flags the headless path as an open question. Ask whether services and policies for ceilings and contexts are usable without mounting the UI. That matters if your admin surface is Inertia, React, Vue or traditional Blade.
- How does Clearance handle multi-tenancy?
- Contextual authorization is scoped to a model instance such as a Store or Tenant, but the assessment explicitly asks whether contextual means tenant-scoped and how it interacts with Spatie's team support when enabled. Test this against your tenancy model rather than assuming it maps one-to-one. Also check whether ceiling or context changes invalidate Spatie's permission cache.
- Who can access the Clearance admin panel and is there an audit log?
- Clearance is designed to be fully opt-in and configurable for exposure to admins or managers, with fine-grained clearance-{section}-write permissions per panel section. The key check is whether that exposure is enforced server-side, not just hidden at the route level. Ask for the panel's authorization check and whether role, permission and ceiling changes produce an audit trail.