> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/task/what-is-task-module.md).

# What is Task module?

In XoroERP, users can create and assign tasks to ensure that processes are completed on time and users are notified regarding the work. The Task Module helps to create and manage tasks efficiently. It assists teams in tracking tasks from the beginning, setting deadlines, prioritizing tasks, and assigning them to the right individuals. This ensures projects stay on track and are completed on time.

By leveraging the Task Module, users can ensure the following:

* Enhance team collaboration and communication
* Increase productivity and focus
* Improve project tracking and monitoring
* Ensure timely task completion and reduced delays

### Tasks can be created in multiple ways:

#### 1. Create a new, individual task

You can enter information into the task module to create the tasks.

#### 2. Create a task from a transaction module

Users can now create and manage tasks directly from various transaction modules to assign specific actions related to an order, estimate, or bill. This ensures that every stage of the transaction lifecycle is tracked and executed efficiently.

The **“Task”** tab is available in the header and subform sections of the following modules:

* Sales Order
* Estimate
* Purchase Order
* Invoice
* Bill
* Credit Memo
* Invoice Credit Memo


---

# 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.xorosoft.com/xoroerp-1/admin/task/what-is-task-module.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.