Organizations (like mine) often operate multiple DAM and CMP instances across business units, brands, regions, or subsidiaries. Today, sharing assets between instances requires manual downloads, re-uploads, duplicate storage, or granting users access to multiple environments. This creates inefficiencies, version control risks, governance challenges, and duplicated effort.

Suggestion is to introduce a native Cross-Instance Asset Sharing & Synchronization capability that allows users to securely share, reference, or synchronize assets between DAM/CMP instances without requiring manual downloads and uploads.

Key Capabilities

• Share assets across instances through a secure "Share to Instance" action.
• Option to synchronize assets automatically, ensuring updates and new versions are reflected across connected instances.
• Preserve metadata, taxonomy mappings, permissions, renditions, and usage rights during transfer.
• Allow users to reference a source asset without duplicating files, creating a "single source of truth" across instances.
• Support sharing assets directly within CMP workflows, work requests, campaigns, and approvals.
• Provide administrator controls to define which instances can send, receive, or synchronize assets.
• Maintain a complete audit trail showing where assets originated and how they are being used across instances.

Business Value

• Reduces manual asset management and duplicate work.
• Improves governance and version control across brands and business units.
• Accelerates creative and campaign workflows.
• Eliminates the need for users to maintain access to multiple instances.
• Supports enterprise organizations managing multiple DAM/CMP environments while maintaining centralized control.
• Increases platform scalability and adoption for multi-brand and multi-company organizations.