Platform administration

Managing tenants

Superadmin only - the Tenants page isn't visible to any other role.

Creating a tenant

From Tenants → Create tenant, you provide:

Field	Notes
Name	Display name for the organization
Subdomain	3-30 characters, must be unique across the platform - this becomes `https://<subdomain>.ed-tech.pro`, so it can't be changed casually later
Plan tier	Defaults to `trial` - a label only right now, doesn't gate any features (see product docs overview)

Creating a tenant automatically provisions:

The tenant itself, in trial status
A first admin user for that tenant, with a temporary password shown once in the response - this is the only time that password is visible, so copy it before dismissing the dialog

There's no email step - passing the new admin's username and temporary password to them is a manual step today.

Self-serve signup

Anyone can also create their own tenant from the marketing homepage's "Get started" button, with no superadmin involved - see login-and-accounts.md for the visitor-facing flow. The tenant this creates is identical in every other respect (same trial status, same admin role, same Tenants table row) to one a superadmin creates here - the only differences are how the founding admin's email and password get set (real email verified by a one-time code, real password chosen immediately, no temporary one to hand over) and that there's no response dialog to copy credentials from, since the person who signed up already knows their own password.

Suspending and reactivating

Suspending a tenant blocks that tenant's users from signing in, without deleting anything. Reactivating restores access. Both are one-click actions from the Tenants table, superadmin-only.

What you can see per tenant

The Tenants table shows name, subdomain, status (active / trial / suspended), plan tier, and creation date. There's no tenant-level usage or billing view yet - subscribe to #4 progress for when that becomes relevant (the LMS is what will generate that kind of usage data).

Support's view of tenants

Support agents can also list tenants (read-only) - they need tenant names to make sense of the cross-tenant Users page they can see, even though tenant lifecycle actions (create/suspend/activate) stay superadmin-only. See docs/superadmin-access-patterns.md for the full reasoning behind what support can and can't do.