> 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-1.md).
# 单个已分配用户条件
**用途：**\
此工作流卡根据任务或文档是否分配给特定组来执行操作。它使用简单的条件，根据组分配情况触发或阻止操作。
**卡片组件：**
1. **运算符**
* \*\*说明：\*\*定义要应用于组分配的逻辑条件。
* **选项：**
* \*\*是：\*\*如果文档或任务的已分配组与指定组匹配，则触发操作。
* \*\*不是：\*\*如果文档或任务的已分配组与指定组不匹配，则触发操作。
2. **组**
* \*\*说明：\*\*指定要与已分配组进行比较的组。
* \*\*详细信息：\*\*此字段允许你选择一个组来比较分配情况。
**功能：**
* \*\*识别组分配：\*\*自动识别分配给特定任务或文档的组。
* **条件评估：**
* 使用**是**运算符时，卡片会检查已分配组是否与指定组匹配。
* 使用**不是**运算符时，卡片会确认已分配组与指定组不匹配。
* **执行操作：**
* **条件为真：如果组分配符合条件（是或不是**），则触发相关操作，例如发送通知、启动任务、进行审批或执行其他工作流步骤。
* \*\*条件为假：\*\*如果不符合条件，文档或任务可能会进入不同的路由，也可以指定替代操作。
**用户交互：**
* **设置与配置：**\
用户通过选择运算符并指定相关组来配置卡片。配置过程应简单直观。
* **监控与报告：**\
系统应提供监控和报告此卡片所触发操作的功能，以便了解分配准确性和流程效率。
* **错误处理与通知：**\
用户应可以选择接收有关分配问题的提醒或通知，例如任务未分配或组选择错误。
**结论：**\
“已分配组条件”工作流卡对于根据组分配管理文档和任务工作流至关重要。通过设置任务或文档是否分配给特定组的条件，它可确保只有在与相应组进行交互时才触发工作流，从而提升任务管理和工作流效率。
---
# 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-1.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)