Monday.com CRM 操作教學

Monday.com CRM System Guide

Vivid Gaming & Ideal Gaming　
CRM 各看板使用規範與連動邏輯

Vivid Gaming & Ideal Gaming　
CRM Board Usage & Workflow Logic

工作區與版面總覽

Workspaces & boards

我們的 monday 分成四個工作區（第一層），每個工作區底下有各自的版面（第二層）。點版面看它的操作說明。

Our monday is split into four workspaces (level 1), each holding its own boards (level 2). Click a board to open its guide.

3 步驟上手

Get going in 3 steps

這個網站怎麼用

How to use this site

• 左側選單＝我們 monday 的四個工作區（Onboarding／Product／AM／Marketing），每個底下是它的看板。點看板看操作說明。Left sidebar = our four monday workspaces (Onboarding / Product / AM / Marketing), each with its boards. Click a board for its guide.
• 右上角可切換 中文 / EN 與 深色 / 淺色。Top-right toggles 中文 / EN and dark / light.
• 上方搜尋框可用關鍵字找任何內容；主流程頁有每個工作區的流程圖。Search box up top finds anything by keyword; the Main Flow page has a flow diagram for each workspace.
• 卡住了就看 常見問題 FAQ，或問你的主管。Stuck? Check the FAQ or ask your manager.

先懂幾個 monday 名詞

A few monday words first

• Workspace 工作區 — 最上層分類（我們有 4 個）。Board 看板 — 一個主題一張大表。Workspace — the top-level grouping (we have 4). Board — one big table per topic.
• Group 群組 — 看板裡的分段。Item 項目 — 表格裡的一列（一款遊戲、一檔促銷）。Subitem 子項目 — item 底下的細項。Group — a colored section in a board. Item — one row (a game, a promo). Subitem — a breakdown under an item.
• Column 欄位 — 每一直行記一種資訊。Status 狀態 — 有顏色的膠囊，點一下選；顏色代表進度（灰＝未開始、藍＝完成）。Column — each column holds one kind of info. Status — a colored pill you click; color shows progress (grey = not started, blue = done).

找到你的團隊

Find your team

點你所屬的團隊，看你會用哪些看板、從哪一個開始。點看板名稱可直接跳到它的教學。

Click your team to see which boards you use and where to start. Click a board name to jump to its guide.

不管哪一團，第一週都要做

Everyone, in week one

• 用公司 email 登入 vividgamingmalta.monday.com，並裝好桌面與手機 App。Sign in at vividgamingmalta.monday.com with your company email; install the desktop and mobile apps.
• 走一遍你團隊的看板路徑（上面那格），每個看板頁讀一次。Walk your team's board path (above) and read each board's guide once.
• 把 我的工作 My Work 設成每天起點；學會用 @ 在項目裡標記別人。Make My Work your daily start; learn to @-mention people on an item.
• 看不到某個看板？找 PMO Claire 開權限。Can't see a board? Ask PMO Claire for access.

點開下面每個工作區，看它的目的、說明與流程圖。預設收合，點一下展開。

Open each workspace below to see its purpose, details and flow diagram. Collapsed by default — click to expand.

如何找到我的工作

How to Find My Work

我的工作不一定會直接出現在左側選單，通常要先點左側的「更多」展開才看得到。
很多人找不到，就是因為沒有展開「更多」。

“My Work” may not appear directly in the left menu — usually you must first click “More (⋯)” on the left to reveal it. Most people who can’t find it simply haven’t expanded “More”.

1. 在左側選單點「更多」展開。In the left menu, click “More (⋯)” to expand it.
2. 選「我的工作」。建議在它上面按右鍵釘選 / 加到最愛，下次就能直接一鍵點開。Pick “My Work”. Tip: right-click to pin / favorite it so it’s one click next time.

它不屬於任何單一看板，是專屬於你個人的彙整頁——每個人看到的內容都不一樣（只會是自己的工作）。

It doesn’t belong to any single board — it’s your personal aggregated view, so everyone sees only their own work.

※ 此為示意圖，客戶名稱皆為範例；完成的項目預設不會出現在清單中，讓你專注在還沒做完的事。

※ Illustrative preview — client names are examples; completed items are hidden by default so you can focus on what’s still open.

為什麼要用它

Why use it

• 一頁看完你在所有看板上被指派的工作，不用逐一打開看板。
• 可依個人檢視習慣，至右上角變更模式進行分組。
• 可直接在這裡更新狀態、點進該項目，省去切換看板的時間。
• 只顯示你自己的工作，不會被別人的項目干擾。

• See all your assigned work across every board on one page — no need to open each board.
• Can be grouped by your personal viewing preference, accessible via the top-right corner.
• Update statuses or jump into an item right from here, without switching boards.
• Shows only your own work — you won’t be distracted by other people’s items.

看板操作權限

Board Editing Rights

依工作區分。「可操作」是該看板的主要編輯團隊；其餘人多半仍可查看。

Grouped by workspace. "Can Edit" is the board's main editing team; others can usually still view.

系統與權限管理

System & Access

看板操作之外，Monday 的系統設定、自動化與權限開通由以下團隊負責：

Beyond board editing, Monday's system setup, automations, and access provisioning are handled by:

1設置目的Purpose

所有客戶流程的起點——潛在／既有客戶的公司基本資料主檔。BD／AM 在這裡建立與維護客戶資料，並從這裡觸發後續洽談（Lead）；資料會同步到 Leads & Deals、Integration 等看板。

