Move a boundary to another tenant

Moving a boundary needs boundaries/tenant/admin at the root of the platform, which only the Platform Owner role has. Without it the boundary page has no Tenant tab. What a move carries across is explained in Tenants.

Move the boundary

1. Open Boundaries, choose the boundary and open its Tenant tab. It shows the current tenant and the other boundaries in it.
2. Choose Move to tenant.
3. Pick the target:
   • New tenant — a tenant that contains only this boundary.
   • Existing tenant — a tenant that already owns another boundary. Tenants have no names, so each is listed by the names of its boundaries and the first characters of its ID. The boundary's current tenant is not offered, and the option is unavailable when there is no other tenant.
4. Choose Move boundary.

On success the confirmation says how many members were added to the target tenant, how many groups were retagged and how many invitations were retargeted, and how many members could not be added, if any.

If the move is refused

The dialog stays open, and a message gives the reason. Moving to a tenant that owns no boundary, or to the tenant the boundary already belongs to, is refused, as is moving a boundary that is being deleted. When a move stopped partway, the boundary is still on its old tenant; choose Move boundary again with the same target to complete it — repeating a move is safe.

After the move

Tenant checks elsewhere on the platform follow the move within five minutes. The people who had access are now members of the target tenant as well; the old tenant keeps its own members and settings.

With the API

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

{ "tenantId": null }

null moves the boundary to a new tenant; the ID of a tenant that owns another boundary moves it there. The response lists what was carried across.