DocumentationExperience Cloud KCS

Best practices for repository architecture with Creative Cloud and AEM Assets

Last update: October 30, 2026

This article outlines Adobe’s recommended best practices for repository architecture when managing working files, approved source files, and final assets across Adobe Creative Cloud and AEM Assets.

Description description

Environment

  • Adobe Experience Manager (AEM) Assets (all versions)
  • Adobe Creative Cloud

Issue/Symptoms

  • Enterprise teams require guidance on the optimal repository architecture for managing creative production assets throughout their lifecycle, including:

    • Working files (WIP): InDesign, Photoshop, and supporting files actively edited by designers.
    • Approved working files: Final approved source packages for print/distribution teams.
    • Final assets: Exported PDFs and other deliverables for business users.

  • Two architecture options are under consideration:

    • Option 1: AEM-centric: All asset types (WIP, approved, and final) are stored in AEM Assets.
    • Option 2: Hybrid: WIP files remain in Creative Cloud during design; approved and final assets are published to AEM Assets as the governed enterprise repository.

Cause

A hybrid architecture separates high-churn creative work from governed enterprise asset management, optimizing both creative workflows and enterprise governance.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Keep active working files (WIP) in the Creative Cloud environment during the design phase.
  2. After approval, move approved source packages and final deliverables (such as PDFs) into AEM Assets.
  3. Use AEM Assets as the governed enterprise repository for approved and final assets.
  4. Use Adobe Asset Link to connect Creative Cloud applications (such as InDesign, Photoshop, Illustrator) with AEM Assets, allowing designers to browse, check out, and check in assets between Creative Cloud and AEM Assets.
  5. Define governance and operational practices in AEM Assets, including metadata schemas, permissions, approval workflows, versioning, retention, and archival rules.
  6. Review scalability and performance considerations: storing only approved and final assets in AEM reduces storage and processing overhead, while high-churn design iterations remain in Creative Cloud.

Verify that only approved and final assets are stored in AEM Assets and that creative workflows are optimized using Creative Cloud.

recommendation-more-help
experience-cloud-kcs-help-kbarticles