1.2 Companies & Tenants

GamersLab is organized around a clear company → tenant hierarchy, with companies serving as the organizational anchor.

• A tenant represents a single game or environment (e.g., development, staging, production).
• Each tenant owns its own data, access policies, API keys, and visibility rules.
• A single company may operate multiple tenants across multiple titles or environments.

Tenant isolation is enforced at every layer of the system: ingestion, storage, streaming, and historical queries.

Key Rules

• By default, a user can own at most one company.
• Company access is owner-only.
• Every tenant belongs to a company.
• A user can belong to multiple tenants, each with a different role.
• Tenant roles are standardized across the platform: owner, admin, moderator, viewer.
• Inviting, removing, and updating tenant members is restricted to the owner and admin roles.

Primary Flow

1. Create a company (the creating user becomes its owner).
2. Create one or more tenants under the company.
3. Invite additional users to a tenant (note: these are studio management roles, not players).
4. The invited user accepts the tenant invitation, which activates their membership.
5. Update roles or remove members as needed (owner/admin only).
6. Transfer ownership of the company or a tenant when required.

Role Matrix

Company access:

Tenant access:

Ownership Transfer

Company ownership transfer:

• The company owner can transfer ownership to any existing user who has a first and last name set.
• The new owner does not need to be a member of the company beforehand.
• The transfer cascades across all tenants in the company:
• If the old owner held an owner membership on a tenant, they are demoted to admin.
• If the new owner already has a membership on a tenant, they are promoted to owner.
• If the new owner has no membership on a tenant, a new owner membership is created.