> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/workflow/cards-overview/then/assignee/assign-to-group.md).

# 分配至组

<figure><img src="https://1870485400-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlPczlNw8zzYNLfjfispX%2Fuploads%2Fgit-blob-75c3be04d542f1d58f90146b1a32e4e15efb8387%2Fimage%20(377).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

## 用途：

**“Assign to Group”（分配至组）工作流卡片可将文档分配给系统中的特定组**，确保文档由合适的团队处理，从而简化工作流。后续版本增强了此功能，并引入决策树功能，以便动态分配组。

## 卡片组件：

1. **组**
   * **描述：指定要分配文档的组**。
   * **详情：从可用组**的下拉列表中选择。

## **版本 3 中的其他组件**

1. **决策树（仅限版本 3）**
   * **描述：通过决策树动态确定应将文档分配到哪个组**。
   * **选项：**
     * \*\*True：\*\*启用决策树处理。
     * \*\*False：\*\*禁用决策树处理。

## 功能：

* \*\*条件评估：\*\*仅当 **“Where”** 和 **“And Sections”** 的评估结果均为 true 时，此卡片才会执行操作。
* **文档分配：将文档分配给所选组**。在**版本 3**中，如果启用了**决策树**，则由其动态确定目标组。

## 设置与配置：

* **选择组：从下拉列表中选择要分配文档的组**。
* **使用决策树（仅限版本 3）：如果要使用决策树**动态分配组，请启用此选项。

## 结论：

**“Assign to Group”（分配至组）工作流卡片可自动将文档分配给预定义的组**，加强团队协作。**版本 3**新增了根据决策树逻辑动态分配组的功能。


---

# 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://docs.docbits.com/chinese/guan-li-yu-she-zhi/workflow/cards-overview/then/assignee/assign-to-group.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.