Multi-Tenant

Choose and test explicit tenant boundaries

Tenant isolation is an application design. Separate deployments, databases, schemas, or security-key-based record restrictions have different operational and security consequences. QQQ 4.0 does not provide a universal QMultiTenancyConfig switch or automatic tenant billing.

Map the authenticated user to the intended tenant and test cross-tenant denial for queries, direct record lookups, writes, exports, reports, processes, and custom endpoints. Backend variants can select settings for a backend, but selection alone does not prove tenant authorization.