> ## Documentation Index > Fetch the complete documentation index at: https://docs.salu.com.vc/llms.txt > Use this file to discover all available pages before exploring further. # Hierarchy > The Branch × Sector × Position combination that positions the employee. The **Hierarchy** is the **Branch × Sector × Position** combination that defines an employee's "position" in the company. It is not a manager↔report relationship: it is an **organizational/positional** structure, and it is precisely what determines the **occupational risks** and the **required exams**. > Where the person works (**Branch**) + the environment they work in (**Sector**) + what they > do (**Position**) = the Hierarchy. ```mermaid theme={null} flowchart LR U[Branch] --> H((Hierarchy)) S[Sector] --> H C[Position] --> H H --> E[Employee] ``` ## How the hierarchy is created You **do not create the hierarchy directly** through its own endpoint. It is **resolved or created automatically** when you register an Employee providing `branch_id`, `sector_id` and `position_id`. The platform ensures the `(branch, sector, position)` combination is **unique** per organization — if it already exists, the employee is linked to it; if not, it is created. That's why the onboarding prerequisite is having **Branch, Sector and Position already registered** in the organization. See the [Set up the company structure](/public-api/en/flows/company-setup_en) flow. ## Why this matters in occupational health Two employees can work in the same company and even the same branch, but if they are in **different sectors and positions**, they may have **completely different exposure risks and required exams**. The hierarchy makes that explicit and traceable.