> For the complete documentation index, see [llms.txt](https://help.impact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/customize-microsite-lifecycle-emails.md).

# 自定义微站生命周期邮件

自动设置过程中会为你的微站创建两封生命周期邮件：

* 用户验证
* 密码重置

你可以保留这些邮件原样、进行编辑，或创建全新的邮件，在这些情况下发送给用户。

<details>

<summary>添加新邮件</summary>

1. 在左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → 内容**.
2. 在 *微站* 卡片上，选择 **编辑内容**.
3. 在左侧边栏菜单中选择 **邮件** 。
4. 选择 **创建新的邮件模板**.
5. 输入邮件模板 ID。请使用简短且唯一的名称，以便识别该邮件。之后无法更改。
6. 选择 **创建**.
   * 你将被重定向到邮件编辑器。
7. 进行所需的更改。

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>注意：</strong> 如果你希望团队中的某人收到发送给参与者的每封邮件副本，可以选择 <strong>编辑</strong> ，该选项位于 <em>联系信息</em> 标题右侧，然后调整 <strong>密送字段</strong>.</p></div>
8. 选择 **保存**.
9. 将现有生命周期邮件之一替换为你新创建的邮件。

</details>

<details>

<summary>编辑邮件模板</summary>

1. 在左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → 内容**.
2. 在 *微站* 卡片上，选择 **编辑内容**.
3. 在左侧边栏菜单中选择 **邮件** 。
4. 选择要编辑的邮件名称。
   * 你将被重定向到邮件编辑器。
5. 进行所需的更改。

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>注意：</strong> 如果你希望团队中的某人收到发送给参与者的每封邮件副本，可以选择 <strong>编辑</strong> ，该选项位于 <em>联系信息</em> 标题右侧，然后调整 <strong>密送字段</strong>.</p></div>
6. 选择 **保存**.

</details>

<details>

<summary>替换生命周期邮件</summary>

你可以在管理门户中调整微站设置，以决定生命周期邮件使用哪些邮件模板。

1. 在左侧导航菜单中，选择 ![](https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-230534471fef5f40808e921e41ee44e4a06ded03%2Fe6cb9548999afdc1ed3ce4942e4cb5b45b5cecbd323267aac2a7cd1915fccc09.svg?alt=media) **\[Engage] → 内容**.
2. 在 *微站* 卡片上，选择 **编辑设置**.
3. 在 *生命周期邮件* 部分中，选择新的 **验证** 或 **密码重置** 邮件。请使用下拉列表进行选择。
4. 选择 **保存**.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/advocate-program/manage-advocate-participant-experiences/microsite-experiences/customize-microsite-lifecycle-emails.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
