Organizations
The tenant directory and the organization detail view, including lifecycle actions and support sessions.
The Organizations area is where operators find, inspect, and act on tenants. It lives at
/operator/organizations, with a detail view at /operator/organizations/{organizationId}.
Directory
The directory (/operator/organizations) is a searchable, paginated table of every organization.
- Search by name.
- Sort by most urgent (triage signals first), last activity, or name.
- Filter by status: active, inactive, or suspended.
- Each row shows the organization's plan, member count, document count, last activity, status, and any triage signals: no members, stale (no recent activity), failed ingestion, or near the run cap.
- A per-row menu offers quick actions: open the tenant, suspend or reactivate it, and resend a pending admin invitation.
It is backed by operator.listOrganizations, with lifecycle actions calling
operator.suspendOrganization, operator.reactivateOrganization, and
operator.resendOrganizationInvite.
Organization detail
The detail view gathers everything about one tenant.
Header and lifecycle
- Plan badge with a menu to change the tier (
operator.updateOrganizationPlan). - Status with suspend / reactivate controls (
operator.suspendOrganization/operator.reactivateOrganization). - A link into this tenant's filtered audit history.
- A triage banner surfacing the same signals as the directory when present.
Tabs
| Tab | Shows |
|---|---|
| Overview | General health, metadata, and pending invitations. |
| Members | The organization's members with their roles. |
| Knowledge | The tenant's documents and ingestion stats. |
| Usage | Run consumption and estimated cost against the plan. |
| Conversations | Recent advisor conversations, refusals, and channel mix. |
| Audit | A link to the audit log filtered to this tenant. |
The view is backed by operator.getOrganization plus the relevant intelligence and ingestion
procedures for each tab.
Join as support
From the detail view, an operator can start a support session to see the product exactly as one
of the tenant's users sees it. Starting a session requires a reason and is recorded in the audit
log; an active session is shown with a banner and can be ended at any time. See
Authentication & multi-tenancy
for how impersonation stays attributable. Procedures: operator.startSupportSession and
operator.endSupportSession.
Plan changes, suspensions, reactivations, and support sessions all write to the audit log. Treat them as accountable operator actions.
For step-by-step procedures, see the runbooks on onboarding a tenant and plans & lifecycle.