> 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-the-sub-organization.md).

# 将文档分配给子组织

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

## **用途：**

\*\*“将文档分配给子组织”\*\*工作流卡片会将文档分配给系统中的特定子组织，确保文档被路由到相应的组织单元进行处理。

## **卡片组成部分：**

1. **子组织**
   * \*\*说明：\*\*指定要将文档分配到的子组织。
   * \*\*详情：\*\*系统会提供可用子组织的下拉列表，供用户选择目标子组织。

## **功能：**

* **条件评估：**\
  只有当 **“Where”** 和 **“And Sections”** 均评估为真时，卡片才会执行操作。
* **文档分配：**\
  卡片会将文档分配给从下拉列表中选择的子组织。

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

* **选择子组织：**\
  从下拉列表中选择要分配文档的适当子组织。

## **结论：**

\*\*“将文档分配给子组织”\*\*工作流卡片可确保文档被路由到正确的子组织，并根据组织结构分配责任，从而简化文档管理流程。


---

# 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-the-sub-organization.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.
