1. Accounts, roles, and campus access

• ☐ Each current Principal and Staff member has the correct campus access; inactive and test-only accounts are disabled.
• ☐ Each teacher is approved and assigned to the courses they will teach. Confirm a teacher cannot see an unassigned course.
• ☐ Parent contacts match the intended family email, and no shared staff account is used for a family.
• ☐ A multi-role user has switched roles and campuses successfully. Confirm the active role before making changes.

2. Sign-in and account recovery

• ☐ Test a real sign-in path for one Parent and one school employee in the production-like environment.
• ☐ If Google sign-in is enabled, test the intended account type and confirm SchoolCMS still applies its own role, campus, and approval rules.
• ☐ Test the password-reset/help path for a password-capable account. Do not record or share a password during the test.
• ☐ Confirm the launch owner knows who can correct an account email, role, campus, or teacher approval.

Verify configuration by completing the user-facing flow and checking its result. Do not copy OAuth settings, environment-variable names or values, callback URLs, API keys, or secrets into training material.

3. School year, courses, and calendar

• ☐ Confirm the active school year, terms, registration status, no-class days, graduation dates, and calendar approval state.
• ☐ Review each launch course: campus, meeting time, room, capacity, assigned teacher, fee/material fee, and billing mode.
• ☐ Complete one safe end-to-end enrollment check and verify the family sees the expected course/calendar information.
• ☐ Confirm the owner for calendar corrections and course/teacher assignment corrections.

4. Payments and billing safety

• ☐ A designated Principal/finance owner has reviewed the visible Payment Setup status and the school’s fee/refund process.
• ☐ Run an approved, controlled payment test only when finance authorizes it; verify the resulting invoice/payment state and support path.
• ☐ Confirm Staff can review an invoice and knows when to escalate a payment, refund, or reconciliation issue.
• ☐ Do not capture, paste, email, or screen-share payment credentials, payment card data, webhook details, or live payment identifiers.

Stop: do not open broad parent payment access until the finance owner confirms payment readiness, fee disclosure, and the escalation path.

5. Role smoke test

6. Privacy, support, and launch decision

• ☐ Training uses approved demo records only. Screenshots/videos contain no passwords, secrets, private student information, or live payment details.
• ☐ School users know to use their own account, verify role/campus, and sign out of shared devices.
• ☐ Support owners are named: enrollment/roster → Staff; teacher/calendar approval and staff access → Principal; payments → finance owner; sign-in/system issue → technical support.
• ☐ The launch owner records any open issue, owner, and due date. Invite families only after critical issues are closed or explicitly accepted.

1. 账号、角色和校区权限

• ☐ 每位现任 Principal 和 Staff 都有正确的校区权限；不活跃和测试账号已停用。
• ☐ 每位 Teacher 已获审批并分配到应授课程；确认教师看不到未分配课程。
• ☐ Parent 联系邮箱与预期家庭邮箱一致，且没有家庭使用共享员工账号。
• ☐ 多角色用户已成功切换角色和校区。任何修改前先确认当前角色。

2. 登录和账号恢复

• ☐ 在接近 production 的环境中，为一位 Parent 和一位学校员工测试真实登录流程。
• ☐ 如启用 Google 登录，测试预期账号类型，并确认 SchoolCMS 仍按自身角色、校区和审批规则授权。
• ☐ 为可使用密码的账号测试重置密码/求助流程。测试时不要记录或分享密码。
• ☐ 确认上线负责人知道谁能更正账号邮箱、角色、校区或教师审批。

通过完成用户可见流程并核对结果来验证配置。不要将 OAuth 设置、环境变量名称或值、回调 URL、API key 或密钥写入培训材料。

3. 学年、课程和校历

• ☐ 确认当前学年、学期、报名状态、停课日、毕业日期和校历审批状态。
• ☐ 审核每门上线课程：校区、上课时间、教室、容量、分配教师、课程/材料费和 billing mode。
• ☐ 完成一次安全的端到端报名核查，并确认家庭看到预期课程和校历信息。
• ☐ 确认校历修改、课程修改和教师分配修改的负责人。

4. 付款和账单安全

• ☐ 指定 Principal/财务负责人已审核可见的 Payment Setup 状态，以及学校的手续费和退款流程。
• ☐ 仅在财务授权后进行受控付款测试；核对产生的 invoice/payment 状态及支持路径。
• ☐ 确认 Staff 能查看 invoice，并知道何时升级付款、退款或对账问题。
• ☐ 不要截图、粘贴、邮件发送或屏幕共享付款凭据、卡信息、webhook 详情或真实付款标识。

停止：在财务负责人确认付款准备、费用说明和升级路径前，不要向大量家长开放付款。

5. 角色冒烟测试

6. 隐私、支持和上线决定

• ☐ 培训只使用获批准的演示记录。截图/视频不含密码、密钥、私人学生资料或真实付款信息。
• ☐ 学校用户知道只用自己的账号、先核对角色/校区，并在共用设备上退出。
• ☐ 已指定支持负责人：报名/名单 → Staff；教师/校历审批和员工权限 → Principal；付款 → 财务负责人；登录/系统问题 → 技术支持。
• ☐ 上线负责人记录所有未解决问题、负责人和截止日期。仅在关键问题关闭或明确接受后邀请家庭。