> 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-version-release-notes/october-2026/payroll/payroll-setups/setup-employees.md).

# Setup Employees

Logic ERP has added an **official phone** and **official e-mail** for each employee. These are the contacts colleagues see in the **People** screen of the **Logic Workforce** app - the personal phone and e-mail are never shown there.

***

### **Step 1: Show the new fields**

* Navigate to **Payroll Setups** and open **Setup Employees**.
* Click **Column Locks** (at the bottom of the screen; shown to users allowed to modify), tick **OFFICE PHONE(UNLOCK)** and **OFFICE EMAIL(UNLOCK)**, and accept. The two fields now show.

***

### **Step 2: Enter the official contacts**

* On the **Basic Information** tab, fill **Official Phone** and **Official Email**, just below **Email**, and save.
* Leaving them blank saves them empty.
* Changes to either field are recorded in **User Access Reports > Masters Modification Log**.
* The fields are also on the web.

***

### **What's corrected**

* On the web, a **Date of Leaving** that had been filled in can now be cleared. Earlier the date came back as soon as the box was left.


---

# 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://kb.logicerp.com/logic-erp-version-release-notes/october-2026/payroll/payroll-setups/setup-employees.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.
