PIM Manager settings · Settings > Deployment rings

Deployment rings

Key	DeploymentRings
Where	Settings > Deployment rings (managing tenant only); also on MSP > Managed tenant registry
Type	List
Default	Three rings: 0 Dev, 1 Test, 2 Broad, no tag rules
Feature	MSP: roll a change out to a first group of customers · Pro MSP

What it does

The rings that stage what a managing tenant replicates (central admins, delegations and other ring-tagged rows). A row on ring N reaches the managed tenants whose own ring is N or lower, so ring 0 gets new rows first and the highest ring is the broadest. Each ring has a name and an optional tag rule (tag:region:eu, tag:a+b for all-of, tenant:<id>) that narrows which tenants on it count. Each managed tenant still sets its own ring locally.

When set

When saved: the rings are read back, every ring picker follows at once, and a publish is requested -- the rings reach the managed tenants in the next signed bundle (within about 5 minutes). A tenant on a ring whose tag rule it does not match receives nothing ring-gated until it matches. Up to 10 rings (0-9), numbered without gaps.

When blank or default

At the default: rings 0 Dev, 1 Test and 2 Broad with no tag rules -- every managed tenant on a ring is a member of it.

Risk and how to reverse it

A tag rule that a tenant does not match withholds new and changed rows from that tenant: it keeps what it already has (nothing is retracted) but gets no updates. Removing the highest ring is refused while a tenant or a row still uses it. Reversible: edit or clear the rule and save; the next bundle delivers the held rows.

Requires

Pro (multi-tenant), on the managing tenant only. SuperAdmin to change. Tags come from the managed tenant registry.