The starting point for every client process — the master profile of a prospective/existing client. BD/AM create and maintain it here and trigger the deal flow (Lead) from it; data syncs onward to Leads & Deals, Integration and more.

2可操作人員Who can edit

• BD team主要維護者：建立客戶、判斷 Route 與類型、觸發 Lead。Primary owner — creates clients, sets Route & type, triggers leads.
• AM team共同建立與維護客戶基本資料。Co-creates and maintains client profiles.

3欄位說明簡介Fields at a glance

Route 整合路徑：

Route integration path:

4自動化邏輯及使用方式Automation & how to use

• 一鍵觸發 Lead：把 Add VVD Lead／Add IDG Lead 設為 Approached，系統自動在 Leads & Deals 建立對應 Studio 的 Lead 並連結，同步下列欄位。One-click Lead: set Add VVD/IDG Lead to Approached and the system auto-creates & links a Studio Lead in Leads & Deals, syncing the fields below.
• Route 自動處理 Via：選 Direct／Reverse 自動把 Via 設為 NA；選 Via 會清空 Via 提示你填，未填會通知相關人。Route auto-handles Via: Direct/Reverse sets Via to NA; Via clears it so you fill it, and notifies if left empty.
• Live Stage 自動分組：設為 Go Live 時，客戶自動移到看板下方的 Go Live 群組。Live Stage auto-grouping: set to Go Live and the client moves to the Go Live group.
• Outlook 收發信整合：與客戶往來的信件記錄在看板。Outlook email sync: emails with the client are logged on the board.

使用方式：新增客戶 → 填必填欄位 → 要開始洽談時，依 Studio 點對應按鈕觸發 Lead：

How to use: add a client → fill the required fields → when ready to engage, trigger a Lead by Studio:

Add VVD Lead

開啟 VVD Studio 的洽談

Start a VVD Studio deal

Add IDG Lead

開啟 IDG Studio 的洽談

Start an IDG Studio deal

觸發後，以下資料自動連動至 Leads & Deals：

These fields then auto-sync to Leads & Deals:

5注意事項Cautions

• 必填欄位：Client、Route、Is Aggregator、Is Operator（Route = Via 時 Via 也必填）。Required: Client, Route, Is Aggregator, Is Operator (plus Via when Route = Via).
• Add Lead 按下會自動建立 Leads & Deals 項目，不要重複觸發或手動另建。Add Lead auto-creates the Leads & Deals item — don't trigger twice or create it manually.
• Jurisdiction 用 ISO alpha-2 國碼（如 MT、TW、CW）。Use ISO alpha-2 codes for Jurisdiction (e.g. MT, TW, CW).

1設置目的Purpose

客戶洽談進度追蹤：從 Lead（潛在）→ In Discussion → Deal（成交）。部分資料由 Profile 連動。在這裡按 Kickoff 啟動法務與整合流程；成交後系統自動在 Client 建檔。

Deal-progress tracking: Lead → In Discussion → Deal. Some data syncs from Profile. Pressing Kickoff here starts the legal & integration process; a closed deal auto-creates the Client record.

2可操作人員Who can edit

• BD team主要維護者：填優先級、合約類型、洽談階段，按 Kickoff。Primary owner — fills priority, agreement type, stage; presses Kickoff.
• AM team共同追蹤洽談進度。Co-tracks the deal progress.
• 紅色欄位鏡射自 Profile（Route／Via／類型／Studio），回 Profile 改。Mirrored from Profile — edit in Profile.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 階段自動填日期：狀態變 Lead 自動填 Lead Date、變 Deal 自動填 Deal Date。Dates auto-stamp: Lead sets Lead Date, Deal sets Deal Date.
• Kickoff 啟動流程：按下 Initiate，系統自動在 Legal WIP for BD/AM、Legal WIP for Legal、Integration WIP 建立項目並連結、同步下列欄位。Kickoff starts the flow: Initiate auto-creates & links items in Legal WIP for BD/AM, Legal WIP for Legal and Integration WIP, syncing the fields below.
• 成交自動建檔：狀態變 Deal 時，系統自動在 Client 看板建立正式客戶。Deal auto-files: reaching Deal auto-creates the client on the Client board.
• Live Stage 自動分組：設為 Go Live 移到 Go Live 群組。Live Stage auto-grouping: Go Live moves it to the Go Live group.

5注意事項Cautions

• Priority 必填——它會同步到 Legal 與 Integration，影響下游排序。Priority is required — it syncs to Legal and Integration and drives their ordering.
• 紅色欄位（Route／Via／類型／Studio）要改請回 Profile。Change red fields (Route / Via / type / Studio) back in Profile.

1設置目的Purpose

BD／AM 為每個客戶處理合約前置文件：NDA、Agreement、DD（我方審／客戶審）。資料在 Leads & Deals 按 Kickoff 後自動建立（每客戶 4 列）。選好處理方式、上傳檔案後，轉交法務團隊接續。

BD/AM handle each client's pre-contract documents: NDA, Agreement, DD (we review / client review). Rows are auto-created after Kickoff on Leads & Deals (4 per client). Set the handling, upload files, then hand off to Legal.

2可操作人員Who can edit

