> 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-document-to-user.md).

# 将文档分配给用户

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

## **用途：**

\*\*“Assign Document to User”（将文档分配给用户）\*\*工作流卡片允许用户将文档分配给特定用户，确保文档能够流转到合适的人员，从而顺畅地管理工作流。版本 3 新增了使用决策树的功能，可根据现有条件动态确定分配对象。

## **卡片组件：**

1. **用户**
   * \*\*说明：\*\*指定接收文档的用户。
   * \*\*详情：\*\*提供包含所有可用用户的下拉列表供选择。选中的用户将接收该文档并进行后续处理。

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

1. **Use Decision Tree**
   * \*\*说明：\*\*启用后，卡片会使用决策树动态确定分配对象。
   * **选项：**
     * \*\*True：\*\*使用决策树动态分配用户。
     * \*\*False：\*\*将文档分配给所选用户，不使用决策树。

## **功能：**

* **条件评估：**\
  仅当 **“Where”** 和 **“And Sections”** 均评估为真时，卡片才会执行操作。
* **文档分配：**\
  卡片会将文档分配给所选用户，确保任务流转到合适的人员进行处理。这有助于明确责任并有效管理文档。
* **决策树（版本 3）：**\
  启用决策树后，卡片会评估树中定义的条件，以动态选择文档的分配对象。

## **设置与配置：**

* **选择用户：**\
  从下拉列表中选择要接收文档的**用户**。
* **Use Decision Tree（版本 3）：**\
  启用或停用决策树，以便动态选择用户。

## **结论：**

\*\*“Assign Document to User”（将文档分配给用户）\*\*工作流卡片通过将文档分配给所选用户来实现高效的文档流转。版本 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-document-to-user.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.