Multi-Tenancy
Multi-Tenancy describes how AeThex separates organizations, teams, projects, users, and resources across shared infrastructure.
Tenant boundary
The tenant boundary protects one organization or project context from another.
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
- Store tenant context explicitly.
- Validate tenant access on every protected request.
- Avoid relying on client-provided organization IDs without server-side checks.
- Keep audit logs tenant-aware.
- Make cross-tenant administration rare and traceable.