Overview

The org chart shows the position reporting structure for a selected effective date. Position-to-position Reports to values form the hierarchy; employee assignments can add position holder names when your access permits.

Use the chart to review structure. Edit the position’s Reports to value when the relationship should change.

What determines a position's place in the org chart
PositionThe position whose reporting line you are reviewing.
Reports toThe position directly above it in the reporting structure.
Effective dateThe date when that reporting relationship begins.
Org chart placementThe position appears beneath its Reports to position on the selected date.

What the org chart shows

Each position node can show:

  • Position name and number.
  • Vacancy or staffing status.
  • Job code and department.
  • Assigned employee names when you have employee access.
  • Positions that report directly to it.

Draft positions with current proposed values can appear in proposed views. Approved and proposed structures remain distinct.

Choose the effective date

Reporting lines can change by date. Select the date you want to understand before reviewing the hierarchy.

A future reporting-line change does not alter today’s chart. A backdated correction can change historical and current structure beginning on that date.

Change a reporting line

  1. Open the position whose reporting line you want to change.
  2. Select Details.
  3. Edit Reports to.
  4. Enter the effective date.
  5. Choose the position it should report to.
  6. Save the value and submit it for approval if required.

The available Reports to choices are active positions in departments where you can manage positions. FTE Tree prevents a position from reporting to itself, directly or anywhere through the reporting structure beneath it.

Position reporting lines can contain up to 25 levels, counting a top-level position as level 1. Reports to choices that would place the position, or any positions beneath it, below level 25 are not offered. If information changes before the form is saved, the same limit is checked again and the change is blocked with an explanation.

Top-level positions

A top-level position has no Reports to value. If your organization requires Reports to, a user with Manage positions in All departments can still leave it blank to create an intentional top-level position.

An organization can have more than one top-level position. You do not need a generic root position.

Changing the field setting to Required does not automatically add reporting relationships to existing top-level positions.

Access and employee names

Position visibility follows position access for the relevant department. Employee names follow employee access for each employee’s owning department.

This means you can see a position node and its vacancy or staffing state without seeing the employee’s name. That is expected access behavior, not missing assignment data.

What happens when a position above others is archived

When a position with direct reports is archived, those positions move to the next active position above it. If the archived position was top-level, its direct reports become top-level.

Restoring the archived position does not automatically rebuild the former relationships. Review Archive, restore, or discard a position before archiving a position with direct reports.

Common questions

Why is a position missing from the chart?

Check the effective date, approved versus proposed view, archive status, department access, and whether the position has current values for that date.

Why can I not choose a Reports to position from another department?

Reports to choices are limited to active positions in departments where you can manage positions.

Why did a position become top-level?

The position it reported to may have been archived, or FTE Tree may have prevented a circular redirection while preserving a valid hierarchy.