• BD team主要維護者：為四項文件選 Status、上傳檔案。Primary owner — sets Status for the four docs and uploads files.
• AM team共同處理合約文件。Co-handles the documents.
• 紅色欄位Client／CID／Studio／Deal Owner 鏡射自 Leads & Deals，唯讀。Client / CID / Studio / Deal Owner mirror from Leads & Deals, read-only.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 自動建立資料：Leads & Deals 按 Kickoff 後，系統自動在此為每個客戶建立 4 列（NDA／Agreement／DD×2）。Auto-created rows: after Kickoff on Leads & Deals, 4 rows per client (NDA / Agreement / DD×2) are created here.
• VVD 合規保護：VVD 客戶的文件若被設為 Not Required，系統會自動改回 Not Started 並通知你（僅 IDG／DD client review 例外）。VVD compliance guard: if a VVD client's doc is set to Not Required, the system reverts it to Not Started and notifies you (IDG / DD client review excepted).
• 轉交法務：把 Status 設為 Process by Legal 並附檔，即交給 Legal WIP for Legal 接續。Hand off: set Status to Process by Legal with the file attached to pass it to Legal WIP for Legal.
• 使用方式：每個客戶 4 項各選 Status → 需要的上傳檔案 → 轉法務。How to use: pick a Status for each of the 4 docs → upload files as needed → hand to Legal.

5注意事項Cautions

• Process by Legal 一定要附上檔案，否則法務無從處理。Attach the file with Process by Legal or Legal can't act on it.
• 看板是空的？先確認 Leads & Deals 的 Kickoff 已觸發。Board empty? Confirm Kickoff was triggered on Leads & Deals.

1設置目的Purpose

法務團隊專用看板。BD／AM 在 Legal WIP for BD/AM 把文件設為 Process by Legal 後，狀態自動拋轉到這裡，由法務逐項推進 NDA、Agreement、DD（我方審／客戶審）至 Completed。

The Legal team's dedicated board. Once BD/AM mark a doc Process by Legal, its status flows here for Legal to advance NDA, Agreement and DD (we / client review) to Completed.

2可操作人員Who can edit

• Legal team主要維護者（Legal Owner），推進各文件狀態。Primary owner (Legal Owner) — advances each doc's status.
• BD ／ AM用子項目 Comment 溝通，不改法務狀態。Communicate via subitem comments; don't change legal status.
• 紅色欄位Client／Studio／CID／Priority／Deal Owner 鏡射自 Leads & Deals。Mirror from Leads & Deals.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 收到自動初始狀態：BD/AM 選 Process by Legal 後，對應欄位自動變為初始狀態（見下表）。Auto initial status: after BD/AM select Process by Legal, each field auto-sets to its starting status (table below).
• 狀態改變自動填日期並在子項目留記錄。Status changes auto-stamp the date and log a subitem note.
• 四項都完成 → Completeness 自動 Total Completed，項目自動移到 Completed 群組。All four done → Completeness auto Total Completed and the item moves to the Completed group.

使用方式：依實際進度把每項推進到 Completed（不需要則 Not Required），必要時用子項目 Comment 與 BD/AM 溝通。

How to use: advance each item to Completed (or Not Required), and use subitem comments to coordinate with BD/AM.

5注意事項Cautions

• Completeness 是系統自動算的，不要手動改。Completeness is automatic — don't set it manually.
• 進度與卡點請寫在子項目 Comment from Legal，BD/AM 在自己的看板就看得到。Post progress/blockers in the Comment from Legal subitem; BD/AM see it from their board.

1設置目的Purpose

技術整合看板，記錄每個客戶從整合準備、串接測試、驗收到正式上線（Go Live）的完整時程與各階段日期。上線後的 Live Date 會鏡射到 Client 的 Go Live Date，是整條客戶流程的終點。

The technical integration board — tracks each client from preparation through testing and acceptance to Go Live, with a date per stage. The Live Date mirrors into the Client board's Go Live Date, closing the whole client flow.

2可操作人員Who can edit

• Tech team主要維護者（RD／TCS + Integration Owner），推進 Integration Status。Primary owner (RD/TCS + Integration Owner) — drives Integration Status.
• AM參與最終驗收與上線（Assignee = AM 階段）。Handles final acceptance & go-live (Assignee = AM stages).
• 紅色欄位Client／CID／Studio／Priority／Route／Via 鏡射自 Profile／Leads & Deals。Mirror from Profile / Leads & Deals.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 階段自動填日期／指派：切換 Integration Status 時，系統自動填對應日期並設定 Assignee（見下表）。新項目自動預設 0. Not started。Stages auto-fill dates/assignee: changing Integration Status auto-stamps the date and sets Assignee (table below). New items default to 0. Not started.
• Testing 依 Route 指派：Direct → TCS、Reverse → RD。Via 客戶狀態跟隨串接廠商（例：500 Casino 跟 Hub88）。Testing routes by Route: Direct → TCS, Reverse → RD. Via clients follow the vendor (e.g. 500 Casino follows Hub88).
• Live Date 鏡射到 Client：上線日期會自動出現在 Client 看板的 Go Live Date。Live Date mirrors to Client: the go-live date appears on the Client board's Go Live Date.
• 逾期自動提醒：若卡在某階段超過設定天數（例：整合開始 +19 天），系統自動通知相關人。Overdue reminders: if a stage stalls past a set number of days (e.g. Integration Start +19), the system notifies.

5注意事項Cautions

• 日期多為自動，切換 Status 就會填，不用手動補（Integration Finished 等少數例外才手填）。Dates are mostly automatic — changing Status fills them; only a few (e.g. Integration Finished) are manual.
• Via 客戶的整合狀態要跟串接廠商一致，不要自行超前。Via clients should mirror the vendor's status — don't get ahead of it.
• 卡關請設 98. On Hold 或 99. Blocked 並在 Notes 註明，避免逾期提醒誤發。If stuck, set 98. On Hold or 99. Blocked and note why, so overdue reminders don't misfire.

