This page is part of the AeThex documentation system.
+
Multi-Tenancy describes how AeThex separates organizations, teams, projects, users, and resources across shared infrastructure.
-
> [!NOTE]
-
> This article is a placeholder and should be expanded.
+
<div class="docs-section-heading">
+
<h2>Tenant boundary</h2>
+
<p>The tenant boundary protects one organization or project context from another.</p>
+
</div>
-
{{PageIndex}}
+
AeThex systems should assume that users may belong to multiple organizations, teams, and projects. Every protected resource needs a clear ownership context and a permission check against that context.
+
+
## Tenant-aware resources
+
+
- [[Organizations]]
+
- [[Teams]]
+
- [[Projects]]
+
- API credentials and integrations
+
- Billing, audit, and operational records
+
- Game, studio, or lab environments
+
+
## Design requirements
+
+
1. Store tenant context explicitly.
+
2. Validate tenant access on every protected request.
+
3. Avoid relying on client-provided organization IDs without server-side checks.
+
4. Keep audit logs tenant-aware.
+
5. Make cross-tenant administration rare and traceable.
