> 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-recipient.md).
# 将文档分配给接收人
## **用途：**
\*\*“将文档分配给 Disponent / Purchaser”\*\*工作流卡片会将文档分配给 **Disponent** 或 **Purchaser**。如果未找到有效用户，系统会选择备用用户，以确保文档始终有人负责。
## **卡片组件：**
1. **Disponent / Purchaser**
* \*\*说明：\*\*指定将文档分配给 Disponent 还是 Purchaser。
* **选项：**
* \*\*Disponent：\*\*将文档分配给 Disponent。
* \*\*Purchaser：\*\*将文档分配给 Purchaser。
2. **备用用户**
* \*\*说明：\*\*指定备用用户，以便在无法将文档分配给所选 Disponent 或 Purchaser 时使用。
* \*\*详情：\*\*可用用户的下拉列表允许您选择一名备用用户，确保即使无法确定主要用户，文档仍会有人负责。
## **功能：**
* **条件评估：**\
只有当 **“Where”** 和 **“And Sections”** 均评估为真时，此卡片才会执行操作。
* **文档分配：**\
此卡片会按照所选对象，将文档分配给 **Disponent** 或 **Purchaser**。如果所选人员不可用或无效，文档将分配给备用用户。
## **设置与配置：**
* **选择 Disponent / Purchaser：**\
选择将文档分配给 **Disponent** 还是 **Purchaser**。
* **选择备用用户：**\
从下拉列表中选择一名备用用户；如果无法进行主要分配，文档将分配给该用户。
## **结论：**
\*\*“将文档分配给 Disponent / Purchaser”\*\*工作流卡片可确保文档始终有人负责：优先分配给所选的 Disponent / Purchaser，必要时分配给备用用户。这有助于减少工作流中断，并确保文档处理顺利继续。
---
# 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-recipient.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.
.png?alt=media)