Tenant Approval Workflow
Tenants are registered by orchestrators and may require Global VSA approval before they become operational. The approval workflow gives SuperAdmins control over which organizations can use the platform.
Tenant Lifecycle
Every tenant progresses through a defined set of status transitions:
pending_approval ──→ active ──→ suspended ──→ active (reactivated)
│
└──→ rejected
| Status | Description |
|---|---|
pending_approval | Newly registered by an orchestrator, awaiting SuperAdmin review |
active | Approved and fully operational |
suspended | Temporarily disabled by a SuperAdmin |
rejected | Registration denied |
Approving a Tenant
- Navigate to the tenant detail page. You can reach it from:
- The Tenants list in the sidebar
- The Recent Pending Registrations table on the Dashboard
- The Associated Tenants table on an orchestrator detail page
- Review the tenant information: name, ID, orchestrator, and contact email.
- Click the Approve button (green, with a checkmark icon).
- Confirm the action in the dialog that appears.
- The tenant status changes to
active, and the orchestrator will receive updated feature flags on its next sync.
Rejecting a Tenant
- Navigate to the tenant detail page.
- Click the Reject button (red, with an X icon).
- Confirm the action in the dialog.
- The tenant status changes to
rejected.
Suspending an Active Tenant
If you need to temporarily disable a tenant that is already active:
- Navigate to the active tenant's detail page.
- Click the Suspend button (red, with a ban icon).
- Confirm the action in the dialog.
- The tenant status changes to
suspended.
warning
Suspending a tenant does not immediately disconnect their edges. The suspension affects feature flag sync on the next polling interval (up to 5 minutes). During this window, existing edge configurations continue to operate normally.
Reactivating a Suspended Tenant
- Navigate to the suspended tenant's detail page.
- Click the Reactivate button (green, with a checkmark icon).
- Confirm the action in the dialog.
- The tenant status returns to
active, restoring full functionality on the next sync cycle.
Important Notes
- All status changes require confirmation via a dialog to prevent accidental actions.
- Status transitions are logged for audit purposes.
- Only the transitions shown in the lifecycle diagram above are valid. For example, a
rejectedtenant cannot be directly approved -- it must be re-registered by the orchestrator.