0057-laravel-multi-tenancy

Automatic tenant isolation in Laravel is achieved by applying tenant scoping to queries so models do not require explicit tenant_id handling, ensuring data separation without manual filtering.

To preserve tenant context in queued jobs, Laravel multi-tenancy uses tenant-aware job patterns that maintain the correct tenant scope when background jobs execute, preventing cross-tenant data leaks.

Laravel multi-tenancy supports testing both central and tenant contexts by providing test infrastructure that creates isolated tenant databases, manages transactions, and runs correct base test cases by directory.

The best way to organize central versus tenanted logic is separating actions and DTOs for tenant management and tenant-specific business logic, keeping central administration distinct from tenant-scoped operations.

You can initialize tenancy by domain, subdomain, or request header, routing requests to central or tenant handlers to correctly identify and scope tenant-specific business operations.

Stancl Tenancy is needed to solve the complexity of keeping tenant isolation correct while separating central administration from tenant-scoped business operations in SaaS designs requiring database isolation per tenant.