> 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-user-from-field.md).

# 根据字段分配用户

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

## **用途：**

\*\*“使用备用用户根据字段分配用户”\*\*工作流卡片会根据指定文档字段中的值动态分配用户。如果该字段中没有有效用户，系统会从预定义的可用用户列表中选择一名备用用户，以确保任务或操作得到妥善分配。

## **卡片组件：**

1. **字段名称**
   * **描述：指定包含待分配用户信息的文档字段**。
   * \*\*详细说明：\*\*系统会评估此字段，以确定应分配给哪位用户。如果字段中包含有效用户，该用户将获得此任务。如果字段为空或无效，则会分配给备用用户。
2. **用户（备用）**
   * **描述：指定在文档字段中没有有效用户时要分配的备用用户**。
   * \*\*详细说明：\*\*系统会提供包含所有可用用户的下拉列表供选择。如果文档字段为空或不包含有效用户，则会分配给此用户。

## **功能：**

* **条件评估：**\
  仅当 **“Where”** 和 **“And Sections”** 的评估结果均为 true 时，卡片才会执行操作。
* **基于字段分配用户：**\
  卡片会先尝试将任务或操作分配给 **Field Name** 中指定的用户。
* **分配备用用户：**\
  如果字段中没有有效用户（或字段为空），卡片会将任务分配给从 **User (Fallback)** 下拉列表中选择的备用用户。

## **设置和配置：**

* **选择字段名称：**\
  选择用于指定待分配用户的**文档字段**。
* **选择备用用户：**\
  从下拉列表中选择**备用用户**。如果文档字段中没有有效用户，系统会将任务分配给此用户。

## **结论：**

\*\*“使用备用用户根据字段分配用户”\*\*工作流卡片可确保任务或操作始终分配给有效用户。如果文档字段中的用户不可用，系统会自动分配给备用用户，从而提供灵活性并确保任务完成。


---

# 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-user-from-field.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.
