> For the complete documentation index, see [llms.txt](https://docs.oneweb.tech/oneweb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/process-components/process-activity/human-task.md).
# Human Task
Use the **Human Task** to assign a job to a human based on a work-party, user-role or any custom condition.
### **Purpose**
**Human Task** is used to support the allocation of a job to a human entity based on work party assignments, user-roles or any custom conditions. It has the mapping parameter screen to define the input and output parameters of the task. Human Task will be executed when you manually submit a form. It is represented as in rectangular shape box as shown below:
### **Human Task Properties:**
Human Task configuration panel has four different tabs to define properties.
**General**
General Tab contains general information such as title, task id, description etc.
**Business Object**
It is used to configure and map the **Business Object** for the input and output of any node. In case you need a value from the process to be used in your node (input) or pass the value from your node to other nodes in the process (output) you should map the input and output Activity parameters to the process **Business Object.** But it is not mandatory to map the parameter as you can use the node without parameters as well.
**Assignment Policy**
To set the type of assignment policy to be used for the task allocation
Property
Mandatory
Default
Description
Setting
Y
Lane
To choose the type of assignment method to be used. System provides 6 types as follows: Lane, Pull, Round Robin, Load Balance, Routing Policy, Multi Instance and Custom.
More details for each Assignment policy method are discussed in [Task Allocation & Queuing](/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/process-components/process-activity/human-task/task-allocation-and-queuing-for-human-task.md) chapter
**Load Entity**
Load entity tab is used to map an Entity on your ONEWEB Platform to the human task. User can configure the properties and Values inside Load Entity Tab. Delete/Trash icon is provided on right side to remove any key value mapping.
For more information on each tab and Configuration settings of **Human node Task**, please refer to[ ](/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/process-components/process-activity/human-task.md)[Human](/oneweb/reference/process-designer-reference/process-designer-component/activity-nodes/human.md) Activity Node in Process Designer Reference Chapter
---
# 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.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-process/process-components/process-activity/human-task.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.