Organizational Unit

Organizational units represent nodes in a company’s structure - departments, divisions, teams, or similar groupings. They can be nested via a parent reference to form a hierarchy. All properties follow the dated property model.

Properties

Property	Description
`name`	The unit’s display name
`description`	Optional description
`email`	Contact email address
`phone`	Contact phone number
`tier`	The unit’s level in the organisational hierarchy
`source_external_id`	The unit’s primary key in the source system, as written by the last integration that synced it. Must always be mapped, but see the warning below before reading it.
`source_external_parent_id`	The parent unit’s primary key in the source system, as written by the last integration that synced it. Used to resolve the hierarchy; read `parent_id` instead.
`custom_properties`	See Custom Properties

source_external_id and source_external_parent_id hold whatever the integration that synced the unit last put there. A unit fed by two integrations gets its values overwritten on every sync. Use the organizational_unit_mappings relation (relations=organizational_unit_mappings on the /v2/org/organizational-units endpoints) for the unit’s id per integration, and the top-level parent_id field for the parent. See Source Properties.

Core Concepts

Data Model

Expressions

Configuration

Other

Properties

​Properties

Properties