Solved
Asset Redundancy Best Practice
We are trying to find a way to avoid asset redundancy. E.g, an asset residing in folder A should be consumable by an account that doesn’t have permission to folder A. We would like to avoid duplicating the asset into a folder that the account has permission to. We may need to move the asset into a “public” folder to be shared across different accounts, but other than this, is there any other better way? Can you perhaps share some best practices around this topic?
