Training Session Plan

You're not walking into a blank room. By the time you start the museDAM block, four things are true.

1. The space is provisioned and pre-populated

Tezign confirmed Apr 22; Jennifer finished the workspace setup Apr 26 evening. When you open the laptop:

• Team name KTC, Team ID 232 on musedam.ai
• Plan: 50 seats, 5TB year 1 / 8TB year 2, valid 2026/04/22 – 2028/04/29
• Add-on: ingenOPS (batch templating) — that's the afternoon track
• museDAM join link (sent to client): https://musedam.ai/s/1yXAEV#Join
• ingenOPS access: https://dipp.ing/ — KTC users #24–32 in MarComm and Graphic Designer departments are already invited to the KTC Brand Space
• Folder tree and tag groups are pre-created (per Jennifer last night). Don't rebuild — walk through.

2. Users are already invited — defaulted to Contributor

Jennifer's kick-off email to Sudchavee this morning confirmed everyone has been added to the museDAM KTC workspace as Contributor. Admin access has been granted (both museDAM and ingenOPS) to:

• Sudchavee.b@ktc.co.th — Digital Marketing
• Muanfun.w@ktc.co.th — Digital Marketing
• Slin.p@ktc.co.th — MarCom
• Chutima.h@ktc.co.th — MarCom

These four were created server-side, so on first login they use "Forgot password" to set their password. Tell them this before they touch a keyboard or they'll think their account is broken.

3. The folder structure and tagging rules are agreed and built

Through the Mar 11 → Apr 16 thread with Sudchavee, you've co-designed the structure. Jennifer instantiated it Sunday. Don't re-debate it on stage — narrate the live tree on screen.

4. KTC IT has whitelisted the platform

Per Jennifer's Apr 24 reply: musedam.ai, withmuse.ai, dipp.ing. If anyone can't load the site Monday morning, that's a KTC IT escalation, not yours.

Most of the prep is already done by Jennifer. Trim down to what's left.

• Verify you can log into the KTC space as Admin and see the populated workspace (folders + tags should be there)
• Spot-check that the 4 KTC admin emails are listed and have the Admin role applied
• Have 5–10 sample assets ready to drag in. Use realistic naming: KTC_Promotion_2-02_v1.jpg, Agoda_Hero_KV.png, etc.
• Open three tabs side-by-side: KTC museDAM (Admin view) / KTC museDAM (Contributor view, incognito) / museDAM Help Center (musedam.ai/en-US/help) for fallback
• Skim the museDAM Role Permissions Notion page Jennifer shared (link) so the Contributor / Admin / Owner specifics are fresh
• Have an answer ready for "What pixel size is In-store / Branch POP?" — it's the one ingenOPS format Jennifer didn't pre-set, so it'll surface in the afternoon

KTC side, based on the email thread + space-provisioning list:

• Sudchavee Banjobdee — Head of Digital Marketing Division. Primary counterpart, decision-maker. Will have detailed governance questions.
• Muanfun Wisitwanichkul ("K. Muan") — Digital Marketing
• Pranaya Nithananon — Digital Marketing
• Tosapong Rangkawara — Digital Marketing
• Varitta Phatanarajta — Digital Marketing
• Sarinda Sukhumkietsupahong — added to thread Apr 24
• Slin P. — MarCom (space owner)
• Chutima Huabkhunthod — MarCom (owns Brand Assets, knows existing asset organization deeply)
• Plus other team members invited via the link

Roughly: a Digital Marketing core, a MarCom partner team, and likely a Design contingent that'll show up Tuesday for the layout workshop.

The order matters: roles → folders → tags → assets is "container before content". Trying to upload before they understand who can see what produces awkward questions you don't want.

Objective: Sudchavee and team understand the role model well enough to assign their team — and know what they can and can't delegate.

The actual museDAM role ladder

Four named roles in the English UI, with three additional Members sub-variants used mostly for partners/agencies. This is what the team will see in the platform — no fabricated names.

Four things only System Admin can do

These matter for handoff: (1) delete the team, (2) transfer ownership, (3) promote anyone to Content Manager / Admin, (4) toggle member invitations on/off. Everything else a Content Manager can do too.

Folder-level overrides — the visibility mechanism

A team-level role is the default. Within a Shared folder, the folder owner can grant individual collaborators tighter or looser rights. Critical visibility rule from the Feishu 3.4 doc: Members, Contributors, and Content Managers can only see folders they've been added to as collaborators. The System Admin sees everything. So visibility is governed by who's been added to each folder, not by role alone — that's how you isolate Marketing's WIP folder from MarCom even though both teams are in the same workspace.

Anticipated questions (have these answers loaded)

• "Can MarCom and Marketing be separate workspaces?" (raised Mar 26) — museDAM does not have native sub-workspace isolation. Single team space, differentiated through (a) folder-level permissions per individual on the Team Plan, or (b) department-level permissions on the Enterprise Plan add-on. Recommend the layered model below: Layer 1 open, Layer 2 restricted to the campaign team, Layer 3 external share-link only.
• "How do we control who can approve assets?" — Approval = the asset moving into 02_CAMPAIGN/[Campaign]/04_Approved_Final. So approval permission = who can move/upload to that folder. Recommend: only System Admins + Content Managers + designated Contributors on that specific folder.
• "What happens to assets when someone leaves?" — Their uploaded assets stay in the workspace. Their account loses access. System Admin / Content Manager can reassign asset ownership. Show the Operation Log briefly.

