A tenant is one isolated customer workspace: its own members, roles, groups, integrations, and policies. A Tenant Admin only ever sees their own tenant. A Super Admin operates across all of them, and this is where that happens.
The tenant list
The page lists every tenant on the deployment in a searchable, filterable table:
You can search by slug, name, or display name, and filter by status.
Switching the tenant you’re acting in
Cross-tenant admin work — managing group mappings, impersonating a user, and similar — lets a Super Admin choose which tenant the action applies to. That tenant picker lives with the surface you’re using (for example, the toolbar on the Group mappings tab and the tenant filter in the impersonation popover), rather than as a single global switcher at the top of the app.Verify before relying on it: the Tenants surface here is a management and provisioning view. Confirm the exact create/edit affordances against your deployment before documenting them for your team, as these controls are gated to platform operators.