6. 对你的创作者执行批量操作。请参考 [批量管理创作者](#bulk-manage-creators) 以下部分了解操作方法。
### 批量管理创作者
{% hint style="success" %}
**注意**：这些批量操作的可用性取决于用户账户权限。
{% endhint %}
在 *我的创作者* 屏幕上，你可以同时对多个创作者执行批量操作。要开始任何批量操作：
1. 将鼠标悬停在你要更改的创作者上，并选择  **\[未选中的复选框]** 其名称旁边的。
* 或者，选择  **\[未选中复选框]** **全选** 对所有创作者进行更改。
2. 从筛选器下方可用的选项中选择所需操作。请参阅下面的选项卡，了解如何执行所需操作。
{% tabs %}
{% tab title="创作者组" %}
更改分配给你创作者的组。
1. 选择 **更改组 \**  **\[下拉菜单]**。从此下拉菜单中，你可以执行以下其中一项：
* 分配到某个组：选择  **\[未选中复选框]** 目标组旁边的 **全选** 或选择
* 从某个组移除：取消选择  **\[复选框已勾选]** 组名称旁边的 **清除** 或选择
2. 选择 **应用** **→ 确认**.
{% hint style="success" %}
**注意**：更新可能不会立即可见。请在刷新浏览器前等待几分钟。
{% endhint %}
{% endtab %}
{% tab title="分配账户经理" %}
批量将创作者分配给特定账户经理。
1. 选择 **分配给** 以打开账户经理下拉列表。
2. 选择你要将创作者分配给的账户经理。
3. 选择 **应用** **→ 确认**.
{% hint style="success" %}
**注意**：更新可能不会立即可见。请在刷新浏览器前等待几分钟。
{% endhint %}
{% endtab %}
{% tab title="通过电子邮件联系合作伙伴" %}
批量向创作者发送电子邮件。
1. 选择 **电子邮件**.
2. 在弹出窗口中填写电子邮件详细信息。
3. 选择 **发送**.
{% endtab %}
{% tab title="更新合同" %}
批量更新你创作者的合同。
1. 选择 **合同。**
2. 选择以下选项之一：
* **切换到现有合同**
* **切换到新合同**
* **暂停**
* [**到期**](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/expire-partner-contracts.md#expire-a-partner-contract)
* [**修改设置**](/brand/zh/what-would-you-like-to-learn-about/platform-features/contracts-and-template-terms/contracts/revert-a-partner-contract-switch-or-expiry.md)
{% endtab %}
{% endtabs %}
---
# 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/working-with-creators/manage-your-creators.md?ask=&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.
\[消息] 该申请人。
\[更多] 将申请人移动到 审核中 或 候补.
[勾选] 如果创作者是 直接合作伙伴.