Skip to main content

​
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

PropertyTypeRequiredDescription
titlestringYesDisplay name.
slugstringYesIdentifier — unique.
parent_idreferenceNoParent organization, for hierarchy.
profilesarrayNoAdopted profiles — drive the organization’s attributes.
taxonomiesarrayNoTaxonomies applied to the organization.
tagsarrayNoTags applied to the organization.
An organization’s custom fields come from the profiles it adopts; ownership applies as on any customer-data object.

​
Contacts

A contact belongs to an organization through its organization_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): 
[
  {
    "object_type": "organizations",
    "data": {
      "title": "Lehner PLC",
      "slug": "lehner-plc",
      "general": {
        "annual_revenue": 571815.45
      },
      "taxonomies_ids": [
        "{{getContentInstance('default-organizations', 'slug', 'automotive')}}",
        "{{getContentInstance('default-organizations', 'slug', 'electronics')}}"
      ]
    }
  }
]

​
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.

Contacts

The contacts an organization groups.

Profiles

The attribute schema an organization adopts.

Hierarchies

Parent/child organization trees.