1設置目的Purpose

追蹤每一款遊戲從美術素材到正式上線（Go Live）的交付執行。PMO 在這裡管理交付階段、上線季度與日期，並透過子項目把每一步做細；同時是 Roadmap、Certification、Pre-release 等看板的資料樞紐。

Tracks every game from art assets to Go Live. PMO manages the delivery stage, launch quarter and dates here, breaking each step down via subitems; it's also the hub that links Roadmap, Certification and Pre-release.

2可操作人員Who can edit

• PMO team主要維護者，負責交付階段與所有紫色欄位。Primary owner — drives delivery stages and all editable (purple) fields.
• AM ／ BD檢視遊戲進度，不直接編輯。View game progress; don't edit directly.
• 紅色欄位鏡射／連結自其他看板，任何人都不在此改。Mirrored/linked from other boards — not edited here by anyone.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 階段自動展開子項目：Delivery Stage 進到某階段時，系統自動建立該階段對應的交付步驟（子項目）並設好狀態，不用一個個手開。Stages auto-create subitems: when Delivery Stage advances, the matching delivery steps are created as subitems with their status pre-set.
• 子項目回填與通知：子項目 Step Status 改變時自動填入 Notification／Completed Date；改到 Pending Review 會自動寄信通知。Subitem auto-fill & notify: changing a subitem's Step Status auto-fills Notification/Completed Date; hitting Pending Review emails a notification.
• 全部完成自動推進：某項目的子項目全部完成時，系統自動把該遊戲的階段狀態更新為完成。Auto-advance: when all subitems are done, the game's stage status flips to complete automatically.
• Certification ETA 自動鏡射自 Certification WIP，會跟著更新，不用手填。Certification ETA mirrors from Certification WIP and updates automatically.

使用方式：五個交付步驟依序從 Not Started → In Progress → Completed（不需要的步驟設 Not Required）：

How to use: move each of the five steps from Not Started → In Progress → Completed (set Not Required for steps you skip):

5注意事項Cautions

• 紅色欄位不要改：Certification ETA、Roadmap、Certification WIP、Pre-release List、Request by GD 都是鏡射／連結，要改去來源看板。Don't edit red fields: Certification ETA, Roadmap, Certification WIP, Pre-release List and Request by GD are mirrored/linked — change them at the source board.
• Item ID 系統自動產生（G-xxxxx），不要手動改。Item ID is auto-generated (G-xxxxx) — don't edit it.
• 不需要的交付步驟請設 Not Required，不要留 Not Started，否則會被當成未完成卡住自動推進。Set steps you skip to Not Required (not Not Started), or they'll block the auto-advance as if unfinished.

1設置目的Purpose

遊戲發行的季度規劃表——決定每款遊戲落在哪一季上線、排定 Release Date。多數遊戲基本資料鏡射自 Game Delivery／Certification WIP，這張表專注在「排期」這件事。

The quarterly release plan — decides which quarter each game launches in and sets the Release Date. Most game details mirror from Game Delivery / Certification WIP; this board is all about scheduling.

2可操作人員Who can edit

• PMO teamOwner（Matt），排定季度、Release Date 與 Demo 狀態。Owner (Matt) — sets quarter, Release Date and demo status.
• AM ／ BD檢視發行排程。View the release schedule.
• 紅色欄位鏡射自 Game Delivery／Certification WIP，不在此改。Mirrored from Game Delivery / Certification WIP — not edited here.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• Finalize Roadmap 按鈕：按下去，系統自動把該遊戲的 Release Date 設為「今天」——用來定案發行日。所以要確認今天就是定案日再按。Finalize Roadmap button: pressing it auto-sets that game's Release Date to today to lock the launch. Only press it when today is the date you mean to commit.
• 自動連結 Certification WIP：新增遊戲時，系統用項目 ID 自動把它連到對應的認證項目。Auto-links Certification WIP: a new game is auto-connected to its certification item by matching item ID.
• 鏡射欄自動更新：GameID、Studio、Certification ETA 由來源看板帶入，不用手填。Mirrors update automatically: GameID, Studio and Certification ETA come from source boards.
• 使用方式：新增／連結遊戲 → 設定 Quarter → 確認 Demo → 排定後按 Finalize 定案。How to use: add/link the game → set Quarter → check the demo → press Finalize to lock the date.

5注意事項Cautions

• Finalize 會蓋掉 Release Date 為今天——排程未定不要亂按。Finalize overwrites Release Date with today — don't press it before the schedule is set.
• 紅色欄位不可在此改：GameID、Studio、Certification ETA 要回來源看板改。Don't edit red fields: change GameID, Studio, Certification ETA at their source boards.

1設置目的Purpose

所有促銷活動的主看板，分成 Active（進行中）與 Finished（已結束）。每檔促銷從建立、備妥後台（RD）與素材（Marketing）、上線到結束，都在這裡追；結束後在 Promo Analysis 看成效。

The master board for promotions, split into Active and Finished. Each promo is tracked here from setup — backend (RD) and creative (Marketing) readiness — through launch and end; results are then reviewed in Promo Analysis.

2可操作人員Who can edit

• AM team主要維護者，每檔促銷指派一位 Responsible AM。Primary owner — each promo gets one Responsible AM.
• Marketing依 Request 提供素材（Marketing Assets）。Delivers creative via the request (Marketing Assets).
• RD後台設定完成後確認 RD Set Up。Confirms RD Set Up once the backend is ready.

