I think a good start would be to separate via tags and then add subscribers to the Data Object fact sheets, maybe make a relation with organization fact sheets too.
Other than that maybe integrations with your data related tools etl, analytics etc. may be useful. 
At least without thinking too much these could be the “extra” actions that could come in handy for this.

Thanks for providing the inputs, one of the concerns while implementing Data mesh thinking in LeanIX is to be handling sub-domains impacting cross domains. Means how to handle scenarios where sub-domains shared by multiple domains?

Thanks for providing the inputs, one of the concerns while implementing Data mesh thinking in LeanIX is to be handling sub-domains impacting cross domains. Means how to handle scenarios where sub-domains shared by multiple domains?

Hi ​@ShyamBaggu 

Difficult question you have asked. In fact, it all depends on how you implemented your data mesh.
We have also started a data mesh implementation but not yet fully reflected it in leanIX yet.

As a minimum, we will create each data domain as an application. However, we wonder if we should register our data products in leanIX, since they are (or will be) also documented in our data catalog. Nothing decided yet, but an option that we might consider is an automated replication of our data products from our data catalog to leanIX.