Laravel Mongo Permission Filament Laravel Package

Product Decisions This Supports

• Admin surface for access control: whether to ship a first-party roles/permissions UI now versus deferring it — this package supplies Filament resources for creating roles and permissions (including assigning permissions through the form's multiselect), so the "build vs buy" question for an internal RBAC admin panel tilts toward buy/adopt.
• MongoDB + Laravel stack commitment: adopting it is a de facto reaffirmation that the product's persistence layer is MongoDB and that access control lives in webrek/laravel-mongo-permission rather than a SQL-backed package (Spatie et al.). Treat it as a signal of stack direction, not just a UI add-on.
• Filament as the internal-tooling standard: the plugin registers both resources on a panel, so it only pays off if Filament is already the chosen admin framework. It's a cheap way to validate that decision on a real, security-sensitive surface.
• Roadmap sequencing for tenancy/multi-role features: a working role/permission CRUD UI is a prerequisite for anything downstream — per-tenant roles, role templates, approval workflows, scoped permissions. Its availability de-risks those roadmap items and lets discovery focus on scoping semantics rather than plumbing.
• Runtime/platform upgrade planning: the release pins Laravel 12 / PHP 8.2+, which sets a floor for the host application and interacts directly with the app's own upgrade timeline.
• Build-vs-buy cost baseline: a maintained, tested, CI-backed plugin gives a concrete comparison point against a hand-rolled resource pair (which typically costs a few days plus ongoing Filament/Laravel upgrade churn).

When to Consider This Package

Consider adoption when:

• The application already runs Laravel 12 on PHP 8.2+ and uses MongoDB for auth/authorization data — the requirement on webrek/laravel-mongo-permission ^1.5 makes this non-negotiable.
• Filament is (or is about to become) the admin panel, and you want role/permission management inside it rather than in a separate tool.
• You need the standard CRUD lifecycle for roles and permissions quickly, and are comfortable with the package's opinionated model binding (resources are bound to the Mongo models directly).
• You want something with at least basic quality signals — a Filament/Livewire test suite, CI across PHP 8.2–8.4 and a MongoDB service, and PHPStan level 5 — as a starting point you can fork or extend.

Look elsewhere / hold when:

• Your stack is SQL-backed (MySQL/Postgres): use Spatie's permission package and its Filament plugins instead; this one is Mongo-specific.
• You are on Laravel 11 or earlier, or PHP < 8.2, or cannot adopt webrek/laravel-mongo-permission 1.5+ — v1.0.0 is an explicit cutoff, and there is no prior stable line to fall back to.
• You need rich authorization semantics out of the box — teams, per-tenant scoping, guard-specific permission sets, policy generation, audit trails. Expect to build on top of the base models.
• You require a long support horizon or a large community: this is a first stable release at v1.0.0 with a narrow maintainer surface, so plan for the possibility of forking.
• Your admin UI is not Filament (Nova, custom Blade/Livewire, Inertia) — the value here is almost entirely the Filament resource integration.

How to Pitch It (Stakeholders)

For executives: Access control is required for every customer-facing and internal workflow, and building an admin UI for it ourselves is pure overhead. This package gives us a tested, actively maintained screen for managing roles and permissions inside our existing admin panel at effectively zero build cost. It's a first stable release with automated tests and CI, so the risk is contained and reversible — and it does not add a new vendor or hosting dependency.

For engineering: v1.0.0 is the first stable cut: it adds a Filament + Livewire test suite covering role/permission creation (including the permissions select), panel resource registration, and Mongo model binding; plus GitHub Actions CI on PHP 8.2/8.3/8.4 against Laravel 12 with a MongoDB service, and PHPStan at level 5. It hard-requires Laravel 12 / PHP 8.2+ and pulls in webrek/laravel-mongo-permission ^1.5 for the legacy flat-data fix and cache invalidation — the cache-invalidation fix matters, since stale permission caches are a real production failure mode. Two caveats to flag: the Laravel 12 pin sets our app's upgrade floor, and PHPStan level 5 is a floor rather than a strong static-analysis guarantee. Treat the resources as a solid baseline to extend (scoping, tenancy, policy hooks) rather than a complete authorization solution.