Skip to content

Hosted Multi-Tenant

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.

Authentication And Branding

Authentication providers, callback origins, session policy, and account branding are deployment-specific. This public page intentionally does not publish provider hostnames or internal authentication configuration. Verify the deployed account configuration and data-handling commitments with the operator of the deployment.

Verification

Tenant isolation and production-readiness evidence must be verified using the private runbook for the deployment. The existence of this page is not evidence that hosted multi-tenant operation is enabled or generally available.