Published at: 2026-09-17
Org structure and influence map object relationships
Overview
Use this reference to understand the underlying data relationships for the Account Org Structure and Influence Map.
Account Department object
The predefined Account Department object’s API Name is
AccountDepartmentObj.| Field or relationship | Rule |
|---|---|
| Account | Required; identifies the Account that owns the department |
| Parent Department | Self-referencing field on the Account Department object |
| Available range | Departments under the current Account only |
| Cross-Account relationship | Not supported |
Contact Influence relationship object
| Field | Purpose |
|---|---|
| Belongs to Account | Identifies the Account that owns the relationship data |
| Parent Node | Self-referencing field that creates the parent-child structure |
| Associated Contact Name | Specifies the Contact displayed by the node; this field can be Empty |
Each map node represents one Contact Influence relationship record. The same Contact can appear in multiple nodes.
Data governance requirements
- Nodes in one relationship chain must belong to the same Account.
- Keep one top-level node for each Account, when possible.
- Before changing a shared tree data source, check whether other layouts reference it.