The job of this console
Keep the manager tree true: reassign a reporting line, confirm hierarchy nodes, and align master lists so approval chains and capacity still resolve. Search, then write the manager field on Employee.
Admin · People
Org Structure
Reporting lines, hierarchy nodes, and HRMS master lists sourced from EmployeeModel and Application Config.
Scroll to Flowcharts. Scenario: Reassign a manager and update master lists.
Reporting lines
The tree managers already live on
Org structure is reporting lines, hierarchy nodes, and HRMS master lists sourced from Employee and Application Config — not a decorative chart with its own people table.
Admin → Org structure
Route
/admin/org-structure
Org flag orgStructureEnabled
HR Admin · Org Admin
Seat at the table
HR and org administrators. Employees browse a read-only organization chart under People when that flag is on. Managers do not drag the tree here.
The working rhythm
Open Reporting, find a person, reassign manager, save, then spot-check an approval simulation and the People org chart. Use master-list tabs only for config values, not as a second employee directory.
Moments that bring you here
Reorg day. A skipped manager breaking leave approval. New department node before year-end planning. After a bulk employee import, to repair orphans.
ⓘ
Employee is the source
Manager changes write
fs_employee_model. Application Config still owns list values. There is no shadow org table.Flowcharts
1 — Reassign a reporting manager
Search the tree, pick a new manager, then confirm EmployeeModel updated.
flowchart TD
A[Open Org structure] --> B[Reporting tab]
B --> C[Search employee]
C --> D[Reassign manager]
D --> E[Writes manager_id]
E --> F[Hierarchy / master lists as needed]
- 1Open Org structureAdmin → Org structure.
- 2Reporting tabEmployee tree plus manager reassign.
- 3ReassignSearch the new manager, then save.
- 4Optional listsDepartment, designation, team, cost center live on Master lists.
Overview
Org units are derived from EmployeeModel — there is no shadow org table. Master lists write Application Config HRMS lists.
How to use
1. Flattened forests
Hierarchy nodes infer type from depth; they are not a second source of truth.
2. Check payload before success
Empty reassign payloads must not show a success toast.
3. Use App Config for extra lists
Deep list edits can also be done in Application Config.