BoundariesUsers

The boundary page

What each tab of a boundary's page shows and who sees it, the statuses a boundary can have, and the CLI commands for boundaries.

Open Boundaries in the sidebar of the portal at https://portal.example.com. The list shows every boundary you hold a role in — on the boundary itself or on anything inside it — with its name, slug, status and creation date. Choose a boundary to open its page.

Tabs

Tab	What it shows
Overview	Display name, slug, tenant (its ID) and creation date. Below them a read-only Single sign-on card lists the tenant's email domains, whether each is verified, and its identity providers. The card is shown to those who may read the boundary's role assignments (`rbac/members/read`); platform administrators configure it — see Single sign-on.
Projections	The clusters the boundary is projected into, each with its status. Adding one is a platform administrator task — see Projections.
Resources	Every resource in the boundary, grouped by resource group, with its type, status and creation date. Resource groups without resources are left out.
Tenant	Only shown to platform administrators holding `boundaries/tenant/admin` at the root: the tenant, the other boundaries in it, and Move to tenant — see Move a boundary to another tenant.
Deployment Sources	The source-control accounts connected to the boundary for automated deployments — see Deployment sources.
Network	What the boundary's network blocked, who talks to whom, and the Can this reach that? check — see Find out why a connection is blocked. Shown to those holding `boundaries/network/read`; Owner, Contributor and Reader all have it.
Crosslink	Connectivity between the boundary's clusters — see Crosslink.
Operations	The platform operations run in the boundary — creating and deleting resource groups, adding projections, and operations on the resources inside — with a search on resource name and filters for status and period. Choose one to see its steps and messages.
Access Control	Role assignments on the boundary itself. This is where people are given access — see Members and tenants.

Statuses

Status	Meaning
Active	The boundary is in use. A boundary is Active from the moment it is created.
Deleting	A platform administrator is deleting the boundary. If the deletion stopped partway the boundary stays Deleting until it is repeated — see Delete a boundary.

The status filter on the list also offers Provisioning and Suspended. Nothing on the platform sets them today, so a boundary you see is Active or Deleting.

Renaming

The portal has no rename. The display name can be changed through the API, which needs boundaries/manage on the boundary (Owner and Contributor have it):

http

PATCH https://api.example.com/boundaries/<boundary-id>
Content-Type: application/json

{ "displayName": "Production EU" }

The slug does not change, and neither do the namespace names built from it.

With the CLI

bash

stsh boundary list
stsh boundary get my-boundary
stsh boundary projections --boundary my-boundary
stsh boundary use my-boundary

stsh boundary use makes a boundary the default for later commands in the current context, so --boundary can be left out.