> 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/creator-edit-configuration/creator-edit-overview.md).

# Creator Edit 概览

impact.com 的 Creator Edit 提供完全定制的创作者门户，彰显您的品牌形象。您可以在专属环境中与创作者合作，该环境会根据您的需求量身打造。借助这种定制体验，您可以自定义门户的部分元素和内容，使其符合您的品牌和策略，从而更好地与创作者合作。

Creator Edit 门户提供功能完善的创作者仪表板，创作者可通过该仪表板创建链接、选购产品、访问资源以及申请加入营销活动。

#### 优势

* 完全融入品牌形象、由创作者引导的店面。
* 私有且直接掌控所有创作者关系。
* 高度品牌化、定制化且精心策划的体验。
* 为所有创作者提供简单的三步注册流程。

#### 主要功能

* 可自定义的可购物 [产品店面](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/creator-edit-configuration/product-catalog.md)
* 一个 [资源中心](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/creator-edit-configuration/creator-resources/create-and-edit-creator-resources.md) 用于链接对创作者有价值的文章资源
* 独特的 [创作者引导体验](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/creator-edit-configuration/creator-onboarding/customize-your-creator-onboarding-experience.md)
* 动态 [电子邮件模板和仪表板通知](https://help.impact.com/brand/zh/what-would-you-like-to-learn-about/creator-edit-configuration/emails-and-announcements.md)


---

# 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/creator-edit-configuration/creator-edit-overview.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.
