保密責任 · Confidentiality Obligation — 必讀
所有員工均有嚴格的保密責任。以下資料屬公司機密,未獲授權不得以任何形式披露、複製、轉移或分享予任何外部人士:
All employees are bound by strict confidentiality obligations. The following constitutes confidential information that must not be disclosed, copied, transferred, or shared with any external party without authorisation:
- ·客戶資料、供應商資料及合作品牌資料 / Customer, supplier, and brand partner data
- ·公司財務數據、定價、利潤率及合約條款 / Financial data, pricing, margins, and contract terms
- ·內部策略、業務計劃及未公開產品資訊 / Internal strategy, business plans, and unreleased product information
- ·同事的個人資料及薪酬資訊 / Colleagues' personal data and compensation information
- ·任何標示「Internal / Confidential」的文件或通訊 / Any document or communication marked "Internal / Confidential"
保密責任在員工離職後仍然有效。違反保密條款可導致即時解僱及民事或刑事法律責任。
The confidentiality obligation survives termination of employment. Breach may result in immediate dismissal and civil or criminal liability.
嚴禁:在辦公室以外的地方討論公司機密事宜(包括在公共場所、餐廳、交通工具上),亦不可透過個人電郵或非官方通訊渠道傳送公司文件。
Prohibited: Discussing confidential matters outside the office (including public spaces, restaurants, or transport), and sending company documents via personal email or unofficial channels.
系統使用規則 · System Usage Rules
公司系統及帳戶(包括電郵、Shopify 等)只可用於工作用途。嚴禁使用公司帳戶進行個人業務或第三方商業活動。
Company systems and accounts (including email, Shopify, etc.) are for work use only. Using company accounts for personal business or third-party commercial activities is strictly prohibited.
離職時,所有公司帳戶存取權限將即時撤銷。請勿在離職前備份或轉移任何公司數據。
All system access is revoked immediately upon termination. Do not back up or transfer company data prior to departure.
人工智能工具 · AI Tools
禁止將任何機密公司資料、客戶資料、合約或財務資訊輸入任何外部 AI 工具(包括 ChatGPT、Gemini、Claude 等公開版本)。
Inputting confidential company information, customer data, contracts, or financial information into any external AI tool (including public versions of ChatGPT, Gemini, Claude, etc.) is prohibited.
違規後果:違反數據保護政策可導致即時解僱及法律責任。
Violation of the data protection policy may result in immediate termination and legal liability.
共用雲端硬碟文件管理 · Shared Drive Filing Convention
所有文件必須存放於正確的項目或部門資料夾內,切勿直接上載至 Google Shared Drive 根目錄(Drive 首層)。請依照以下原則存放:
All files must be stored in the correct project or team folder. Do not upload directly to the Shared Drive root. Follow these placement principles:
- ·一般工作文件 → 存放於對應部門資料夾(Team Folder)內的相關子目錄
General working documents → relevant subfolder within your Team Folder
- ·向品牌方 / 代理商(Principal)提交的文件 → 存放於指定品牌項目資料夾(Brand Project Folder)
Documents for submission to brand principals → designated Brand Project Folder
- ·來自品牌方的資源文件(assets、產品資料、品牌手冊等)→ 存放於指定品牌資源資料夾(Brand Resources Folder)
Resources received from brands (assets, product info, brand guidelines) → designated Brand Resources Folder
文件命名規格如下:
File naming format:
YYMMDD_Title_Details
例如:260301_Calico_KOLBrief_SpringLaunch
Example: 260301_Calico_KOLBrief_SpringLaunch
Add Shortcut vs. Move — 捷徑與移動的分別
| 操作 Action |
用途 When to Use |
效果 Effect |
Add Shortcut to Drive 新增捷徑 |
你需要從自己的 Drive 快速存取某個文件,但不需要改變文件原本的所屬位置 You want quick access to a file from your own Drive, without changing where the file actually lives |
文件原位不變,只是在你的 Drive 中建立一個連結(如桌面捷徑)。刪除捷徑不會刪除原文件。 The file stays in its original location. A shortcut (link) appears in your Drive. Deleting the shortcut does not delete the original file. |
Move 移動文件 |
文件目前放錯了位置,需要實際移動至正確的資料夾 The file is in the wrong folder and needs to be physically relocated to the correct team folder |
文件從原位移走,只保留在新位置。移動前請確認原來的共享對象不會因此失去存取權。 The file is removed from its original location and exists only in the new location. Confirm that existing collaborators will not lose access before moving. |
原則:如非需要更改文件位置,優先使用「Add Shortcut」;如文件確實放錯資料夾,才使用「Move」。如不確定,請詢問管理層再操作。
Rule of thumb: Use "Add Shortcut" if you simply want easier access. Use "Move" only when a file is genuinely in the wrong folder. When in doubt, check with management before moving.
命名格式不正確或存放位置錯誤的文件可能被退回要求更正。請勿在未經確認的情況下移動他人文件。
Incorrectly named or misplaced files may be returned for correction. Do not move other people's files without their knowledge.
版本管理最佳實務 · Version Control Best Practices
- ·儲存具名版本(Save a Version):在 Google Docs / Sheets / Slides 中,使用「檔案 → 版本記錄 → 為目前版本命名」,記錄重要節點(如送審前、定稿後)。版本命名應清楚反映狀態,例如:v1.0_Draft、v2.0_ForReview、v3.0_Final。
Use "File → Version history → Name current version" in Google Docs/Sheets/Slides to mark key milestones (e.g. before submission, after finalisation). Name versions clearly, e.g. v1.0_Draft, v2.0_ForReview, v3.0_Final.
- ·編輯前先複製(Make a Copy Before Editing):如需修改他人文件或範本,請先「製作副本」再進行編輯,切勿直接覆蓋原檔。副本命名須包含版本號,例如:260301_BriefTemplate_v1.1_COPY。
If editing another person's document or a shared template, always make a copy first — never overwrite the original. Name the copy with a version number, e.g. 260301_BriefTemplate_v1.1_COPY.
- ·版本號命名規範:所有對外提交或多輪修訂的文件,檔名須包含版本號。格式:YYMMDD_Title_vX.X,其中 X.X 為主版本(重大修改)及次版本(細微調整)。
All externally submitted or multi-revision documents must include a version number in the filename. Format: YYMMDD_Title_vX.X, where X.X reflects major (significant changes) and minor (minor tweaks) revision numbers.
良好的版本管理可避免使用錯誤版本,以及因覆蓋原檔而造成的不可逆損失。
Good version control prevents errors from using outdated files and irreversible loss caused by overwriting originals.