"""审批流程台账域通知模板。 台账由 IT 维护:员工改不了自己名下那一行 —— 归属是一条问责记录,不是 偏好设置。员工能做的是说「这不该由我负责」,那是一个需要 IT 裁决的 主张,于是它变成一条推送,收件面只取在职 ``global_admin``(唯一能改 归属的角色)。 半年度确认的模板见 PR3;这里只有争议这一条。 """ from __future__ import annotations TEMPLATES: dict[str, dict[str, str]] = { "approval_registry.confirmation_round": { "subject": "{round_label} 审批流程负责人确认:你名下有 {flow_count} 条", "subject_en": ( "{round_label} approval-flow ownership check: {flow_count} " "recorded against you" ), "subject_ja": ( "{round_label} 承認フロー担当者確認:あなた名義で {flow_count} 件" ), "body_text": ( "请确认以下审批流程是否仍由你负责:\n\n" "{flow_list}\n\n" "确认后,公示页会标注「已确认」。不再负责请逐条转交并指定接手人;" "流程需修改或下线,请在飞书审批管理后台操作,Helix 将于次日同步。\n\n" "请于 {due_date} 前完成。逾期未确认的流程将补发下线提醒,请及时处理。\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "Please confirm whether you still own the approval flows below.\n\n" "{flow_list}\n\n" "Once confirmed, the published page marks it as confirmed. " "If it is no longer yours, hand it over item by item and name " "a successor. To change or stop a flow, use the Feishu approval " "admin console; Helix syncs it the next day.\n\n" "Please answer by {due_date}. Unconfirmed flows after the " "deadline will receive a follow-up reminder to take them offline.\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "以下の承認フローを引き続き担当するか確認してください。\n\n" "{flow_list}\n\n" "確認後、公開ページには「確認済み」と表示されます。担当でなくなった" "場合は後任を指定して個別に引き継いでください。フロー自体の変更・" "停止は Feishu の承認管理画面で行い、Helix は翌日に同期します。\n\n" "{due_date} までにご回答ください。期限後も未確認のフローには、" "停止のフォローアップ通知を送ります。\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), "card_button_label": "✅ 全部确认仍由我负责", "card_button_label_en": "✅ Yes, all still mine", "card_button_label_ja": "✅ すべて引き続き自分が担当", }, "approval_registry.confirmation_overdue": { "subject": "{round_label} 审批流程确认逾期:还有 {flow_count} 条未回", "subject_en": ( "{round_label} approval-flow check overdue: {flow_count} " "still unanswered" ), "subject_ja": ( "{round_label} 承認フロー確認が期限超過:未回答 {flow_count} 件" ), "body_text": ( "{round_label} 的负责人确认还有 {flow_count} 条没有回复:\n\n" "{flow_list}\n\n" "这一轮到 {due_date} 截止。到期仍未回复的会记为「未响应」," "并出现在治理报表里 —— 不是处罚,是因为「没人担保的流程」这件事" "得有人看得见。一条也不是你的话,逐条转交同样算完成。\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "{flow_count} items in the {round_label} ownership check are " "still unanswered:\n\n{flow_list}\n\n" "The round closes on {due_date}. Anything still unanswered is " "recorded as no-response and appears in the governance report " "— not as a penalty, but because \"a flow nobody stands behind\" " "has to be visible. Handing them over counts as answering.\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "{round_label} の担当者確認で {flow_count} 件が未回答です:\n\n" "{flow_list}\n\n" "このラウンドは {due_date} に締め切ります。未回答のままの項目は" "「未対応」として記録され、ガバナンス帳票に表示されます。罰則では" "なく、「誰も担保していないフロー」を可視化するためです。" "引き継ぎでも回答として扱われます。\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), }, "approval_registry.confirmation_overdue_manager": { "subject": "{owner_name} 的审批流程确认逾期({flow_count} 条)", "subject_en": ( "{owner_name} has {flow_count} unanswered approval-flow checks" ), "subject_ja": "{owner_name} の承認フロー確認が未回答({flow_count} 件)", "body_text": ( "你的下属 {owner_name} 在 {round_label} 的审批流程负责人确认里" "还有 {flow_count} 条没有回复:\n\n{flow_list}\n\n" "你不需要替他回答 —— 这条只是让你知道。这类事通常一句话就能" "推动,而不回复的真实原因往往是「这本来就不该是他」,那正需要你" "帮着定人。\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "{owner_name}, who reports to you, has {flow_count} unanswered " "items in the {round_label} approval-flow ownership check:\n\n" "{flow_list}\n\n" "You are not being asked to answer for them — this is for your " "awareness. It is usually one conversation, and the real reason " "for silence is often \"this was never mine\", which is exactly " "the call you can make.\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "あなたの部下 {owner_name} が {round_label} の承認フロー担当者" "確認で {flow_count} 件未回答です:\n\n{flow_list}\n\n" "代わりに回答する必要はありません。共有のみです。多くの場合は" "一言で解決し、未回答の本当の理由が「そもそも自分の担当ではない」" "であることも多く、その判断はあなたにこそできます。\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), }, "approval_registry.flow_request_submitted": { "subject": "{requester_name} 申请新建审批流程「{proposed_name}」", "subject_en": ( "{requester_name} is asking for a new approval flow: " "\"{proposed_name}\"" ), "subject_ja": ( "{requester_name} が新しい承認フロー「{proposed_name}」を申請" ), "body_text": ( "有人需要一条现在还不存在的审批流程。\n\n" " · 申请人: {requester_name} <{requester_email}>\n" " · 建议名称: {proposed_name}\n" " · 分类: {category}\n" " · 用途: {purpose}\n\n" "批准之后要在飞书审批管理后台把流程建出来,再回到台账把 " "approval_code 填回去 —— 填回去这一步才算完成:批了但没人建的" "申请,对申请人来说和没批一样。建的时候顺手把申请人设成流程" "管理员,他之后改流程、下线都不用再找 IT。\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "Somebody needs an approval flow that does not exist yet.\n\n" " · Requested by: {requester_name} <{requester_email}>\n" " · Proposed name: {proposed_name}\n" " · Category: {category}\n" " · What for: {purpose}\n\n" "After approving, build the flow in the Feishu approval admin " "console and come back to fill its approval_code in — that last " "step is what finishes it: an approved request nobody built " "looks exactly like a rejected one from where the requester is " "standing. While you are in the console, make them a process " "administrator so they can change or stop it later without " "coming back to IT.\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "まだ存在しない承認フローが必要とされています。\n\n" " · 申請者: {requester_name} <{requester_email}>\n" " · 希望名称: {proposed_name}\n" " · 分類: {category}\n" " · 用途: {purpose}\n\n" "承認したら Feishu の承認管理画面でフローを作成し、台帳に戻って " "approval_code を入力してください。この最後の手順が完了条件です:" "承認されたのに誰も作っていない申請は、申請者から見れば却下と" "同じです。作成時に申請者をプロセス管理者に設定しておくと、" "後の変更や停止で IT に戻る必要がなくなります。\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), "card_button_label": "去处理", "card_button_label_en": "Open the queue", "card_button_label_ja": "対応する", }, "approval_registry.flow_request_approved": { "subject": "你申请的审批流程「{proposed_name}」已通过,IT 正在创建", "subject_en": ( "Your request for \"{proposed_name}\" was approved — IT is " "building it" ), "subject_ja": ( "申請された承認フロー「{proposed_name}」が承認され、IT が作成中です" ), "body_text": ( "IT 同意新建「{proposed_name}」。\n\n" " · IT 的说明: {note_block}\n\n" "接下来 IT 会在飞书审批里把流程建出来 —— 建好之后你会再收到一条" "消息,里面有它的正式名称,那时就可以用了。**现在还不能提交**。\n\n" "建好之后这条流程会登记在你名下:公示页上大家会看到你是负责人," "每半年会请你确认一次是否仍由你负责。\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "IT agreed to create \"{proposed_name}\".\n\n" " · Their note: {note_block}\n\n" "They will now build it in Feishu 审批. You will get one more " "message when it is ready, carrying its real name — that is when " "you can submit it. **Not yet.**\n\n" "Once built, the flow is recorded under your name: the all-staff " "page will show you as its owner, and twice a year we will ask " "you to confirm that is still right.\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "IT が「{proposed_name}」の作成に同意しました。\n\n" " · IT からの補足: {note_block}\n\n" "これから Feishu 承認でフローを作成します。完成したら正式名称を" "添えてもう一度お知らせしますので、その時点からご利用いただけます。" "**まだ提出はできません。**\n\n" "作成後、このフローはあなたの名義で登録されます。全社公開ページに" "担当者として表示され、半年ごとに継続確認のご連絡をします。\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), }, "approval_registry.flow_request_rejected": { "subject": "你申请的审批流程「{proposed_name}」未通过", "subject_en": "Your request for \"{proposed_name}\" was not approved", "subject_ja": "申請された承認フロー「{proposed_name}」は見送りとなりました", "body_text": ( "IT 这次没有新建「{proposed_name}」,原因是:\n\n" " {note_block}\n\n" "常见的情况是已经有一条能覆盖你需求的流程 —— 去公示页搜一下," "或者直接找 IT 问。如果情况有变化,随时可以再提一次。\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "IT did not create \"{proposed_name}\" this time:\n\n" " {note_block}\n\n" "The usual reason is that an existing flow already covers it — " "search the published list, or just ask IT. If circumstances " "change, you can ask again.\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "今回は「{proposed_name}」を作成しませんでした。理由:\n\n" " {note_block}\n\n" "多くの場合、既存のフローで対応できます。公開一覧を検索するか、" "IT に直接お問い合わせください。状況が変わればいつでも再申請" "できます。\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), }, "approval_registry.flow_request_registered": { "subject": "审批流程「{flow_name}」已经建好,可以用了", "subject_en": "\"{flow_name}\" is live — you can submit it now", "subject_ja": "承認フロー「{flow_name}」が利用可能になりました", "body_text": ( "流程已经在飞书审批里建好了,现在可以提交。\n\n" " · 正式名称: {flow_name}\n" " · 负责人: {owner_name}\n\n" "作为负责人,你会出现在全员公示页上 —— 同事按这个名字来找你。" "每半年平台会请你确认一次是否仍由你负责,不再由你负责时可以直接" "转交给别人。\n\n" "流程本身要改、要加审批人、或者以后要下线,直接去飞书审批管理" "后台操作,Helix 每晚同步回来,不用再走 IT。\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "The flow now exists in Feishu 审批 and can be submitted.\n\n" " · Name: {flow_name}\n" " · Owner: {owner_name}\n\n" "As its owner you appear on the all-staff page — colleagues will " "come to you by that name. Twice a year we will ask you to " "confirm it is still yours, and you can hand it to somebody else " "at any time.\n\n" "To change the flow itself, add approvers, or stop it later, do " "that in the Feishu approval admin console; Helix syncs it back " "nightly, so you do not need IT for it.\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "フローが Feishu 承認に作成され、提出できるようになりました。\n\n" " · 正式名称: {flow_name}\n" " · 担当者: {owner_name}\n\n" "担当者として全社公開ページに表示されます。半年ごとに継続確認の" "ご連絡をしますし、いつでも他の方へ引き継げます。\n\n" "フロー自体の変更・承認者の追加・将来の停止は Feishu の承認管理" "画面で行ってください。Helix が毎晩同期するため、IT を通す必要は" "ありません。\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), "card_button_label": "看看我负责的审批流程", "card_button_label_en": "See the flows I own", "card_button_label_ja": "担当フローを見る", }, "approval_registry.owner_assigned": { "subject": "{flow_summary}现在由你负责", "subject_en": "You now own {flow_summary}", "subject_ja": "{flow_summary}の担当者になりました", "body_text": ( "{handover_line}\n\n" "{flow_list}\n\n" "作为负责人,同事遇到相关问题会来找你,平台每半年也会问你一次" "「还是你吗」。\n\n" "流程本身住在飞书审批管理后台,Helix 记的是「谁为它负责」。" "要改流程内容或者停用它,请找 IT 把你加成飞书里的管理员。\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "{handover_line}\n\n" "{flow_list}\n\n" "As the owner you are who colleagues come to, and Helix " "checks with you every six months that it is still you.\n\n" "Approval flows live in the Feishu approval admin console; " "Helix records who answers for them. To change or retire one, " "ask IT to add you as an admin there.\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "{handover_line}\n\n" "{flow_list}\n\n" "担当者として、関連する問い合わせはあなたに届きます。" "半年ごとに「引き続き担当か」の確認も行われます。\n\n" "フロー自体は Feishu の承認管理画面にあり、Helix は「誰が責任を" "持つか」を記録します。変更・停止が必要な場合は IT に依頼して " "Feishu の管理者に追加してもらってください。\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), "card_button_label": "看看我负责的审批流程", "card_button_label_en": "See the flows I own", "card_button_label_ja": "担当フローを見る", }, "approval_registry.ownership_disputed": { "subject": "{disputer_name} 表示不该由自己负责审批流程「{flow_name}」", "subject_en": ( "{disputer_name} says they should not own the " "\"{flow_name}\" approval" ), "subject_ja": ( "{disputer_name} が承認フロー「{flow_name}」の担当ではないと申告" ), "body_text": ( "流程台账里 [b]{flow_name}[/b]({approval_code})的负责人登记的是 " "[b]{disputer_name}[/b],但本人表示不该由自己负责。\n\n" " · 提出人: {disputer_name} <{disputer_email}>\n" " · 当前归属来源: {owner_source}\n" " · 说明: {note_block}\n\n" "这一行会公示给全员,员工按它决定「这个流程该找谁」。" "挂着一个本人不认的名字,等于这个流程实际上没有人负责。\n\n" " {portal_url}\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "The owner recorded for [b]{flow_name}[/b] ({approval_code}) is " "[b]{disputer_name}[/b], who says it should not be them.\n\n" " · Raised by: {disputer_name} <{disputer_email}>\n" " · Current owner source: {owner_source}\n" " · Note: {note_block}\n\n" "This row is published to everyone, and staff use it to decide " "who to ask about the flow. A name the person does not accept " "means the flow effectively has nobody behind it.\n\n" " {portal_url}\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "台帳上、[b]{flow_name}[/b]({approval_code})の担当者は " "[b]{disputer_name}[/b] と登録されていますが、本人が自分の担当" "ではないと申告しています。\n\n" " · 申告者: {disputer_name} <{disputer_email}>\n" " · 現在の登録元: {owner_source}\n" " · 補足: {note_block}\n\n" "この行は全社に公開され、社員は「このフローは誰に聞けばよいか」" "の判断に使います。本人が認めない名前が残っている状態は、" "実質的に担当者不在です。\n\n" " {portal_url}\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), "card_button_label": "打开流程台账", "card_button_label_en": "Open the approval registry", "card_button_label_ja": "承認フロー台帳を開く", }, # 飞书后台待同步。收件面仍是在职 global_admin —— 但和别的管理员推送 # 不同,这一条要求的动作**不在 Helix 里**:飞书审批 v4 的定义接口只有 # 创建 / 读取 / 订阅,没有更新,流程管理员只能由人在后台改。所以正文 # 的第一件事是说清楚「为什么这条不能自动做」,否则收到的人会先去台账 # 页找一个并不存在的按钮。 "approval_registry.feishu_admin_drift": { "subject": "飞书审批后台待同步:{drift_count} 条流程的管理员和台账对不上", "subject_en": ( "Feishu console out of sync: {drift_count} flows name a " "different admin than the register" ), "subject_ja": ( "Feishu 承認管理画面が未同期:{drift_count} 件のフローで管理者が" "台帳と不一致" ), "body_text": ( "下面这些审批流程,Helix 台账里的负责人已经换了人,但飞书审批后台的" "[b]流程管理员[/b]还是原来那位:\n\n" "{drift_list}\n\n" "[b]这一步只能人工做。[/b]飞书审批 v4 的定义接口只有创建、读取和" "订阅,没有更新 —— 流程管理员没有写接口,Helix 改不了,只能由人" "在飞书审批后台改。\n\n" "不改的后果不是台账不准(台账是对的),而是新负责人有责任没权限:" "编辑流程、查看实例数据、收流程相关的管理员通知,靠的都是后台那份" "名单。同时后台还在把这些通知发给已经交接出去的人。\n\n" "改完不用回来点任何按钮 —— 每晚 03:30 的同步会重新读一遍后台名单," "对上了这一条就自动从待同步里消失。{renag_line}\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "For the approval flows below, the register's owner has " "changed but the Feishu console still names the previous " "person as [b]流程管理员[/b] (process admin):\n\n" "{drift_list}\n\n" "[b]This step can only be done by hand.[/b] Feishu's approval " "v4 definition API is create / get / subscribe — there is no " "update verb and no write for 流程管理员, so Helix cannot " "change it. Only a person in the Feishu approval console " "can.\n\n" "The cost of leaving it is not an inaccurate register (the " "register is right) — it is a new owner with the " "accountability and none of the access: editing the flow, " "reading its instance data and receiving its admin notices " "all come from the console's list. Meanwhile the console " "keeps sending those notices to somebody who handed the flow " "over.\n\n" "No need to come back and click anything — the 03:30 nightly " "sync re-reads the console, and a row that matches drops off " "this list on its own. {renag_line}\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "以下の承認フローは、Helix 台帳の担当者が変わっているのに、" "Feishu 承認管理画面の[b]流程管理员(プロセス管理者)[/b]が" "以前の担当者のままです:\n\n" "{drift_list}\n\n" "[b]この作業は手動でしか行えません。[/b]Feishu 承認 v4 の定義 API " "は作成・取得・購読のみで更新がなく、流程管理员 に書き込み API が" "存在しないため、Helix からは変更できません。Feishu 承認管理画面で" "人が変更する必要があります。\n\n" "放置した場合の問題は台帳の不正確さではありません(台帳は正しい" "です)。新しい担当者が責任だけを持ち権限を持たない状態になること" "です。フローの編集、インスタンスデータの閲覧、管理者通知の受信は" "すべて管理画面側の名簿に依存します。さらに管理画面は引き継ぎ済みの" "人に通知を送り続けます。\n\n" "変更後にこちらで操作する必要はありません。毎晩 03:30 の同期が" "管理画面を読み直し、一致した行はこの一覧から自動的に消えます。" "{renag_line}\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), "card_button_label": "打开飞书审批后台", "card_button_label_en": "Open the Feishu approval console", "card_button_label_ja": "Feishu 承認管理画面を開く", }, # 转交当场的告警(用户决定,2026-08-28)。和上面那条每日汇总同时存在, # 分工是清楚的:这一条只从**员工自己按下「转交」**那条路发出(set_owner # 里 announce == HANDOVER_TRANSFER,只有两个调用点),所以离职批量交接 # 仍然只进汇总,不会九张卡指着同一块后台屏幕。发出去之后调用方会盖 # drift 时间戳,次日汇总不再重复同一条。 "approval_registry.transfer_console_gap": { "subject": ( "{actor_name} 把审批流程「{flow_name}」转交给了 {successor_name}" "——飞书后台的流程管理员需要手动改" ), "subject_en": ( "{actor_name} handed the \"{flow_name}\" approval to " "{successor_name} — the Feishu console admin needs a manual fix" ), "subject_ja": ( "{actor_name} が承認フロー「{flow_name}」を {successor_name} に" "引き継ぎました —— Feishu 管理画面の管理者は手動変更が必要です" ), "body_text": ( "刚刚发生的一次转交,台账已经生效:\n\n" " · 流程: [b]{flow_name}[/b]({approval_code})\n" " · 原负责人: {previous_owner_name}\n" " · 新负责人: {successor_name} <{successor_email}>\n" " · 飞书后台目前的流程管理员: [b]{console_admins}[/b]\n\n" "[b]需要你去飞书审批后台把流程管理员改成新负责人。[/b]飞书审批 v4 的" "定义接口只有创建、读取和订阅,没有更新 —— 流程管理员没有写接口," "Helix 改不了。\n\n" "不改的后果不是台账不准(台账是对的),而是新负责人有责任没权限:" "编辑流程、查看实例数据、收流程相关的管理员通知,靠的都是后台那份" "名单。同时后台还在把这些通知发给刚刚交接出去的人。\n\n" "改完不用回来点任何按钮 —— 每晚 03:30 的同步会重新读一遍后台名单," "对上了这一条就自动从待同步清单里消失。\n\n" "{cta_line}\n\n" "— Helix 流程台账" ), "body_text_en": ( "A hand-over just happened and the register has already " "applied it:\n\n" " · Flow: [b]{flow_name}[/b] ({approval_code})\n" " · Previous owner: {previous_owner_name}\n" " · New owner: {successor_name} <{successor_email}>\n" " · Feishu console currently names: [b]{console_admins}[/b]\n\n" "[b]Please change the 流程管理员 in the Feishu approval console " "to the new owner.[/b] Feishu's approval v4 definition API is " "create / get / subscribe — there is no update verb and no " "write for 流程管理员, so Helix cannot do it.\n\n" "The cost of leaving it is not an inaccurate register (the " "register is right) — it is a new owner with the " "accountability and none of the access: editing the flow, " "reading its instance data and receiving its admin notices " "all come from the console's list. Meanwhile the console " "keeps sending those notices to the person who just handed " "the flow over.\n\n" "No need to come back and click anything — the 03:30 nightly " "sync re-reads the console and a row that matches drops off " "the out-of-sync list on its own.\n\n" "{cta_line}\n\n" "— Helix Approval Registry" ), "body_text_ja": ( "引き継ぎが行われ、台帳には既に反映されています:\n\n" " · フロー: [b]{flow_name}[/b]({approval_code})\n" " · 前の担当者: {previous_owner_name}\n" " · 新しい担当者: {successor_name} <{successor_email}>\n" " · Feishu 管理画面の現在のフロー管理者: [b]{console_admins}[/b]" "\n\n" "[b]Feishu 承認管理画面のフロー管理者を新しい担当者に変更して" "ください。[/b]Feishu 承認 v4 の定義 API は作成・取得・購読のみで" "更新がなく、フロー管理者に書き込み API が存在しないため、Helix " "からは変更できません。\n\n" "放置した場合の問題は台帳の不正確さではありません(台帳は正しい" "です)。新しい担当者が責任だけを持ち権限を持たない状態になること" "です。フローの編集、インスタンスデータの閲覧、管理者通知の受信は" "すべて管理画面側の名簿に依存します。さらに管理画面は、いま引き継ぎ" "を終えた人に通知を送り続けます。\n\n" "変更後にこちらで操作する必要はありません。毎晩 03:30 の同期が" "管理画面を読み直し、一致した行は未同期一覧から自動的に消えます。" "\n\n" "{cta_line}\n\n" "— Helix 承認フロー台帳" ), "card_button_label": "去飞书后台改管理员", "card_button_label_en": "Fix the admin in Feishu", "card_button_label_ja": "Feishu で管理者を修正", }, }