> 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/payroll/payroll-setups/setup-employee-tree.md).

# Setup Employee Tree

**Available on:** Desktop · Web · Phone

Navigate to **Payroll Setups** and click on "Setup Employee Tree".

**Setup Employee Tree** shows who reports to whom as a **tree**, and lets you change it there. Each employee sits under their **manager** - the person their leave, short leave, missed-punch and comp-off requests go to first, unless an approval rule says otherwise. What you change here is the employee's **Reporting Authority**, the same one you see on Setup Employees and Assign Employees to Org.

The manager is worked out the same way as on Assign Employees to Org: the employee's **Reporting Authority** if one is set and still working, otherwise the **head of their unit** (or of a unit above). See [Who is the manager](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/payroll/payroll-setups/assign-employees-to-org.md) for the full rule.

## The screen

* **The tree** starts with the people at the top - those who have no manager but have someone under them. Under each person are the people who report to them. Senior designations come first, then names in order.
* Each line reads **NAME (CODE) - DESIGNATION \[n]**, where **n** is how many people sit under them in total (shown only when there is someone).
* A line shown in **grey** and ending in **(via unit)** comes from the **head of a unit**, not from a Reporting Authority.
* A line shown in **blue** and ending in **(not saved)** is a change you have made but not saved yet.
* **NOT PLACED** at the bottom lists the working employees who have no manager and nobody under them.
* **The details panel** shows the selected employee's designation, unit, branch, department, their **Manager** and where that comes from (their Reporting Authority, or the head of a unit), their **Reporting Authority**, how many people report to them directly and how many sit under them in total.
* **The line at the bottom** counts the working employees, how many are at the top and how many are not placed, and how many changes are not saved yet.

## Change who reports to whom

### **Step 1: Find the employee**

* Click the employee in the tree, or press **Find Employee** and pick the employee from the list: the tree opens down to them and selects them.
* **Expand All** opens every branch; **Collapse All** closes them.

### **Step 2: Make the change**

* **Add Team Members...** - select the manager in the tree, press the button and pick one or more employees. They will report to the selected manager.
* **Move Under...** - select an employee, press the button and pick their new manager. The employee moves there **with everyone under them**.
* **Remove Manager** - clears the selected employee's Reporting Authority. The head of their unit then becomes their manager, if there is one; otherwise they go to the top of the tree, or to **NOT PLACED** if nobody sits under them.
* **Remove Manager** is available only when the employee has a Reporting Authority. Most grey **(via unit)** lines have none - a unit head's line is changed on **Setup Org Units**.
* The buttons stay greyed until you click an employee. Without modify rights on this menu, the change buttons and **Save** stay greyed.
* The same actions are on the tree's **right-click** menu.

Each change is checked at once: you cannot make an employee report to themself, to someone who has left, or to someone who already sits under them.

### **Step 3: Confirm a move**

* When someone you are moving **already reports to someone else**, or **has a team under them**, the screen lists them first, under **Confirm Move**: each employee, who they are under now, how many people move with them, and who they will move under - and asks **Move them?**
* Press **Yes** to go ahead, or **No** (the answer it offers) to change nothing.
* Employees from **NOT PLACED** with nobody under them are not asked about.

### **Step 4: Save**

* The changes show in blue until you press **Save**; they are all saved together. The checks run again, and if one fails nothing is saved.
* Each change is recorded in the change log, with the Reporting Authority and the manager before and after.
* A change you undo (an employee put back under their old Reporting Authority) is no longer counted as a change.
* If you close the screen with changes not saved, it asks first (the answer it offers is **No**).

> **Example - a new sales manager**
>
> Anil heads the *SALES* unit, so Ravi and Neha, who are placed in it, report to Anil - their lines are grey, **(via unit)**. Meena joins as Sales Manager and Ravi and Neha should now report to her. HR clicks **MEENA** in the tree, presses **Add Team Members...** and picks Ravi and Neha. **Confirm Move** lists both as now under *ANIL (…) - head of SALES*, moving under Meena; HR presses **Yes**. Both now show in blue under Meena, who shows **\[2]**. HR presses **Save**.

## Requests already waiting

A request keeps the approvers it was given **when it was made**. Moving someone does not move their requests that are already waiting; only requests made from now on follow the new tree.

So after **Save**, if any waiting request is affected, the screen opens **Requests Still Waiting**: it says how many changes were saved and lists each affected request - the request number, the kind of request, the employee, when it was applied, the approval level, who it is **waiting with** and who the **manager is now**. This list is for information only - nothing is changed.

> **Example - continued**
>
> Neha applied for leave on Monday, before the change, and it is waiting with Anil. After HR saves, **Requests Still Waiting** shows her leave *Waiting With ANIL (…)*, *Manager Now MEENA (…)*. The leave stays with Anil, who can still approve it; Neha's next request goes to Meena.

## Messages you may see

| Message                                                                                                                               | Why                                                                                                      | What to do                                     |
| ------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
| … employee(s) below already report to someone or have a team. They will move to the new manager, with everyone under them. Move them? | **Confirm Move** (Step 3)                                                                                | **Yes** to move them, **No** to change nothing |
| An employee cannot report to themself.                                                                                                | In **Move Under...**, the employee picked is the selected one                                            | Pick someone else                              |
| None of the picked employees can be added under ….                                                                                    | In **Add Team Members...**, the only person picked is the manager themself                               | Pick the team members                          |
| …: the Reporting Authority reports (directly or further up) to …. / …: … reports (through a unit head) to ….                          | The new manager already sits under that employee                                                         | Pick someone higher up                         |
| '…' is not a working employee. / … picked employee(s) left out - not working employees. / …: the Reporting Authority has left.        | Someone picked has left since the screen was opened                                                      | Close the screen and open it again             |
| Nothing to save.                                                                                                                      | **Save** with no changes                                                                                 | -                                              |
| … change(s) saved.                                                                                                                    | **Save** worked (when requests are still waiting, this line heads the **Requests Still Waiting** window) | -                                              |
| … change(s) not saved yet. Close without saving?                                                                                      | Closing with changes not saved                                                                           | **No** goes back so you can Save               |

## On the web

The same screen is on the web, with the actions in a bar above the tree. On a phone or other narrow screen, a switch shows the **Tree** or the **Details**, one at a time. A **right-click** on an employee opens the same menu as on the desktop. On a touch screen, **press and hold** an employee to open it; on a phone it opens as a list from the bottom of the screen, which also has **Expand** / **Collapse** when the employee has people under them.


---

# 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-learning-hub-tutorials-and-best-practices/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.
