Choose a tenant

For: People using the web UI.

Choose the tenant whose records you want to read or change. Cluster-wide lists show each row's tenant.

One tenant at a time

The app shows one tenant at a time, and every page reads and changes that tenant's nodes, plugins, jobs, approvals, cost and settings alone. Its address says which: https://<server>:8443/t/acme/jobs is the jobs of the tenant acme, so a link you share opens the same tenant for whoever follows it, as long as they have a role there.

• The tenant menu, at the top of the sidebar above Search, lists the tenants your account has a role in (every tenant for a cluster admin or reader), with their display names; type to narrow a long list. Choosing one loads the app again at the same section of that tenant: from a job of acme, the jobs of beta.
  The menu remains visible with one tenant, so the current tenant is always clear. The cluster name and mode appear under Orchestrator Zero above it.
• Each browser tab shows the tenant its address names, so two tabs can show two tenants. The tab's title names the tenant when your account has more than one.
• An address without a tenant, such as a bookmark from before or https://<server>:8443/jobs, opens the tenant this browser showed last, else default; one with ?tenant=acme opens acme. Links in notifications and chat posts, and the one oz0 tool call prints, name their tenant.
• A tenant you have no role in, or that does not exist, shows a page that says so and links the tenants you may open.
• Every tenant at once: a cluster admin with more than one tenant may choose Every tenant in the Tenant filter of Nodes and Plugins (?scope=all), and Every tenant and the cluster in the audit log's. Those lists then name each row's tenant, and two tenants' plugins of the same name are two rows, each opening its own. Jobs, approvals and cost have a console of their own across tenants, All tenants (below).
• Nodes that wait for a tenant: a node that joined without a join token belongs to no tenant until a cluster admin accepts it into one, so no tenant's list holds it. For a cluster admin or reader, Nodes lists such nodes above the tenant's own, and the Overview counts them as waiting; Accept into acme puts one in the tenant shown. A node's Accept always names the tenant it goes into.

All tenants

All tenants, first in the tenant menu, opens the console of every tenant at https://<server>:8443/all/: the jobs, approvals and cost of every tenant your account may read, in one list each, with each row naming its tenant. Its address is outside every tenant's (/all/, not /t/all/), since all can be a tenant's name. It has three pages, in a sidebar of their own:

• Jobs (/all/jobs): the top-level jobs that started in the period (the last 7 days unless you pick another), newest first, a page at a time, from the job summaries the server keeps of each tenant's jobs; filtered by tenant and status.
• Approvals (/all/approvals): what waits for a person in each tenant, oldest first, a page at a time, searched by what, agent or job and filtered by tenant. Each tenant's approvals are read from its own jobs, so one list reads at most 20 tenants at a time, the first 20 by name; it names the tenants it did not read, and choosing one in the Tenant filter reads it. A tenant served by another region is read in its own console.
• Cost (/all/cost): the period's cost and model calls of every tenant, by tenant, by agent (the 20 that cost most, each with its tenant) and by model or service, filtered by tenant.

Each list holds a tenant's rows only where your roles there let you read that list, as the tenant's own page would, and says which tenants it read; a tenant where you hold a role that does not, such as an agent user's, is named as left out, and a tenant you hold no role in is not named at all.

A cluster admin or reader reads every tenant. A row opens in its tenant's console, by a page load: a job at its page, an approval in that tenant's Approvals dialog to decide it there, a tenant's cost at its Cost page for the same period. The menu takes you back to a tenant at the same list.

The console of every tenant has no search, chats or settings of its own: those are a tenant's.

Cross-tenant reporting limits

The cross-tenant jobs list has tenant and status filters, but no text search, agent filter or live refresh. Cost totals cover tenant, agent, provider and model; they do not provide a per-job or per-node breakdown. Open the relevant tenant for its detailed views.

Back to Web UI.