Best Approach for Handling Conditional Policy Inheritance Using Derived Relations
We are evaluating policy inheritance using Derived Relations in Collibra and have a scenario where the same data can be used in different product contexts. One product/asset type has royalty obligations, while another does not.
As we move toward automated policy derivation, we're facing a challenge:
Separate policy assignments can create confusion.
For example: assigning policies such as "Royalty Applies" and "Royalty Applies - Specific Product Type Only" at the data level can become confusing when those policies are inherited across multiple asset types. Consumers may see policies that do not actually apply to their specific usage context.
Excluding assets from derived relation configurations is difficult to maintain across multiple asset types and relations. It also introduces a dependency on institutional knowledge, requiring teams to remember and consistently apply the same exclusions as new asset types, relations, and governance configurations are introduced.
Has anyone implemented a scalable approach in Collibra to handle conditional or usage-based policies (such as royalties that apply only under specific product/use-case scenarios) without relying on extensive manual exclusions or duplicate policy assignments? How are you balancing policy inheritance, clarity for users, and governance coverage?
