> 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-recipient.md).
# Assign document to recipient
## **Purpose:**
The **"Assign Document to Disponent / Purchaser"** workflow card assigns a document to either a **Disponent** or **Purchaser**. If no valid user is found, a fallback user is selected to ensure the document is always assigned to someone.
## **Components of the Card:**
1. **Disponent / Purchaser**
* **Description:** Specifies whether the document will be assigned to a Disponent or Purchaser.
* **Options:**
* **Disponent:** Assign the document to the Disponent.
* **Purchaser:** Assign the document to the Purchaser.
2. **Fallback User**
* **Description:** Specifies a fallback user in case the document cannot be assigned to the selected Disponent or Purchaser.
* **Detail:** The dropdown list of available users lets you choose a fallback user to ensure the document is assigned even if the primary user cannot be determined.
## **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 either the **Disponent** or **Purchaser** as selected. If the selected person is unavailable or not valid, the document is assigned to the fallback user.
## **Setup and Configuration:**
* **Select Disponent / Purchaser:**\
Choose whether to assign the document to the **Disponent** or **Purchaser**.
* **Select Fallback User:**\
Choose a fallback user from the dropdown list who will receive the document if the primary assignment is not possible.
## **Conclusion:**
The **"Assign Document to Disponent / Purchaser"** workflow card ensures the document is always assigned, either to the selected Disponent/Purchaser or, if needed, to the fallback user. This minimizes workflow disruptions and ensures document processing continues smoothly.
---
# 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-recipient.md?ask=&goal=
```
`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.