Manage Tenants — Platform Admin

Overview

The Tenants section lets authorized Platform Admins create, inspect, suspend, and reactivate organizations. Tenant rows and tenant-owned records live in the shared application store; isolation is enforced by tenant ownership, query filters, effective tenant context, and permission checks rather than by creating a separate database or partition for each tenant. Subscription assignment is a separate commercial workflow.

Creating a Tenant

1. Open Tenants from the dashboard navigation.
2. Click New Tenant.
3. Fill in the current form fields:
   • Display Name: The organization's visible name.
   • Legal Name: Optional legal identity.
   • Slug: The unique tenant identifier used by the application.
   • Tenant Type: The organization classification.
   • Logo: Optional managed image upload.
4. Click Create Tenant to save.
5. Complete subscription/order and tenant-admin onboarding through their dedicated workflows; the create form does not itself assign a plan or contact email.

The tenant is created in an Active state in the shared store. Tenant isolation starts from the tenant identifier and enforced ownership boundaries; no per-tenant database is provisioned.

Editing a Tenant

1. Find the tenant and open Details to inspect its current state and related tenant-scoped summaries.
2. Use the explicitly available actions, such as logo management, user onboarding, suspension/reactivation, or selected-tenant inspection.
3. The current PlatformTenantsController does not expose the previously described general Edit Tenant form for changing name/contact fields.
4. Do not treat a subscription or tenant-user action as a tenant identity edit.

Subscription plan changes are handled in the Billing section, not from the Edit Tenant form.

Activating and Deactivating Tenants

• Suspend: Sets the tenant status to suspended. The central subscription/access gate treats a non-active tenant as blocked and preserves its data.
• Reactivate: Restores a suspended tenant to active status. Subscription dates/status, account state, channel, and permissions must still pass their own checks.

Deactivating a tenant does not delete any data. All survey responses, files, and user records are retained.

Tenant Isolation

Each tenant's data is strictly isolated:

• Tenant users can only access data belonging to their own tenant.
• Platform Admins can view cross-tenant data only through explicitly authorized platform reports or a permission-checked selected-tenant context.
• No tenant can access another tenant's surveys, respondent data, or files.

Searching and Filtering

The tenant list supports:

• Search by name or identifier.
• Filter by status (Active / Inactive).
• Sort by creation date or name.

Important Notes

• The current platform tenant controller exposes no destructive delete action. Use suspension for the current non-destructive operational behavior; do not promise or attempt permanent deletion from this surface.
• Treat the slug/identifier as stable after creation because no general edit route is currently exposed.
• Active tenant status and an eligible subscription are separate gates. Recovery billing routes may remain available to an authorized Tenant Admin when plan-gated operations are blocked.