> 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-org-units.md).

# Setup Org Units

Logic ERP has added **People** to the **Logic Workforce** app - the organization tree, like a company directory: who reports to whom, with photos. **Setup Org Units** has a new setting that decides who may open the whole organization.

***

### **People in the app**

* In the app, open **More** and tap **People**. It shows working employees only.
* People opens on **Organization**, at the top of the company. Anyone with someone reporting to them also gets an **Organization / My team** switch; **My team** starts at you. Everyone else sees Organization only, with no switch.
* Each card shows the person's photo (or initials), name, designation, employee code and department, with a badge for how many people are under them (everyone under them, not just direct reports).
* Tap a card to open the people reporting to that person. The people above the person you are looking at are shown on the left - tap one to go back to their level, or use the arrow at the top to go up a level. The phone's Back button returns to **More**.
* Tap the **i** on a card - or a card with nobody under it - for the person's details: department, branch, who they report to, and their **official** phone and e-mail (tap to call or write). Personal phone numbers and e-mails are never shown.
* HR also sees the people who are **not placed** - with no manager and nobody under them - so they can be given a manager.
* The reporting lines are the same as for approvals: the employee's **Reporting Authority**, or else the head of their org unit or of a unit above it.

***

### **Your photo**

* On the **More** tab, tap your photo (or initials) and choose **Take photo** or **Choose from gallery** (and **Remove photo** when you have one).
* The photo is saved at once and shows in **People** and on **Setup Employees**. A photo set on **Setup Employees** shows in the app too.
* Every change is recorded in **User Access > Change Log Viewer** as **Employee Photo**.

***

### **Step 1: Decide who may open the organization**

* Navigate to **Payroll Setups** and open **Setup Org Units**.
* **Show People (the organization tree) to every app user** is ticked to start with: every app user can open **Organization**.
* Untick it and press **Save** to open **Organization** only to HR and to people with someone reporting to them. Everyone else sees: *The organization tree is open only to HR and team leaders. Ask HR.*
* The change is recorded in **User Access > Change Log Viewer** under **Org Unit**.
* The setting is also on the web.

> **Example - a small team**
>
> Meera heads Sales, and Arjun and Kavita report to her. Arjun taps **People** and sees **Organization** - no switch, as nobody reports to him. At the top he taps Meera's card (badge **02**) to see Arjun and Kavita, then taps the **i** on Kavita's card and taps her official number to call her.


---

# 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-org-units.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.