3欄位說明簡介Fields at a glance

Promotion Type 常見分類：

Common Promotion Type categories:

4自動化邏輯及使用方式Automation & how to use

• 新增自動處理：建立促銷時，自動把項目名稱設為 Promo ID，並在 Promo Analysis 建立對應分析項目。On create: the item is auto-named by Promo ID and a matching item is created in Promo Analysis.
• Promo Period 自動組成：填 Start／End Date 後自動生成時間軸。Promo Period auto-builds from Start/End Date.
• Request Form 連結自動產生：依狀態自動帶出 Marketing／RD 的需求表單連結。Request-form links auto-generate for Marketing/RD based on status.
• End Date 到期：系統自動把活動移到 Finished 群組並寄出通知信。On End Date: the promo auto-moves to Finished and a notification email goes out.
• 使用方式：新增促銷 → 選類型、填起訖日期 → 送 RD／Marketing 需求 → 兩個關卡變 Yes → 上線 → 到期自動結束。How to use: add a promo → pick type & dates → send RD/Marketing requests → both gates hit Yes → launch → auto-ends on End Date.

5注意事項Cautions

• 兩個關卡都要 Yes：RD Set Up 與 Marketing Assets 都備妥，促銷才算就緒。Both gates must be Yes: a promo is ready only when RD Set Up and Marketing Assets are both done.
• 每檔促銷務必指派 Responsible AM，責任才清楚。Always assign a Responsible AM so ownership is clear.

1設置目的Purpose

追蹤每款遊戲從送測到認證完成：送哪個實驗室（Testlab）、預計完成日（Certification ETA）、目前到哪一步。這裡填的認證 ETA 是 Game Delivery、Roadmap 的資料來源。

Tracks each game from lab submission to certified: which lab (Testlab), the expected date (Certification ETA) and current progress. The ETA entered here is the source for Game Delivery and Roadmap.

2可操作人員Who can edit

• PMO team主要維護者，填 Testlab、Certification ETA、進度與分案子項目。Primary owner — fills Testlab, ETA, progress and per-case subitems.
• AM ／ BD檢視認證進度。View certification progress.
• 紅色欄位連動自 Game Delivery／Roadmap，不在此改。Linked from Game Delivery / Roadmap — not edited here.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 新增自動建立分案子項目：新增一款遊戲時，系統自動依市場建立認證子項目（如 Italy、Spain、Portugal）並指派 Case Owner。Auto-creates case subitems: adding a game auto-creates per-market certification subitems (e.g. Italy, Spain, Portugal) with a Case Owner.
• 填 ETA → 自動 In Progress：一設定 Certification ETA，主狀態自動變 In Progress。Set ETA → auto In Progress: setting a Certification ETA flips the status to In Progress.
• ETA 到期 → 自動 Completed：Certification ETA 當天，系統自動把狀態改為 Completed。ETA arrives → auto Completed: on the ETA date, status auto-flips to Completed.
• 自動連結 Roadmap（項目 ID 對應）；Certification ETA 也自動同步到 Game Delivery。Auto-links Roadmap (by item ID); the ETA also syncs to Game Delivery.
• 使用方式：選 Testlab → 填 Certification ETA → 用子項目分案追每個實驗室 → 完成後確認狀態。How to use: pick Testlab → set ETA → track each lab via subitems → confirm status when done.

5注意事項Cautions

• Certification ETA 只在這裡填一次——它會自動同步到 Game Delivery 與 Roadmap，別在那兩邊重複改。Enter Certification ETA here only — it syncs to Game Delivery and Roadmap; don't re-edit it there.
• ETA 到期會自動變 Completed：若實際還沒過，記得調整 ETA，否則狀態會提前變完成。Status auto-completes on the ETA date — if it isn't actually done, update the ETA or it'll flip early.
• 該款用不到的實驗室，子項目 Certification Status 設 Not Required。For labs that don't apply, set the subitem's Certification Status to Not Required.

1設置目的Purpose

集中管理所有正式合作中客戶的公司主檔——狀態、優先級、負責人（BD／AM）、公司登記資料、付款與商業條件。這是 AM 維護客戶關係，以及後續促銷、遊戲發行的資料源頭。客戶要正式上線（Go Live）後才在此建檔，前段洽談仍在 Leads & Deals。

The master record for every active client company — status, priority, owners (BD/AM), registration details, payment and commercial terms. It's the source of truth AM uses to manage relationships and drive later promos and releases. A client is filed here only after Go Live; earlier deal-making stays in Leads & Deals.

2可操作人員Who can edit

• AM team主要維護者，可編輯所有欄位。Primary owner — can edit every field.
• BD負責的客戶可協作填寫（含商業條件）。Collaborates on their own clients (incl. commercial terms).
• PMO可檢視全部欄位（含機密 Commercial Terms）。Can view all fields (including confidential Commercial Terms).
• 其他團隊僅檢視基本資料，Commercial Terms 不開放。View basic info only — Commercial Terms hidden.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 新增自動預設：建立一筆新客戶時，系統自動把 Client Status 設為 Active、Client Priority 設為 Medium；不符再手動改。Defaults on create: a new client is auto-set to Client Status = Active and Client Priority = Medium; adjust manually if needed.
• Go Live Date 自動鏡射：日期來自 Integration WIP 的 Go Live，串接完成後自動出現，不要手動改（要改去 Integration WIP）。Go Live Date mirrors automatically from Integration WIP; it appears once integration is done — don't edit it here (change it in Integration WIP).
• 使用方式：新增項目 → 以公司縮寫命名 → 連結 Leads & Deals 與 Integration WIP → 補齊公司登記與付款資料 → 指派 BD／AM。How to use: add an item → name it by company abbreviation → link Leads & Deals and Integration WIP → fill registration & payment details → assign BD/AM.

