Skip to content
AlphaBase
HomeDocs

Hosted Multi-Tenant

Hosted organization setup guidance for secure multi-tenant use.

This page is intentionally high-level for public docs.

When a deployment enables hosted multi-tenant operation:

  • tenant isolation controls are enabled by platform policy
  • workspace access is scoped by org membership and roles
  • security contracts and signing details are kept in private operator runbooks

What Operators Should Do

  1. Create tenant organizations and workspace structure.
  2. Enforce least-privilege role assignments.
  3. Enable audit retention and periodic access reviews.
  4. Run tenant isolation validation before release promotion.

Account Login Branding

Social OAuth behavior is deployment-configured. The current runtime permits a configured Supabase project URL by default; operators can require branded OAuth by setting ALPHABASE_REQUIRE_BRANDED_SUPABASE_OAUTH=1 and providing ALPHABASE_SUPABASE_AUTH_URL (or the configured Supabase URL). Do not infer which sign-in methods are enabled from this public page; verify the deployed account configuration and auth provider settings.

Verification

Run your release verification gates:

Terminal window
bun run test:tenant:isolation
MODEL=<provider/model> bun run test:launch:gate