Following up on this to ask a similar question. If we have custom fonts as part of our styles for landing pages, what's the best mechanism to handle to avoid CORS issues? Looks like the Experience Cloud DAM loads from https://instanceNameHere.experiencecloud.adobe.com/content/dam/foo which is not th...

Wondering if there is a documented approach to achieve this outcome? I see documentation for Campaign Classic to mask PII from certain user groups within the interface but not for ACS.