> 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-program/recruit-creators/recruiting-creators-explained.md).

# 招募创作者说明

在招募创作者时，你可以接受他们的申请，也可以直接邀请他们。根据招募流程的处理方式，创作者可能会加入特定的创作者活动，也可能加入你的整体项目。请查看下方场景，了解每种情况会发生什么，以及创作者加入后在哪里可以找到他们。

<div data-with-frame="true"><figure><img src="https://1186853034-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwMLlMoFBtKJa8ptd3zaw%2Fuploads%2Fgit-blob-fd0309b94a76b050a74dd4f5a9258a1a5ec673f0%2F8f16c432029fb9a29591b5873c58247a22fcba80ff0c09d5ae4fd4576e625bf2.png?alt=media" alt="" width="563"><figcaption></figcaption></figure></div>

#### 邀请创作者时的场景

<details>

<summary>通过市场邀请已合作创作者</summary>

如果你将一位已经加入你项目的创作者邀请到关联活动，并且他们接受了邀请，他们将自动获批加入该活动。请在你的 *创作者* 页面或你的 *活动管理*。参见 [管理你的创作者](/brand/zh/what-would-you-like-to-learn-about/creator-program/working-with-creators/manage-your-creators.md) 了解更多详情。

</details>

<details>

<summary>通过市场邀请新创作者</summary>

如果你通过市场邀请一位新创作者加入你的活动，并且他们接受了邀请，他们将自动获批加入该活动和关联项目。请在你的 *创作者* 页面上管理他们——参见 [管理你的创作者](/brand/zh/what-would-you-like-to-learn-about/creator-program/working-with-creators/manage-your-creators.md) 了解更多详情。

</details>

<details>

<summary>通过活动邀请链接邀请创作者</summary>

如果你通过一个活动 *邀请链接* 具体来说，你是在邀请他们加入你的创作者活动以及关联项目（如果他们尚未加入）。如果他们接受，他们将自动获批加入你的项目，但你仍然需要在你的 *活动管理*。参见 [管理创作者活动申请者](/brand/zh/what-would-you-like-to-learn-about/creator-program/recruit-creators/manage-creator-campaign-applicants.md) 以获取指导。

</details>

<details>

<summary>仅邀请创作者加入项目</summary>

如果你从市场直接邀请一位创作者加入你的项目，并且他们接受了邀请，他们将自动获批加入该项目。请在你的 *申请* 页面上管理他们——参见 [管理申请与发送提案](/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/manage-applications-and-send-proposals.md) 以获取指导。

无论你是通过市场还是通过模板条款注册链接邀请他们，这一点都适用。

</details>

#### 批准创作者申请时的场景

<details>

<summary>批准来自已合作创作者的市场申请</summary>

如果某位创作者在已经加入你的项目的情况下申请加入你的创作者活动，请在你的 *活动管理*。参见 [管理创作者活动申请者](/brand/zh/what-would-you-like-to-learn-about/creator-program/recruit-creators/manage-creator-campaign-applicants.md) 以获取指导。

</details>

<details>

<summary>批准来自新创作者的市场申请</summary>

如果某位创作者在未先加入关联项目的情况下申请加入你的创作者活动，impact.com 会将其记录为同时向你的活动和项目提交的双重申请。请在你的 *活动管理* 和你的 *申请* 界面中进行设置。

* 要同时批准这两项申请，请在你的 *活动管理*。参见 [管理创作者活动申请者](/brand/zh/what-would-you-like-to-learn-about/creator-program/recruit-creators/manage-creator-campaign-applicants.md) 以获取指导。
* 若只接受项目申请，请在你的 *申请* 页面上批准该申请。参见 [管理申请与发送提案](/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/manage-applications-and-send-proposals.md) 以获取指导。

</details>

<details>

<summary>批准通过活动邀请链接提交的申请</summary>

如果某位创作者是专门通过该活动的 *邀请链接*申请加入你的创作者活动，impact.com 会自动批准其加入关联项目（如果他们尚未加入）。不过，你仍然需要在你的 *活动管理*。参见 [管理创作者活动申请者](/brand/zh/what-would-you-like-to-learn-about/creator-program/recruit-creators/manage-creator-campaign-applicants.md) 以获取指导。

</details>

<details>

<summary>仅批准加入项目的申请</summary>

如果某位创作者只申请加入你的项目，而不是关联活动，你可以在下方找到并批准他们的申请 *申请* ，就像你批准合作伙伴一样。参见 [管理申请与发送提案](/brand/zh/what-would-you-like-to-learn-about/platform-features/review-partner-applications/manage-applications-and-send-proposals.md) 以获取指导。

无论他们是通过市场还是通过模板条款注册链接申请，这一点都适用。

</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/creator-program/recruit-creators/recruiting-creators-explained.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.
