Org chart & reorg

/hcm/org-chart is the org graph + reorg simulator. AxisSynapse treats the organization as a graph with two edge types — SOLID (direct reporting) and MATRIX (dotted-line / functional). The admin surface lets you visualize, run structural risk detection (overwide span, excessive depth, rank padding, orphaned matrix), and simulate a reorg with full impact analysis before committing under 4-eyes apply.

TL;DR — Open HCM → Org chart. Browse the solid-line tree

• matrix overlays. Risk tab flags structural issues. Reorg simulator drafts changes; the apply step is step-up-protected
• 4-eyes (different admin than the simulator).

Before you start

• The org graph is the source of truth for reporting relationships. SCIM-pushed manager fields flow in if SCIM is configured (see SCIM provisioning).
• Matrix edges are independent of solid-line; you can have N matrix relationships per employee (with N capped per workspace policy).

Solid-line vs matrix

Span of control + structural risk

Simulate a reorg

1. 1

   Open the simulator

   Click Reorg simulator from the Org chart.

2. 2

   Draft changes

   Move employees between managers, change levels, create new business units, change manager assignments. Bulk operations supported.

3. 3

   Cycle detection

   The simulator refuses configurations that would create a reporting cycle (A reports to B, B reports to A).

4. 4

   Run impact analysis

   The simulator surfaces:

   • Structural risk delta — does this make risk better or worse?
   • Comp impact — proposed comp shifts (band changes, level changes).
   • Manager-scope changes — who'd see whose approvals.
   • Comp band membership changes — who'd move bands.
5. 5

   Save the simulation

   Audit log records HCM_ORG_REORG_SIMULATED. The draft is saved + accessible later (or to a different admin).

Apply a reorg (4-eyes + step-up)

1. 1

   A different HR admin opens the saved simulation

   Simulator can't apply their own work.

2. 2

   Review the impact analysis

   Confirm the changes match the workspace's intent.

3. 3

   Click "Apply"

   Step-up modal opens. Apply is step-up-protected.

4. 4

   Commit

   Audit log records HCM_ORG_REORG_APPLIED at critical severity + per-employee HCM_EMPLOYEE_POSITION_CHANGED for each row that changed.

Matrix edges

1. 1

   Open the employee's profile

   Matrix section shows current dotted-line relationships.

2. 2

   Click "+ Add matrix relationship"

   Pick the related manager + the relationship type (functional, project, mentor, etc.).

3. 3

   Add or remove

   Each change emits HCM_ORG_MATRIX_EDGE_ADDED or ..._REMOVED.

Every field, explained

Audit codes

For SIEM ingestion + compliance review, this surface emits:

See Reference → Audit codes for the canonical description of each. HCM_ORG_REORG_APPLIED is the critical-severity row — bulk reporting changes committed under 4-eyes + step-up.

Common gotchas

• "Simulator refused my change." Cycle detection triggered. Check that no two employees are reporting to each other through the proposed edges.
• "Risk flagged a manager I trust." Risk flags are descriptive, not prescriptive. Some healthy teams are deeper or wider than the default thresholds.
• "Apply succeeded but a manager dashboard is empty." The scope toggle remembers the prior setting; refresh + retry.
• "Matrix edge orphan flag won't clear." The employee the matrix points at has been offboarded. Remove the edge manually or re-target to a different person.
• "Reorg changed comp bands but I didn't intend it." Some position changes (level change, new geography) move the employee to a different band; the impact analysis names this before apply.

Troubleshooting