KTC × museDAM / Day 2
/// Day 2 / Hands-on

museDAM
today

///
Date
Tuesday, 28 April 2026
/// Agenda

Today's session

Six blocks. Hands-on in your real workspace.

  • Recap & everyone logs in 15 min
  • Workspace tour — folders & tags live 30 min
  • Tagging — apply, batch, AI auto-tags 45 min
  • Smart folders — admin-only, rule-driven 30 min
  • museDAM × ingenOPS integration 45 min
  • Wrap & Q&A 15 min
/// Where we left off

From yesterday

Concepts covered. Today we put them into your hands.

01

Roles

Four levels. Fixed by the platform. Folder access fills the gaps.

02

Folders

Five roots. Pre-built. Walked through the why behind each.

03

Tags

Two tiers. Required where applicable. Folder-aware.

04

ingenOPS

Layouts from PSDs. Multi-size. Content feed. Render & export.

/// Today

Everyone in the museDAM workspace. Tag real assets. Build smart folders. Connect ingenOPS to museDAM.

/// Block 1+2 / 45 min

In the platform

Get logged in. Walk the live workspace together.

01

First-time login

Use "Forgot password" — your account was created server-side.

02

Walk the folders

Five roots. Already populated. Click through them together.

03

See the AI tags

museDAM has been auto-tagging assets in the background. Take a look.

/// Reminder

The "Uncategorized" folder is visible to everyone. Pick a folder before uploading anything sensitive.

/// Block 3 / 45 min

Tagging — live

Apply, batch, override. Then watch the AI fill in around you.

Three things to practice

  • Open one asset → apply Tier 1 tags from the picker
  • Select 20 assets → batch-tag Placement and Platform at once
  • Find an AI auto-tag that's wrong → override it manually

The applicability rule

  • A logo doesn't need Campaign Code or Language
  • A campaign asset needs all six Tier 1 dimensions
  • Digital Product assets skip Placement
  • The applicability table lives in the Tagging Rules doc
/// Tag groups

Placement values are grouped in the picker, not flat. Same for Platform. Easier to scan, faster to apply.

/// Block 4 / 30 min

Smart folders

The fix for the design ↔ marketing review handoff.

/// The pain today

Designer finishes a layout. Tells MarCom on Teams. MarCom emails Marketing. Marketing replies on a different thread. Files live in OneDrive. Comments scatter, versions drift.

The mechanism
A virtual folder defined by a tag rule. Assets that match the rule appear automatically. Nothing is moved or copied — just visible to whoever needs them.
Use case 1 — review handoff
Designer tags an asset "For Approval" → it lights up in the marketing team's Approval Queue smart folder. No DM, no email, no "did you see it?". Marketing tags it Approved → it falls out of the queue and into the Approved Finals smart folder.
Use case 2 — auto-routing on render
Tag by Platform (Website / Social / Banner / EDM). Each platform has its own smart folder. Renders land in the right place without anyone moving files. Solves the routing question we raised yesterday afternoon.
Live — we build the Approval Queue together
Tag rule: Asset Type = Campaign Asset · Status = For Approval. Save. Populated the moment we hit save. From now on, marketing just opens that folder.
/// Admin-only

Only System Admin and Content Manager can create smart folders. Contributors can't — that's deliberate. The taxonomy stays governed.

/// Block 5 / 45 min

museDAM × ingenOPS

Two platforms, one bridge. Three steps to wire it up.

01

API Key — organisation level

In museDAM: Settings → Settings & Members → API Key. Generate it, copy it once (it can't be viewed again). In ingenOPS: dipp Admin Panel → Edit Organization → paste the key.

02

Feature flag — organisation level

dipp Admin Panel → Edit Feature Config → toggle museDAMEnabled to true. This unlocks the integration UI for the whole org.

03

Brand folder ID — brand level

In museDAM: create an ingenOps folder at the root if it isn't there, then a sub-folder for the KTC brand. Copy the folder ID. In ingenOPS: Edit Brand → paste the museDAM Folder ID. This is where every campaign render will land.

A

Import

Pull museDAM assets into ingenOPS via the sidebar. Filter to images.

B

Export

Push ingenOPS assets to museDAM root. Non-shared assets only.

C

Render

Render a campaign straight to a museDAM folder under ingenOps/.

D

Editor

Pull museDAM assets into a campaign while editing. Lands in Content Shelf too.

/// Wrap / 15 min

By end of day

Everything you should be able to do alone tomorrow morning.

01

Log in & navigate

Find any folder. Find any tag. Find any asset.

02

Tag confidently

Apply Tier 1 in batch. Override AI when it's wrong.

03

Use a smart folder

Open the ones we built today. Suggest more for the admins to add.

04

Move between platforms

Pull museDAM into ingenOPS. Render finals back to museDAM.

/// Wednesday

Half-day until 2:30 PM. Mikhail and Jennifer on-site. Recap, next steps, ongoing cadence — and any open issues we found today.

01 / 08