What is the recommendation for storing raw working files coming from non Adobe platforms? | Community
Skip to main content
Vishal_Anand
Vishal_Anand
Level 5
March 3, 2026
Solved

What is the recommendation for storing raw working files coming from non Adobe platforms?

  • March 3, 2026
  • 3 replies
  • 39 views

I am running into conflicts where multiple teams working on non Adobe platforms and wish to have central repository for storing raw working files for collaboration. I wish to keep these files away from DAM to avoid cluttering. Is there any recommendation on handling these creative team’s query?

 

Storage space: ~10 TB

Best answer by AmitVishwakarma

Hi ​@Vishal_Anand ,
Don’t use AEM DAM for 10 TB of raw WIP.
Use an enterprise file store as the working area and AEM as the approved asset system of record:

  1. Keep WIP in a collaboration store
    Use SharePoint/OneDrive, Box, CC Enterprise Storage/Frame.io, or similar as the central 10 TB repository where creative teams save and version their native files and project structures.
  2. Promote only “final/approved” assets into AEM
    Define a simple rule: nothing goes into AEM until it’s approved for downstream use. Promotion can be:
    • Manual bulk upload via AEM Desktop App or Assets UI, or
    • From Adobe apps via Adobe Asset Link (if they use CC tools).
  3. Use a controlled “intake” area in AEM, not a WIP dump
    Create a small /content/dam/intake or /WIP area only for assets in review, with workflows to:
    • Apply metadata/approvals, then move to final folders, and
    • Periodically archive/clean older WIP so the DAM doesn’t get cluttered.
  4. Standardize folder & naming in the WIP store
    Agree on cross‑team folder conventions and retention (e.g., by project/campaign), so that promoting assets into AEM is predictable and scriptable later if needed.

do heavy WIP outside AEM and only check in major, approved versions to the DAM to protect performance and keep timelines clean.

https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/aem-cc-integration-best-practices

https://experienceleague.adobe.com/en/docs/experience-manager-desktop-app/using/archive/best-practices-for-v1

 

3 replies

giuseppebaglio
giuseppebaglio
Level 10
March 3, 2026

hi ​@Vishal_Anand,

The most scalable approach is to let creative teams use their preferred collaboration tools (CC storage, SharePoint, etc.) for WIP, and establish a formal ingestion workflow that promotes only finalized assets into AEM DAM — either via the AEM Desktop App (bulk folder upload) or the AEM Assets Web UI. 

For further reading, Adobe's official best practices guide is available at Experience League – AEM & Creative Cloud Integration Best Practices.

    AmitVishwakarma
    Community Advisor
    AmitVishwakarmaCommunity AdvisorAccepted solution
    Community Advisor
    March 4, 2026

    Hi ​@Vishal_Anand ,
    Don’t use AEM DAM for 10 TB of raw WIP.
    Use an enterprise file store as the working area and AEM as the approved asset system of record:

    1. Keep WIP in a collaboration store
      Use SharePoint/OneDrive, Box, CC Enterprise Storage/Frame.io, or similar as the central 10 TB repository where creative teams save and version their native files and project structures.
    2. Promote only “final/approved” assets into AEM
      Define a simple rule: nothing goes into AEM until it’s approved for downstream use. Promotion can be:
      • Manual bulk upload via AEM Desktop App or Assets UI, or
      • From Adobe apps via Adobe Asset Link (if they use CC tools).
    3. Use a controlled “intake” area in AEM, not a WIP dump
      Create a small /content/dam/intake or /WIP area only for assets in review, with workflows to:
      • Apply metadata/approvals, then move to final folders, and
      • Periodically archive/clean older WIP so the DAM doesn’t get cluttered.
    4. Standardize folder & naming in the WIP store
      Agree on cross‑team folder conventions and retention (e.g., by project/campaign), so that promoting assets into AEM is predictable and scriptable later if needed.

    do heavy WIP outside AEM and only check in major, approved versions to the DAM to protect performance and keep timelines clean.

    https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/assets/manage/aem-cc-integration-best-practices

    https://experienceleague.adobe.com/en/docs/experience-manager-desktop-app/using/archive/best-practices-for-v1

     

    Amit Vishwakarma - Adobe Commerce Champion 2025 | 16x Adobe certified | 4x Adobe SME
      avesh_narang
      avesh_narang
      Level 4
      March 9, 2026

      We’re seeing similar needs across other teams as well, especially when multiple groups work on non‑Adobe platforms and require a shared workspace. 
      To avoid cluttering the DAM with raw or work‑in‑progress assets, the recommended approach is to set up a separate, centralized repository specifically for creative collaboration.
      Typically, teams use a cloud file service (e.g., SharePoint, OneDrive, Dropbox, Google Drive, or an S3 bucket) as the “working files hub,” while the DAM remains reserved for final, approved, and published assets. 
      This keeps the DAM clean and purpose‑built, while still giving creative teams a common space to store versions, experiment, and collaborate without adding noise to the production environment.

      Additionally, we can also define guidelines/governance mechanism for what should go into the DAM vs what should remain in the working repository, so teams have clarity and a consistent process.

      Thanks 

        Terms & ConditionsAccessibility statement

        Loading footer...