Three-layer access model — the recommendation for KTC

• Layer 1 — open by default (whole-team visibility): 01_SHARED_LIBRARY, 04_ARCHIVE, and every 02_CAMPAIGN/[Campaign]/04_Approved_Final. All 30+ users get at least view/download.
• Layer 2 — restricted by folder (team-specific work): 02_CAMPAIGN/[Campaign]/01_Brief_Reference through 03_Working restricted to the assigned campaign team only — brief docs and WIP shouldn't be visible to broader Marketing until they reach Final. 03_DIGITAL_PRODUCT restricted to UX/UI designers + IT.
• Layer 3 — external (partners + agencies): use share links to specific 05_Distribution_Pack folders only. Assign View & Download (Role 06) so they can pull but not upload or browse the wider library. Share links can be time-limited — solves the asset-expiry concern directly.

Current state — what Jennifer pre-applied

• System Admin (museDAM) + Admin (ingenOPS): Sudchavee, Muanfun (Digital Marketing), Slin, Chutima (MarCom)
• Contributor (default for everyone else): rest of Digital Marketing, MarCom, Graphic Designers, UX/UI designers

For deep details on what each role can do, refer to Jennifer's museDAM Role Permissions Notion page.

Recommended end-of-day adjustments — both directions

Jennifer flagged the Contributor default isn't necessarily right. The proper slate, mapped against KTC's onboarding-checklist team list:

Don't force commitment on the spot. Show the screen, walk Sudchavee through the slate, and lock the changes during the end-of-day check-in. The downward adjustments (Marketing team → Members) and upward adjustments (Sudchavee, Muanfun → System Admin; Sarinda → System Admin) are the only ones that need to move; everything else can stay.

Objective: They walk out understanding why the structure looks the way it does — enough that when they hit a new asset and ask "where does this go?" the answer is obvious.

The five roots, with the reasoning

01_SHARED_LIBRARY

