Org structure

Manage the departments, positions and locations that employee records use, and find the other shared HR lists.

Org structure holds the building blocks that employee records point to: departments, positions and locations. The same page also has tabs for the other shared HR lists: leave types, skills, work schedules and payroll.

Open Org structure#

On the People page, click Org structure. The page has these tabs:

Tab	What it’s for
Departments	The teams or divisions people belong to
Positions	Job titles, filled or not, with optional salary bands
Locations	Offices and sites
Leave types	The kinds of leave people can request. See Leave.
Skills	The shared skill list. See Skills.
Work schedules	Working weeks. See Work schedules and holidays.
Payroll	Payroll periods and entries, shown only with `payroll.view`. See Payroll.

Who can use it#

Permissions

employee.viewemployee.managepayroll.view

Viewing departments, positions and locations needs employee.view. Adding them, and renaming departments, needs employee.manage. Salary bands on positions are shown only to people with payroll.view.

Departments#

The Departments tab lists each department with its code. In the Everyrealm demo, for example, there are departments such as Executive (EXE), Investments (INV) and Technology (TEC).

Add a department
At the bottom of the tab, enter a Name (for example “Engineering”) and an optional Code, then click Add.
Rename a department
Click into the department’s name in the list, type the new name, and click anywhere outside the field. The change saves automatically.

Departments can also have a parent department, a description and a cost centre, but these can’t be set from the screen yet. If a parent is set through the UnitX API, the hierarchy can’t loop: a department can’t be its own parent or sit under one of its own sub-departments.

Positions#

A position is a job title, such as “Portfolio Analyst”. It exists whether or not anyone holds it, which is why it lives here rather than on a person. Each position in the list shows its salary band (if set and you can see it), its department and its status (for example open or filled).

Enter the title
On the Positions tab, enter a Title (for example “Software Engineer”).
Optionally choose a department
Pick one under Department (optional).
Click Add
New positions start with the status open.

Salary bands need payroll.view

A position’s salary band is pay data. People without payroll.view see a Salary band hidden badge with a lock instead of the figures, so they can tell a hidden band apart from a position that has none. Each time someone with access reads a salary band, UnitX records it in the audit trail.

A salary band, level and description can’t be set from the Positions tab yet; they can be set through the UnitX API.

Locations#

Locations represent offices or sites, such as the demo company’s New York, London and Lisbon offices. Each one in the list shows its city and status.

Enter the location
On the Locations tab, enter a Name (for example “HQ”) and an optional City.
Click Add
The location appears with the status active.

Locations also have an address, country, time zone and type (such as headquarters or office), which can only be set through the API for now. Job openings and HR holidays can refer to a location.

Limitations#

Departments, positions and locations can’t be deleted. Positions and locations can’t be renamed from the screen.
The add forms are shown to everyone who can open the page, but saving needs employee.manage.
Departments have no head-of-department field on the screen. Who someone reports to is set on people, and shown on the Org chart.

FAQ#

Why is the salary band hidden?

Viewing people and viewing pay are separate permissions on purpose. An administrator can add payroll.view to your role.

I don’t see the Payroll tab.

The Payroll tab appears only for people with payroll.view.

How do these relate to Teams in Settings?

They’re separate. Departments are part of your HR records; teams group members for work, such as project access and assignments.

Still stuck? Search the docs with ⌘K, open Help inside UnitX, or contact support.