5注意事項Cautions

• Jurisdiction 只能填 alpha-2 國碼（例：MT、GB、CW），不要打全名。Jurisdiction takes alpha-2 codes only (e.g. MT, GB, CW) — not full names.
• Go Live Date 唯讀：這裡改不動，要改到 Integration WIP。Go Live Date is read-only here — edit it in Integration WIP.
• 正式建檔請用真實公司名稱（示意圖用 Operator／Aggregator 代稱僅為教學）。Use the real company name when filing (the preview uses generic aliases for teaching only).

1設置目的Purpose

客戶端的聯絡窗口名單。系統寄信、發通知時，收件人就是從這裡撈；每位聯絡人可設定要收哪幾類通知。與 Client 看板相連。

The client-side contact list. When the system sends mail or notifications, recipients are pulled from here, and each contact can choose which notice types they receive. Linked to the Client board.

2可操作人員Who can edit

• BD與 AM／PMO 共同維護聯絡人名單。Maintains the contact list with AM / PMO.
• AM主要維護客戶窗口與通知設定。Primary owner of contacts and notification settings.
• PMO可編輯、協助維護。Can edit and help maintain.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 新增自動預設：建立聯絡人時自動把 Active 設為 Yes。Default on create: a new contact is auto-set to Active = Yes.
• Notifications 決定收件人：其他看板（如 Promo、Art Request）觸發寄信時，依這裡勾選的分類撈聯絡人。分類填錯就會漏發或錯發。Notifications drives recipients: when other boards (Promo, Art Request…) send mail, contacts are pulled by these tags. Wrong tags → wrong recipients.
• Outlook 收發信整合：與聯絡人往來的信件會自動記錄在看板，方便追蹤。Outlook email sync: emails to/from contacts are logged on the board automatically.
• 使用方式：新增聯絡人 → 填聯絡方式 → 勾 Notifications 分類 → 標一位 Main Contact → 連到 Client。How to use: add a contact → fill channels → tag Notifications → mark one Main Contact → link to Client.

5注意事項Cautions

• Notifications 一定要填正確——系統照它發信，錯了就漏發或錯發。Keep Notifications accurate — the system mails by these tags, so errors misroute mail.
• 窗口離職或不再往來時，把 Active 改成 No，不要直接刪，保留歷史。When a contact leaves, set Active = No rather than deleting — keep the history.
• 每家公司只標一位 Main Contact = Yes。Mark only one Main Contact = Yes per company.

1設置目的Purpose

促銷結束後的成效分析。促銷一結束，資料自動搬到這裡，用「活動前同天數」當 Baseline，比對活動期間的 Players／Bets／GGR，由 AM 判定這檔促銷的成效。

Post-promo performance analysis. When a promo ends, its data moves here automatically; the same number of days before the promo is used as a baseline to compare Players / Bets / GGR, and AM judges the outcome.

2可操作人員Who can edit

• AM team檢視數據、判定 Promo Outcome 並補 Comments。Reviews the figures, sets Promo Outcome and adds Comments.
• 系統／整合自動帶入數據與 % 變化，多數欄位不需手動。Pulls figures and % changes automatically; most fields aren't manual.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 促銷結束自動搬入：Promo 端活動結束時，系統自動在此建立對應分析項目並鏡射基本資料。Auto-imported on end: when a promo ends, a matching analysis item is created here with mirrored details.
• Baseline 自動計算：公式取「活動前同天數」作為對照區間。Baseline auto-computes: a formula takes the same number of days before the promo as the comparison window.
• % Change 自動算：數據帶入後，Players／Bets／GGR 的成長幅度自動更新。% Change auto-calculates for Players / Bets / GGR once figures load.
• 使用方式：等資料進來（Status → Completed）→ 檢視三大指標 → 填 Promo Outcome 與 Comments。How to use: wait for data (Status → Completed) → read the three metrics → set Promo Outcome and Comments.

5注意事項Cautions

• 多數欄位鏡射自 Promo，要改基本資料回 Promo 改。Most fields mirror from Promo — edit core details there.
• Status = NoData 代表沒抓到數據，需要 ReRun 重新抓取，別急著判定成效。Status = NoData means figures didn't load — ReRun before judging the outcome.
• Promo Outcome 要人工判定，不是自動；看完數字再給結論。Promo Outcome is a manual call — decide after reading the numbers.

1設置目的Purpose

促銷活動的後台（RD）設定：要做哪種玩法、成本怎麼算、設定進度、截止日。需求由 AM 在 Promo 看板的 RD Request Form 填寫並送出，表單資料會自動帶進本看板；RD 收到後完成後台設定，完成後回饋到 Promo 的 RD Set Up Confirm 關卡。

Backend (RD) setup for a promo: which mechanic, how cost is calculated, setup progress and the deadline. The request is filled by AM via the RD Request Form on the Promo board, and the form data flows into this board automatically; RD then does the setup, which clears the RD Set Up Confirm gate on Promo.

2可操作人員Who can edit

