> 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/administration-and-setup/workflow/cards-overview/then/assignee/assign-document-to-the-sub-organization.md).

# Assign document to the sub organization

<figure><img src="/files/uudHBug2Jt9R6x9WesDK" alt="" width="563"><figcaption></figcaption></figure>

## **Purpose:**

The **"Assign Document to Sub-Organization"** workflow card assigns a document to a specific sub-organization within the system, ensuring that it is routed to the appropriate organizational unit for processing.

## **Components of the Card:**

1. **Sub-Organization**
   * **Description:** Specifies the sub-organization to which the document will be assigned.
   * **Detail:** A dropdown list of available sub-organizations is provided for selecting the target sub-organization.

## **Functionality:**

* **Condition Evaluation:**\
  The card only executes its action if both the **"Where"** and **"And Sections"** evaluate as true.
* **Document Assignment:**\
  The card assigns the document to the sub-organization selected from the dropdown list.

## **Setup and Configuration:**

* **Select Sub-Organization:**\
  Choose the appropriate sub-organization from the dropdown list to which the document should be assigned.

## **Conclusion:**

The **"Assign Document to Sub-Organization"** workflow card ensures that documents are routed to the correct sub-organization, streamlining the document management process by assigning responsibility based on organizational structure.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.docbits.com/administration-and-setup/workflow/cards-overview/then/assignee/assign-document-to-the-sub-organization.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
