Unassigned People and Unresolved Managers
The chart displays one selected hierarchy. A person with no resolved solid-line manager is a root candidate, not automatically another displayed top card.
Root candidates who are not selected for the displayed hierarchy appear in the Unassigned strip beneath the chart. They are listed by name. They are not drawn as nodes.
Who becomes a root candidate
- Anyone whose solid-line manager is blank,
NO_MANAGER, or-1. That is normal. It is never an error. - Anyone whose solid-line Manager ID does not match any Person ID in the loaded source. Their reports stay attached beneath them. Data issues reports Manager ID {key} does not match any Person ID in this source — branch kept as a separate root. That wording names the data problem. The person is still a root candidate. Unless you set Root person to them, they appear as an unassigned person, not as a second displayed top of the chart.
An unresolved additional reporting manager is different. That extra line is dropped. Data issues reports Manager ID {key} does not match any Person ID in this source. The person stays under their solid-line manager.
How the displayed hierarchy is chosen
- Root person default Auto-detect top charts the root candidate with the most people beneath them.
- Every other root candidate is listed in Unassigned: {names}.
- Choosing an explicit Root person charts that person's branch. Every other root candidate moves to the Unassigned strip, including the previous auto-detected top.
- The Root person dropdown lists people who have at least one report, plus Auto-detect top.
Unassigned people are also counted as Unassigned: {N}. Search can match them; the match count may include ** · +{N} unassigned**.
This is the most common reason people look missing. They are not skipped rows. Check Unassigned before you treat the source as broken.