• AM team在 Promo 的 RD Request Form 填寫並送出需求，表單資料自動帶入本看板（不直接在此看板打字）。Fills & submits the request in the RD Request Form on Promo; the data flows in here automatically (not typed on this board).
• RD收到帶入的需求後完成後台設定，並更新 RD Set Up Status。Receives the carried-in request, does the backend setup and updates RD Set Up Status.

3欄位說明簡介Fields at a glance

Promotion Item 玩法類型：

Promotion Item mechanics:

4自動化邏輯及使用方式Automation & how to use

• 表單資料自動帶入＋通知：AM 在 Promo 送出 RD Request Form 後，系統自動在此建立項目、把表單資料（玩法、Details、成本等）帶入，並寄通知信給 RD（依 Fixed／Percentage 成本分不同通知）。Form data carried in + notify: after AM submits the RD Request Form on Promo, the system auto-creates the item here with the form data (mechanic, Details, cost) and emails RD (different notices for Fixed vs Percentage-based cost).
• 狀態自動分組：RD Set Up Status 改變時，項目自動在 Uncompleted／Completed 群組間搬移。Auto-grouping: changing RD Set Up Status moves the item between Uncompleted / Completed.
• 完成回饋 Promo：狀態 Completed 後，Promo 的 RD Set Up Confirm 關卡才算過。Feeds back to Promo: once Completed, the promo's RD Set Up Confirm gate passes.
• 使用方式：AM 在 Promo 填 RD Request Form 送出 → 資料自動帶入本看板 → RD 依帶入內容完成後台設定 → 把 Status 改 Completed（回饋 Promo）。How to use: AM fills & submits the RD Request Form on Promo → data carries in here → RD completes the backend setup → sets Status to Completed (feeds back to Promo).

5注意事項Cautions

• 選了 Promotion Item 就要填對應的 Details 欄，別漏。Fill the matching Details field for whichever Promotion Item you pick.
• Status 一定要改到 Completed，否則 Promo 那檔促銷會卡在未過關。Set Status to Completed or the promo stays blocked on its gate.
• 客戶、Games、日期等鏡射自 Promo，不在此改。Client, Games and dates mirror from Promo — not edited here.

1設置目的Purpose

給特定客戶「搶先上架」的遊戲清單：哪款遊戲、給哪個客戶／市場、什麼時候開、狀態到哪。遊戲基本資料鏡射自 Game Delivery／Roadmap／Certification WIP，AM 只補客戶端資訊與狀態。

The list of games offered to a specific client ahead of general launch: which game, which client/market, when it opens and its status. Game details mirror from Game Delivery / Roadmap / Certification WIP; AM just adds the client-side info and status.

2可操作人員Who can edit

• AM team主要維護者：填 Pre-release Client／Market／Date 與狀態。Primary owner — fills Pre-release Client / Market / Date and status.
• 紅色欄位鏡射自 Product 三看板，不在此改。Mirrored from the three Product boards — not edited here.

3欄位說明簡介Fields at a glance

Pre-release Status：

Pre-release Status:

Pending 排定中 → Opened 已對客戶開放 → Released 已上線；不做了設 Cancelled。

Pending → Opened (available to the client) → Released; set Cancelled if dropped.

4自動化邏輯及使用方式Automation & how to use

• 資料自動鏡射：Game ID、Planned Release Date、Certification ETA 由 Game Delivery／Roadmap／Certification WIP 連動帶入，會自動更新。Auto-mirrored: Game ID, Planned Release Date and Certification ETA come from the three Product boards and update automatically.
• 本看板無其他自動化，狀態由 AM 手動維護。No other automations — AM maintains the status manually.
• 使用方式：從 Game Delivery 連結遊戲 → 填 Pre-release Client／Market／Date → 隨進度更新 Status。How to use: link the game from Game Delivery → fill Pre-release Client / Market / Date → update Status as it progresses.

5注意事項Cautions

• 紅色欄位不可在此改：Game ID、Planned Release Date、Certification ETA 要回來源看板改。Don't edit red fields: change Game ID, Planned Release Date and Certification ETA at their source boards.
• 一定要填 Pre-release Client 與 Market，否則不知道搶先給了誰。Always fill Pre-release Client and Market so it's clear who got early access.
• 不做了請設 Cancelled，不要直接刪。If dropped, set Cancelled rather than deleting.

1設置目的Purpose

AM 針對特定客戶／遊戲向 Marketing 提出的美術素材需求（縮圖、截圖、Banner、季刊 Game Book）與進度追蹤。每筆用 Task ID 連到 Marketing 的 Request By AM，直接鏡射對方進度。

AM's art-asset requests to Marketing for a client/game (thumbnails, screenshots, banners, quarterly game book) with progress tracking. Each links by Task ID to Request By AM in Marketing and mirrors its status.

2可操作人員Who can edit

• AM team提出需求、指派 Responsible AM、追蹤進度。Raises requests, assigns Responsible AM, tracks progress.
• Marketing在 Request By AM 端製作，進度鏡射回本板。Produces on the Request By AM board; status mirrors back here.

3欄位說明簡介Fields at a glance

Art Request Type 素材類型：

Art Request Type:

4自動化邏輯及使用方式Automation & how to use

