Human Capital Managementoperational
Organization & Positions
How do I keep the org chart, positions, and job descriptions current as the organization changes?
HCM is the working surface for the organizational model the whole platform shares. Units nest to any depth, positions report to other positions, and each seat — a position placed in a unit — carries its own flags, clearance level, and staffing limit.
Referenced across4 other parts of continON
How it works
The organization is a self-referencing hierarchy of units: each unit has a parent, a type, and its own currency and logo, with a headquarters flag for the top. The org chart screen renders the tree directly from these records, so what you see is what access rules, workflow routing, and reporting actually use.
Positions are defined once at the title level — reporting line, pay grade, base pay, and generic responsibilities — then placed into units as seats. A seat carries head-of-unit and managerial-position flags, a clearance level, a maximum number of holders, and an editable rich-text job description, so the same title can behave differently in different units.
Because permissions, dashboards, and file access on the platform attach to the seat rather than the person, keeping this screen current is what keeps access current. The canonical explanation of the model lives on the platform organization page; HCM is where HR maintains it day to day.
What the register holds
4 on the record- Arbitrary-depth unit tree
- Units nest without a fixed level count; each unit records its type, parent, currency, and logo, with an explicit headquarters flag.
- Seats, not just titles
- A position placed in a unit becomes a seat with head-of-unit and managerial flags, a clearance level, and a maximum-holders limit.
- Rich-text job descriptions
- Each seat carries an editable job description and position criteria maintained on the position screen, used downstream by vacancies.
- The chart other modules obey
- Workflow actor resolution, notification targeting, and document permissions across continON resolve against these same unit and seat records.
What this touches
- Organization & positions platform model
The canonical seat-based model; HCM is its primary maintenance surface. - Identity & access
Permission bundles are granted to seats, so position changes carry access with them. - Recruitment
Every vacancy is opened against a defined position. - Employment & contracts
Employment assignments bind a person to a seat over time.
See organization & positions running in continON.
A guided walkthrough on a sanitized demo tenant — this capability inside its module, on the shared platform.