Tenants
A tenant is a partition inside an organization used to separate teams, projects, or environments. Data and many operations in downstream apps (for example pipelines, collectors, and metrics) are scoped to the current tenant once you select it in the org/tenant switcher.
Organization Tenants list
On Identity Management → Tenants (or /identity/settings/tenants in embedded builds), you get a searchable table of tenants you can access with sorting and pagination as implemented in your version.
Actions (subject to organization:write and your deployment rules) typically include:
- New tenant — Opens a form for name and optional description. Names must be unique within the organization; duplicate names return a clear error.
- Edit — Update name and description for a tenant.
- Remove — Delete a tenant (with confirmation; downstream effects depend on your backend policy).
Tenant Settings (per tenant)
From the tenant list, open a tenant to reach Settings for that tenant. Route shape includes query parameters such as tenant, tenantName, orgId, and optional tab for deep–linking. Example pattern:
…/settings/tenant?tenant=<id>&tenantName=<name>&orgId=<orgId>&tab=users
If you change organization or tenant from the shell while on tenant settings, the page updates the URL and context to stay consistent, or redirects to org Identity Management when the org no longer matches.
Tabs inside tenant settings
| Tab | Purpose |
|---|---|
| Users | Users in this tenant (see Users). Invite user is available when your permissions allow. |
| Invitations | Invitations scoped to this tenant. |
| API tokens | Create and list API tokens for this tenant. |
| SSO | SSO connections at tenant scope, or a focused wizard when adding from tenant context. |
| Collector update policy | Shown only for roles that are admin or owner in the product’s permission model. Lets you set policies related to how collectors update when tied to this tenant. |
Cross-app behavior
The org/tenant selector in the nav writes organization and tenant identifiers to app context and may mirror them in local storage (for example orgId, tenantId, tenantName) so the whole shell reloads with a consistent scope after navigation or refresh.