• 新增自動處理：建立需求時，自動以 Task ID 命名，並產生一條預先帶入 Studio／Task ID／Requester 的 Marketing Request Form 連結（改 Responsible AM 會自動重算連結）。On create: auto-named by Task ID, with a Marketing Request Form link pre-filled with Studio / Task ID / Requester (re-built when Responsible AM changes).
• 狀態自動分組：Art Request Status 改變時，項目自動在 Uncompleted／Completed 群組間搬移。Auto-grouping: changing Art Request Status moves the item between Uncompleted / Completed.
• 跨看板鏡射：用 Task ID 連到 Request By AM，對方的 Task Status／Due Date 會鏡射過來。Cross-board mirror: linked by Task ID to Request By AM; its Task Status / Due Date mirror in.
• 使用方式：新增需求 → 選 Type、填客戶與遊戲、指派 AM → 點自動產生的表單連結送給 Marketing → 看鏡射狀態追進度。How to use: add a request → pick Type, fill client & games, assign AM → open the auto-generated form link to submit to Marketing → track via the mirrored status.

5注意事項Cautions

• 用系統產生的表單連結送需求，它已帶好 Task ID，Marketing 才對得上。Submit via the auto-generated form link — it carries the Task ID so Marketing can match it.
• 進度看鏡射的 Linked Task Status（來自 Marketing），不要只靠自己那格猜。Read progress from the mirrored Linked Task Status (from Marketing), not just your own field.
• Task ID 系統自動產生，不要手動改。Task ID is auto-generated — don't edit it.

1設置目的Purpose

每款新遊戲要給行銷準備的素材：宣傳影片、素材包、Game Sheet，以及完成度追蹤。由 Game Delivery 連過來，每款遊戲一筆。

The marketing deliverables each new game needs — promo video, asset pack, game sheet — plus completeness tracking. Linked from Game Delivery, one row per game.

2可操作人員Who can edit

• Marketing team主要維護者：製作素材、放連結、更新兩個進度欄。Primary owner — produces assets, adds links, updates the two progress columns.
• 紅色欄位GameID、Studio 鏡射自 Game Delivery，不在此改。GameID and Studio mirror from Game Delivery — not edited here.

3欄位說明簡介Fields at a glance

4自動化邏輯及使用方式Automation & how to use

• 狀態自動分組：Game Completeness 變 Total Completed 時項目自動移到 Completed 群組；改回 In Progress／Not Started 則回 Uncompleted。Auto-grouping: when Game Completeness hits Total Completed the item moves to Completed; back to In Progress / Not Started returns it to Uncompleted.
• GameID／Studio 自動鏡射自 Game Delivery。GameID / Studio auto-mirror from Game Delivery.
• 使用方式：從 Game Delivery 連結遊戲 → 製作影片與素材 → 放連結 → 兩個進度欄更新到完成。How to use: link the game from Game Delivery → produce the video & assets → add links → advance both progress columns to done.

5注意事項Cautions

• 兩欄都要完成：Video Status 與 Game Completeness 都到位，這款的行銷素材才算齊。Both columns must be done: assets are ready only when Video Status and Game Completeness are both complete.
• 素材連結放對欄位（Link／Asset pack／Game Sheet），別全塞一格。Put links in the right fields (Link / Asset pack / Game Sheet), not all in one.
• GameID、Studio 鏡射自 Game Delivery，不在此改。GameID and Studio mirror from Game Delivery — not edited here.

1設置目的Purpose

AM 向 Marketing 提出的各類素材需求（Banner、影片、Email、Landing Page 等），透過 Marketing Request Form 提交、集中追蹤製作。Marketing 接單、指派 Task Owner、交付；用 Task ID 連到 Art Request 與 Promo。

AM's asset requests to Marketing (banners, videos, email, landing pages…), submitted via the Marketing Request Form and tracked here. Marketing takes them, assigns a Task Owner and delivers; linked by Task ID to Art Request and Promo.

2可操作人員Who can edit

• Marketing team主要維護者：接需求、指派 Task Owner、製作、填 Assets Path、更新狀態。Primary owner — takes requests, assigns Task Owner, produces, fills Assets Path, updates status.
• AM透過表單送需求並追蹤進度。Submits requests via the form and tracks progress.

3欄位說明簡介Fields at a glance

Asset Type 素材類型：

Asset Type:

4自動化邏輯及使用方式Automation & how to use

• 新增自動通知：表單送出、建立需求時，系統自動寄信通知 Marketing 設計團隊（含完整需求細節），並用 Task ID 自動連到 Art Request 與 Promo。Auto-notify on submit: a new request auto-emails the Marketing design team (full request details) and auto-links to Art Request and Promo by Task ID.
• 交付自動通知：Marketing 一填 Assets Path，系統自動寄信通知提出者「素材已完成」。Delivery notice: filling Assets Path auto-emails the requester that assets are ready.
• 狀態自動分組：Task Status 改變時，項目自動在 Uncompleted／Completed 群組間搬移。Auto-grouping: changing Task Status moves the item between Uncompleted / Completed.
• 使用方式：收到需求 → 指派 Task Owner → 製作 → 完成後填 Assets Path 並把 Task Status 改 Completed。How to use: receive request → assign Task Owner → produce → fill Assets Path and set Task Status to Completed.

5注意事項Cautions

• 需求越清楚越快：提需求時填好 LOGO、Language、Sizes、Text Content 與 Style Reference。Clearer = faster: fill LOGO, Language, Sizes, Text Content and a Style Reference when requesting.
• 完成一定要填 Assets Path——這是觸發「交付通知信」的關鍵，漏填提出者就收不到。Always fill Assets Path when done — it triggers the delivery email; skip it and the requester isn't notified.
• Task ID 是跨看板對應的關鍵，不要亂改。Task ID links the boards together — don't change it.

找不到答案？聯絡對象

Still Stuck? Who to Contact