Anything reusable across campaigns. The notable subfolder is 06_COMPLIANCE_COPY (added at KTC's request) for responsible-lending text, T&C archives, disclaimers in TH and EN. Single source of truth for legal copy. Worth flagging — it solves a real risk: campaigns shipping with stale legal text.

02_CAMPAIGN

Structured Year > Month (JAN, FEB, …) > Campaign Name. The Month layer was KTC's Apr 10 request. Inside each campaign: 04_Approved_Final and within that, 06_Merchant_Variations (separates the master KV from the batch outputs going to specific merchants). The "Distribution Pack" folder was removed; it's now inside Approved_Final.

03_PARTNER_ASSETS

Organized by partner name: Agoda, Klook, Visa, etc. There's a [Partner Name] placeholder folder for onboarding new partners — show how to clone it. Industry category (Dining, Travel, Shopping, Health) is not in the folder hierarchy here; it's a tag dimension. Deliberate decision to avoid duplicating partners across category folders.

03_DIGITAL_PRODUCT

Each product gets its own folder, and inside every product the same UI Screens / Banners / Icons / Components & References substructure repeats. Predictable, easy to navigate.

04_ARCHIVE

Campaign Type > Year > Campaign Name (KTC's preference; lets them retrieve all "promotion 5%" campaigns across years quickly).

Three platform mechanics to demo here

• Three folder types: Personal folders (each user's own space) · Shared folders (the team library — what KTC will live in; any System Admin / Content Manager / Contributor can create one) · Smart folders (rule-driven, auto-populated; only System Admin and Content Manager can create). Demo one Smart folder: "all assets tagged Approved AND placement = LINE this month". Useful for cross-campaign collections without copying.
• Folder permissions inheritance. A Contributor is by default Contributor on every shared folder they're added to, but the folder owner can downgrade or upgrade specific people on that folder. Visibility rule (Feishu 3.4): Members, Contributors, and Content Managers only see folders they've been added to as collaborators — System Admin sees everything. Show this on a Marketing folder (give MarCom View only) — and tie it back to Sudchavee's Mar 26 governance question.
• Folder ownership = delete authority. The folder owner can delete the folder + all sub-folders + all assets inside. A sub-folder owner can delete that sub-folder + its assets. An asset owner can only delete their own assets. So the owner of 02_CAMPAIGN/[Campaign] effectively controls that whole campaign's deletability.

Naming convention — open item for the room

KTC asked to revise the system on Apr 10 but hasn't sent the final version yet. Confirm the naming convention live or schedule it for Wed morning. Suggested anchor format: KTC_[Partner]_[CampaignType]_[CampaignName]_[Variant]_v[N] — but pause for their input.

Objective: Team understands the two-tier tagging model, knows when each tier applies, and can use the tag picker without thinking.

Tier 1 — mandatory on approved finals

The 6 dimensions, with KTC's Apr 16 adjustments baked in:

Note: Campaign Code was dropped from Tier 1 — the file naming convention + folder structure already capture it, no need to double-up.

Tier 2 — optional, governed

Only apply when it adds real signal:

• Category (Industry) — Dining, Travel, Shopping, Health, etc. Now elevated to be the primary way to search across industry types (since Partner is folder-based, not tag-based).
• Content Theme — only tag manually if the brief specifies a theme that wouldn't be visually obvious to AI auto-tagging (e.g. specific cultural reference). Otherwise let the AI handle it.
• Designer — only when the designer differs from the uploader; otherwise the platform's auto-captured "Created By" field covers it.

What was removed (worth saying explicitly so the room knows)

• Partner as a tag dimension — gone, because partner is now the folder. Two sources of truth would create drift.
• Usage Rights / Expiry as a tag — use the platform's built-in expiry date field on the asset. Tag values can't be auto-evaluated by date; the field can.

Demo sequence (8 min)

1. Show the tag library backend — Owner / Admin / Can Edit can manage; everyone else can view + apply
2. Demonstrate tag groups — group "Placement" tags together so the picker shows them grouped, not as a flat list of 50 things
3. Apply tags to a single asset via the asset detail panel
4. Batch-apply tags — select 10 assets, right-click → Batch edit → add Placement = LINE. Critical demo because this is what they'll do daily.
5. Filter by tag group — show how Marketing can find "all 16:9 LINE-placement Travel-category assets approved in March"

Anticipated questions

• "Can we add new tags later?" — Yes, anyone Can-Edit and above. Encourage a brief governance step (Admin reviews tag-group additions weekly to avoid sprawl).
• "What if AI auto-tagging gets it wrong?" — Manual override always wins. Show how to remove an AI tag.

Objective: Everyone can get a file into the system through whichever path fits their actual workflow.

Four upload paths

Show all four briefly so people pick the one that fits how they actually work:

1. Drag-and-drop files or folders into the asset list (most common)
2. Top-right + button → "Upload local file" (keyboard people)
3. Clipboard paste (Cmd/Ctrl+V) — paste an image directly. Game-changer for designers iterating on screen captures.
4. Resume on crash — if upload dies mid-stream, no need to delete the partial files. The system resumes from the last successful chunk. Worth explicitly mentioning because it eats anxiety.

Then call out the other ingestion paths in passing — they'll find them later if useful: mobile collection (iOS/Android app), browser inspiration collector plugin, Eagle migration.

Asset operations to demo

Recap the four things they should be able to do this afternoon without help:

1. Log in and switch between team workspaces
2. Find a folder by structure, find an asset by tag
3. Upload and apply Tier 1 tags
4. Share a batch externally

Then plant two threads for Wednesday:

• Naming convention finalization — they owe you the revised system from their Apr 10 message
• Role assignment confirmation — they confirm the Owner/Admin/Editor slate you proposed

• First-login friction (the 4 admins). Sudchavee, Muanfun, Slin, Chutima were created server-side. They have to use "Forgot your password" on first login or they'll think their account is broken. Tell them this up front, before they touch a keyboard.
• "Contributor" default may not match seniority. Jennifer flagged this explicitly — she defaulted everyone to Contributor without knowing the seniority of each name. End-of-day with Sudchavee is the moment to lock the right slate; if you skip it, you'll be cleaning up later.
• The "Uncategorized" gotcha. People will drag-drop without picking a folder. Catch the first instance and turn it into a teaching moment instead of a quiet leak.
• Tier 1 fatigue. Six dimensions sounds like a lot. The applicability table is the answer — keep that visible whenever you're talking tags.
• Naming convention drift. Without their final convention, the demo files use your convention. Be explicit: "this is a placeholder; your team will finalize Wed."
• In-store / Branch POP sizing (afternoon, ingenOPS). Jennifer didn't preset this format — she wasn't sure how to convert the spec to pixels. When it surfaces this afternoon, decide live with Sudchavee rather than improvising.
• Wednesday 2:30 PM cutoff. Per Jennifer's Apr 24 reply, training extends only until 2:30PM Wed. Anything not closed by then becomes follow-up. Watch the clock Tuesday afternoon.

These were owed to KTC. Status as of Monday morning, with Jennifer's Sun-night work folded in:

1. Updated Folder Structure doc — covered live by demo (folders are pre-built); written doc still to send if Sudchavee asks for a reference
2. Updated Tagging Rules doc (Apr 16: Channel→Placement, Platform → Tier 1, Campaign Code dropped) — same: covered live, written doc on request
3. User Roles & Permissions doc — Jennifer's Notion page covers it: museDAM Role Permissions
4. Workspace Structure recommendation — implicit in the populated workspace; explicit narrative happens during the Folders block
5. Training prep materials — Jennifer's kick-off email this morning serves as the pre-read; access details + admin list are in there
6. Confirm Contributor → adjusted role assignments — end-of-day check-in with Sudchavee (per Jennifer's note)
7. In-store / Branch POP pixel spec — open for ingenOPS afternoon
8. Naming convention finalization — KTC owed this since Apr 10; due Wed