The full asset loop

Pull brand assets from museDAM into ingenOPS, render the campaign with a platform-aware filename, push the renders back to museDAM. Smart folders sort the output automatically — no manual filing.

museDAM

Brand library

Brand core, photography, partner assets, digital product UI — already organized in your five root folders. Source of truth for everything that goes into a campaign.

PULL — IMPORT

ingenOPS

Campaign builder

Layout + content feed → render with platform-aware filename. Each render bakes the platform name into the file itself.

RENDER — PUSH

museDAM

05_INGENOPS_RENDERS/

Dedicated landing zone for everything ingenOPS produces. Auto-created sub-folder per campaign. Smart folders pivot off this scope.

/// Example render filename

KTC_Songkran_LINE_1080x1920_TH_v01.jpg

Smart folders — Name-filtered

Smart folder

Website

Name contains
"Website"

Smart folder

Social

Name contains
"FB" / "IG"

Smart folder

LINE

Name contains
"LINE"

Smart folder

Banner

Name contains
"Banner"

Smart folder

EDM

Name contains
"EDM"

/// Step 1 — Pull

From the ingenOPS editor, designers pull museDAM assets directly into the Content Shelf. Filtered to images. Folder browser supported. Lands in the campaign workspace, ready to drop into layouts.

/// Step 2 — Render

Build the campaign. On render, configure the filename pattern to embed the platform identifier (Website / Social / LINE / Banner / EDM) — that one token is what makes the smart folders work.

/// Step 3 — Push

Renders auto-push to 05_INGENOPS_RENDERS/ in museDAM. ingenOPS creates a sub-folder per campaign. No manual upload — the integration handles it.

/// Step 4 — Smart folders sort

Five smart folders, each with one rule: Name contains "[platform]". The moment a render lands, it appears in the matching platform folder. Same asset shows in multiple smart folders if the filename matches multiple patterns.