What is Subscription Lineage ?

Assets created from tasks or spaces will have subscription lineage considerations. These assets can be referred to as derived assets.

When a product is used in a task or a space and that task or space is the source of a derived asset, the product is referred to as a contributing product. Using subscription lineage enforcement, owners of contributing products can force consumers of derived assets to obtain subscriptions to their contributing product before the derived asset consumers can access consume the derived assets.

Subscription lineage is a means of controlling the downstream use and distribution of data. Subscription lineage ensures that data contained in products cannot be used to freely create and distribute downstream assets without the original data owner knowing about it and/or approving it first.

Subscription lineage has a big impact on both data publishers and data consumers.

  • If lineage is enforced on a product created from a connector, any user who consumes a derived asset or a product containing derived assets must also subscribe to the contributing product.

  • If lineage is not enforced then any user who consumes a derived asset or a product containing derived assets will NOT need to subscribe to the contributing product.

For data producers it is important to consider if you want to restrict the ability for a consumer to use any assets that are derived from your original product. This is impactful on a data consumers experience as depending on how subscription lineage is enforced (or not), a data consumer will have more or less subscription requirements when consuming any derived assets.