> 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/and/assignee/single-assigned-user-condition.md).
# 单个已分配用户条件
**用途**
此工作流卡片根据任务或文档是否分配给某个特定用户来执行操作。它采用直接的条件逻辑管理需要特定用户参与的工作流，确保基于用户的任务处理精准无误。
**卡片组件**
1. **运算符**
* **说明**：指定应用于用户分配情况的逻辑。
* **选项**：
* **IS**：如果文档或任务的已分配用户与指定用户匹配，则触发操作。
* **IS NOT**：如果已分配用户与指定用户不匹配，则触发操作。
2. **用户**
* **说明**：允许选择一名用户，用于与已分配用户进行比较。
* **详情**：此处提供一个简单的下拉列表或自动补全字段，每次可选择一名用户。
**功能**
* **识别用户分配情况**：识别当前分配给特定任务或文档的用户。
* **条件评估**：
* 对于 **IS** 运算符，卡片会检查已分配用户是否与所选用户相同。
* 对于 **IS NOT** 运算符，卡片会验证已分配用户是否与所选用户不同。
* **执行操作**：
* **条件为真**：如果分配情况符合设定条件（IS 或 IS NOT），则触发预定义操作，例如继续审批、启动后续任务、发送通知或执行其他相关工作流。
* **条件为假**：如果条件不成立，工作流将不会继续。
**用户交互**
* **设置和配置**：用户通过选择运算符并在用户字段中选择一名用户来设置卡片。此过程应简单明了，便于选择用户和进行配置。
* **监控和报告**：提供监控卡片性能的工具，例如跟踪哪些任务由特定的用户分配情况触发，以及这些触发的结果。
* **错误处理和通知**：提供相应机制，在任务分配错误或分配问题导致操作错误时提醒用户。
#### 结论
“单个已分配用户条件”工作流卡片对于 ERP 系统中精准管理特定用户相关的文档和任务至关重要。它通过聚焦于单个用户的分配情况来简化工作流，确保只有在符合用户角色和职责的情况下才执行操作。清晰记录此卡片有助于用户了解其用途，从而在日常操作中有效实施和管理。本文档可帮助所有潜在用户轻松理解卡片的用途，并将其无缝整合到工作流中。
---
# 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/and/assignee/single-assigned-user-condition.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.
