Overview
An Organization groups contacts under a single, hierarchical entity — a company with its departments and people. Organizations are first-class customer-data objects: their attributes come from adopted Profiles, and they carry taxonomies, tags, relationships, workflows, ownership, hierarchy, and archive. For the bigger picture, see the Customer Data overview.Where to find it
Organizations live under Customer Data → Organizations.Properties
| Property | Type | Required | Description |
|---|---|---|---|
title | string | Yes | Display name. |
slug | string | Yes | Identifier — unique. |
parent_id | reference | No | Parent organization, for hierarchy. |
profiles | array | No | Adopted profiles — drive the organization’s attributes. |
taxonomies | array | No | Taxonomies applied to the organization. |
tags | array | No | Tags applied to the organization. |
Contacts
A contact belongs to an organization through itsorganization_id. An organization can group many contacts, and renaming the
organization updates the organization name shown on each of its contacts.
Hierarchy
Organizations nest into a parent/child tree — a company, its divisions, its departments. Hierarchy-aware queries resolve an organization together with all of its descendants. See Hierarchies.Behaviour & rules
- Can’t delete an organization with contacts — reassign or remove its contacts first.
- Attributes come from profiles — an organization with no profile has no custom attributes; adopt a profile to give it a schema.
- Archive, don’t hard-delete — organizations use Archive and can be restored.
Seeds
Organizations travel between environments as structural Seeds. An organization carries its title, slug, attribute values, and taxonomy references (resolved with reference helpers):Governance & permissions
A super admin or Master can manage any organization. Organizations carry Ownership, so a Journey Manager manages the organizations they own.API access
Organizations have full CRUD, plus restore and remove-from-hierarchy operations, and bulk actions for attributes, taxonomies, tags, ownership, workflows, and hierarchy. See the API reference.Related
Contacts
The contacts an organization groups.
Profiles
The attribute schema an organization adopts.
Hierarchies
Parent/child organization trees.