> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-vouchers/job-order/job-order-configuration/default-worker-party.md).
# Default Worker/Party
**YouTube:** [How to Configure the Default Worker or Party in Job Orders?](https://youtu.be/zaWAqWH9Bzs)
## How to Configure the Default Worker or Party in Job Orders?
In this tutorial, we will learn how to specify a **Default Worker or Party** for Job Order entries in Logic ERP. This feature automatically selects the configured Worker or Party while creating a new Job Order, reducing manual data entry.
***
### Objective of This Feature
* Automatically select a Default Worker or Party
* Reduce repetitive data entry
* Speed up Job Order creation
* Simplify outsourced Job Order processing
* Minimize manual selection errors
***
### Access to the Job Order Configuration
* Open the **Configuration** window.
* Navigate to the **Default Settings** section.
* Locate the option labeled as:
> **"Default Worker/Party"**.
* Open the dropdown list.
* Select **Worker**.
**Next:**
* Locate the next option labeled as:
> **Default Worker**
* Select the required Worker from the dropdown list.
* Save the configuration changes.
***
### Verify the Default Worker
* Initiate a **New Job Order** entry.
**Result**
* The **Worker** option is automatically selected, and the **Worker Name** field is populated with the Worker defined in the configuration.
* This eliminates the need to manually select the Worker for every Job Order.
***
### Set Default Party
For outsourced Job Orders, you can configure a **Party** as the default instead of a Worker.
* Return to the **Job Order Configuration** window.
* Navigate to **Default Settings**.
* Set **Default Worker/Party** to **Party**.
* Select the required Party in the **Default Party** option.
* Save the configuration changes.
***
### Verify the Default Party
* Initiate a **New Job Order** entry.
**Result**
* The **Party** option is automatically selected, and the **Party Name** field is populated with the Party defined in the configuration.
***
### Key Benefits
* Faster Job Order entry
* Eliminates repetitive Worker or Party selection
* Simplifies outsourced Job Order processing
* Improves data entry efficiency
* Reduces manual errors
* Ensures consistent transaction setup
***
### Best Practice Tips
* Select **Worker** when Job Orders are assigned to internal workers.
* Select **Party** when Job Orders are outsourced.
* Ensure the required Worker or Party is defined before configuring the default.
* Review the default configuration whenever the Job Order process changes.
***
### Final Outcome
After configuring **Default Worker/Party**, Logic ERP automatically selects the appropriate **Worker or Party** and populates the corresponding name field during Job Order entry. This makes the process faster, more consistent, and easier to manage.
---
# 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/production/production-vouchers/job-order/job-order-configuration/default-worker-party.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.