Weave Code
Nova Multi Tenant Manager Laravel Package
genealabs/nova-multi-tenant-manager
GeneaLabs Nova Multi-Tenant Manager adds multi-tenancy support to Laravel Nova: manage tenants, scope resources and queries per tenant, and let users switch tenants so your Nova admin panel stays tenant-aware.
A Laravel Nova package to manage multi-tenants.
Frequently asked questions about Nova Multi Tenant Manager
- Does genealabs/nova-multi-tenant-manager support Laravel 11 and current Nova versions?
- The only documented release signal is Laravel 11 compatibility, and the repository was archived after its last release in May 2024. That means you should verify the package constraints against your exact Nova major before installing, because there is no forward path to Laravel 12 or Nova majors released after mid-2024. If you need current Nova support, plan to fork and maintain the package internally.
- How do I install genealabs/nova-multi-tenant-manager?
- Installation is a standard Composer install with service-provider auto-discovery, config publishing, and middleware registration. The TPM assessment describes it as mechanically trivial to spike, but the real blocker is lifecycle risk because the upstream repo is archived. For production, mirror the source into an internal repository or pin a Composer VCS/path repository to a specific commit SHA instead of pointing at upstream.
- Does this package actually implement multi-tenancy for Laravel?
- No. It adds a Nova admin surface for managing tenants, domains, tenant switching, and tenant-scoped resources, but it does not supply tenant resolution, per-tenant database routing, or queue and cache separation. It is only useful if your application already has a real tenancy model. If tenancy is unbuilt, adopting this package is a UI over work still to be done, and building natively is the more realistic choice.
- How does tenant switching work in Nova Multi-Tenant Manager?
- The package gives Nova a tenant switcher and tenant-aware provisioning actions, so operators can change the active tenant context in the admin panel. Tenant switching is a privileged action and tenant scoping is an authorization boundary, so you need role boundaries and audit logging around who may switch tenants. The package does not ship audit logging, impersonation controls, or role boundaries for tenant switching; those controls are on you.
- Is genealabs/nova-multi-tenant-manager still maintained?
- The repository is archived, the last release was May 2024, and it has a single-maintainer lineage with roughly 20 stars and zero dependents. Archival means no CVE response, no issue triage, and no compatibility work, so ownership transfers to your team on day one. Treat adoption as a fork decision rather than a normal Composer dependency.
- Can I use genealabs/nova-multi-tenant-manager with Laravel 12 or a newer Nova major?
- There is no documented or forward path to Laravel 12 or Nova majors released after mid-2024. Nova is commercial and major-versioned aggressively, so pairing it with an archived extension guarantees half your stack moves and half cannot. If you must upgrade, assume you will fork the package and do the compatibility work yourself.
- How do I scope Nova resources and queries per tenant with this package?
- The package provides tenant-scoped resources and tenant-aware provisioning actions, but the TPM assessment warns that scope enforcement may live in your models rather than in the package. You need to confirm whether scope enforcement is in the package or in your application code before relying on it. A silent scope bypass is a cross-tenant exposure, so test this boundary explicitly.
- What are the alternatives to an archived Nova multi-tenant manager?
- The realistic alternatives are native Nova tooling, a maintained third-party package, or an internal build estimated at roughly two to four weeks. The TPM assessment frames the replacement-cost comparison as the main decision: owning a fork versus replacing it. Because the upstream is archived, your exit trigger and named internal owner should be written down before you rely on it.
- How should I test tenant isolation and prevent cross-tenant data leaks?
- There is no evidence of test coverage or scope-bypass hardening in the package, so you must build your own isolation tests. Focus on tenant switching permissions, resource query scoping, and provisioning actions, because those are the authorization boundaries. Also check queue serialization and Octane behavior, since the package makes unverified non-functional claims.
- Does Nova Multi-Tenant Manager support Laravel Octane, queues, and per-tenant databases?
- The TPM assessment says there is no evidence of Octane support, queue serialization handling, or per-tenant database routing. The package supplies the Nova UI layer, not the tenancy infrastructure, so database, cache, and queue separation remain your responsibility. Confirm your database, cache, queue, and Octane posture up front before adding the package to an admin-only deployment.
Weaver
How can I help you explore Laravel packages today?