> 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-employee-tree.md).

# Setup Employee Tree

Logic ERP has introduced **Setup Employee Tree**. It shows who reports to whom as a tree - each employee under their manager - and lets HR change it there.

***

### **What it does**

* Navigate to **Payroll Setups** and open **Setup Employee Tree**.
* Each employee sits under their **manager**: their **Reporting Authority**, or else the head of their unit (or of a unit above). A line from a unit head shows in grey, **(via unit)**. Employees with no manager and nobody under them are listed under **NOT PLACED**.
* **Find Employee** opens the tree down to an employee. **Add Team Members...** puts the employees you pick under the selected manager; **Move Under...** moves the selected employee, with everyone under them, to a new manager; **Remove Manager** clears the employee's Reporting Authority. The same actions are on the tree's right-click menu.
* Moving someone who already reports to someone else, or who has a team, is listed under **Confirm Move** first.
* Changes show in blue until **Save**. Each change is recorded in the change log, with the Reporting Authority and the manager before and after.
* Requests already waiting keep the approver they were given when they were made. After **Save**, any that are affected are listed under **Requests Still Waiting**; requests made from then on follow the new tree.
* The screen is also available on the web; on a phone, press and hold an employee to open its menu.

***

For more detailed information, [Click Here](/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/setup-employee-tree.md)


---

# 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-employee-tree.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.
