> 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/introduction-welcome-to-creator/step-2-invite-creators-or-review-applications.md).

# 第 2 步：邀请创作者或审核申请

在与创作者合作时，你可以选择邀请创作者，或者创建一个创作者可以申请参与的活动。

{% hint style="success" %}
**注意：** 你可以邀请创作者加入你的 *计划* 或者加入一个 *活动*。请参阅 [不同场景](/brand/zh/what-would-you-like-to-learn-about/creator-program/recruit-creators/recruiting-creators-explained.md) 了解创作者加入你的计划与活动时会发生什么。
{% endhint %}

#### 邀请创作者 <a href="#section-idm234650341931937" id="section-idm234650341931937"></a>

一旦你找到适合参与活动的创作者，你可以邀请他们，或将他们标记为潜在对象，以便在稍后阶段再邀请。你可以通过不同方式邀请创作者：

* [市场](/brand/zh/what-would-you-like-to-learn-about/creator-program/recruit-creators/invite-creators-to-your-campaign.md)：一旦你在市场中找到合适的创作者，选择他们的个人资料即可邀请他们加入你的活动。
* [潜在客户](/brand/zh/what-would-you-like-to-learn-about/performance-program/recruiting-partners/prospective-partners/view-prospective-partners.md)：如果你不想立即邀请创作者，而是想在稍后阶段再邀请，可以将他们标记为潜在对象。
* [直接从你的活动中](/brand/zh/what-would-you-like-to-learn-about/creator-program/recruit-creators/invite-creators-to-your-campaign.md)：一旦你设置好活动，就可以直接从活动中邀请创作者或创作者群组。

<details>

<summary>邀请创作者的最佳实践</summary>

在邀请创作者加入你的活动时，邀请的人数要多于实际所需，并扩大筛选条件，以提高找到完美创作者的机会。结合使用 [创作者层级](/brand/zh/what-would-you-like-to-learn-about/platform-features/reach-out-to-partners/partner-management/partner-size-rating-criteria.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/introduction-welcome-to-creator/step-2-invite-creators-or-review-applications.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.
