# Nested Third-Party Relationships — Changelog
[ 
Changelog
](/changelog) June 10, 2026 [ TPRM ](/changelog?tag=TPRM) 
# Nested Third-Party Relationships

Third parties can now nest to any depth, not just one level of sub-vendor, so subprocessors of subprocessors are representable. 

[Third-party relationships](/docs/product/third-party-management) used to support exactly one level: a vendor and its direct sub-vendors. Anything past that had no home in the data model.

Third parties can now nest to arbitrary depth. Each third party carries a reference to its parent, and the console, API, and [CLI](/docs/developers/cli/commands/thirdparty) (prb third-party list --level N) all understand levels beyond the first. If your vendor’s subprocessor has its own subprocessor, that relationship is now representable instead of flattened.

This also cleans up how sub-vendor links work generally: they’re just a parent reference on the third party itself now, instead of a separate link/unlink relationship to manage.