Create a business unit and department
What this achieves
Section titled “What this achieves”Business units, departments, and teams are the three levels Humavera models your organization with. This page covers building them as a structure, including nesting departments and adding teams beneath them.
Required role: Administrator.
Before you start
Section titled “Before you start”Create your legal entities first — business units sit beneath them. If you are creating your very first department, Build your organization covers the form field by field; this page covers the structure around it.
- Go to Organization → Business Units.
- Create a business unit with its Name, Code, Description, and Head.
- Go to Organization → Departments and create the departments beneath it.
- To nest one department under another, set its Parent Department.
- Go to Organization → Teams to add teams within a department.
The three levels
Section titled “The three levels”| Option | Description |
|---|---|
| Business Unit | The top level beneath a legal entity. Carries a name, code, description, and head. |
| Department | A functional grouping within a business unit. Can be nested beneath another department. |
| Team | A working group within a department. |
The structure tree at Organization → Structure shows all three together and can be expanded and searched, which is the quickest way to check what you have actually built.
Departments can nest
Section titled “Departments can nest”A department can have a parent department, so a hierarchy inside one business unit is possible without adding a separate level.
Example: at HC Corp UK Ltd, Payroll sits beneath Finance as a child department. Both are departments; one is the parent of the other.
Nest where the relationship is genuine. Nesting for tidiness produces a tree nobody can navigate and reporting that needs explaining.
A department detail shows what depends on it
Section titled “A department detail shows what depends on it”Opening a department shows its head, parent, and cost centre, with tabs for its Teams and its Employees and a count on each.
Use those counts before making a structural change. They are the fastest answer to what a change to this department will affect.
Example: opening Engineering at HC Corp UK Ltd shows its 34 employees and its teams, so the consequence of splitting or renaming it is visible before you act.
Deletion is guarded
Section titled “Deletion is guarded”Deleting a business unit, department, or team warns that the action cannot be undone, and names what will block it.
| Option | Description |
|---|---|
| Business Unit | Cannot be deleted while departments or child units belong to it. |
| Department | Cannot be deleted while employees or sub-departments belong to it. |
| Team | Cannot be deleted while employees are assigned to it. |
That matches locations and positions, which protect against the same thing. Use the employee and team counts on the department detail to see what has to move first — until it does, the deletion will not go through.
What happens next
Section titled “What happens next”Structural units become selectable on employee records, and reporting groups by them. Approvals do not follow this tree — they route along each employee’s reporting manager — so building the structure is not the same as setting up who approves what.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved