A permission system that fits in one integer.

One number instead of a join table.

Most permission packages store one database row per role × permission × resource. That scales into a maintenance problem. A bitwise permission collapses any combination of capabilities into a single integer, checked with CPU-level math.

// one row per capability, per role, per resource
DB::table('role_has_permissions')
    ->where('role_id', $role->id)
    ->where('resource', 'leads')
    ->whereIn('permission', ['view','create','update'])
    ->count() === 3;

// one integer, resolved once per request
$access = $user->getAccess(); // 13

$access & $bits['create'] === $bits['create']; // true

A complete authorization layer, not just a bitmask.

The bitwise core is the foundation. On top of it: route protection, role cloning, self-managing menus, and an optional UI to run the whole thing without touching a migration.

From install to a protected route in four steps.

use HenryHt\BitwisePermission\Traits\HasPermissionsTrait;

class User extends Authenticatable
{
    use HasPermissionsTrait;
}

Route::middleware('bwp.permission:create')->group(function () {
    Route::post('/leads', [LeadController::class, 'store'])->name('leads.store');
});

@if(auth()->user()->canCreate())
    <a href="{{ route('leads.create') }}">New lead</a>
@endif

Everything you need to run it in production.