Overview
The Org Chart block draws an interactive hierarchy from any flat list of records. You bind a data list, point Primary Key at each record's own ID and Parent Key at the ID it reports to, and the block lays the tree out automatically, with an optional hover Preview Card. Each node is a fully composable card you design like any other part of your app.


A new Org Chart arrives pre-built with an avatar-name-role card and a manager preview card.
Tip: Use it for reporting lines, team structures, or any parent-child hierarchy stored as flat records with an ID and a parent-ID column. For tabular people data without hierarchy, prefer a Table. For data that is already nested (children stored inside each record), use Tree View. The Org Chart renders tree-shaped hierarchies only and is not suited to free-form node-and-edge diagrams.
Note: The Org Chart is available in web apps only. It does not render in mobile apps, so use a Table or a list there.
Content Properties
Property | Type | Default | Description |
|---|---|---|---|
Data ( | list of records (bindable) | Sample list of 10 employees | The flat list of records to chart. Each record becomes one node. No nesting required — the block builds the tree from the key relationships. |
Primary Key ( | field mapping |
| The field in each record that uniquely identifies it — the node's own ID. |
Parent Key ( | field mapping |
| The field holding the ID this record reports to. Root nodes have no value here. |
Initially focused node ( | string (bindable) |
| On load, the chart focuses this node and highlights its whole reporting line up to the root. Bind to the signed-in user's ID for a "your place in the org" view. |
Slots → Preview Card ( | slot | Pre-filled card | A floating card shown when the user hovers a node. Pre-filled on new blocks with the person's photo, name, role, and manager details. |
Appearance Properties
Property | Type | Default | Description |
|---|---|---|---|
Orientation ( | Vertical | Horizontal | Vertical | Tree grows downwards (Vertical) or left-to-right (Horizontal). |
Edge Appearance → Default Edge | Color, Style (Solid | Dashed | Dotted) | Light gray, Solid | How the connecting lines between nodes are drawn. |
Edge Appearance → Focused Edge | Color, Style (Solid | Dashed | Dotted) | Brand color, Solid | How the lines on the highlighted path, from the focused node up to its root, are drawn. |
Styles ( | style set | Full width, 640px height | Width/height, margin, padding, background, border, position. |
Visibility ( | condition | — | Shows or hides the whole block. |
Events
| Event | Trigger | Payload |
| On Select Node | User clicks a node | selectedItemKey (the node's Primary Key value), selectedItem (the full record) |
Methods
Method | Parameters | Description |
|---|---|---|
Highlight Node |
| Focuses the node and highlights its reporting line up to the root. An unknown ID clears the highlight. |
Node Context Bindings
The block exposes no top-level state keys. Inside the node card and preview card, each node's details are available as context:
Binding | Type | Description |
|---|---|---|
{{ id.context.item }} | object | The full record behind the node being rendered |
{{ id.context.isFocusedUser }} | boolean | Is Focused Node — true on the focused node |
{{ id.context.isAncestorOfFocusedUser }} | boolean | Is Ancestor of Focused Node |
{{ id.context.isDescendantOfFocusedUser }} | boolean | Is Descendant of Focused Node |
{{ id.context.childCount }} | number | Child Count — number of direct children of the node |
{{ id.context.descendantCount }} | number | Descendant Count — number of direct and indirect children of the node |
Behavior & Gotchas
⚠ Nothing renders until data, Primary Key, and Parent Key are all set
The chart area stays empty — no error, no placeholder — when the bound data is empty or either key mapping is missing. If your chart is blank, check all three first.
⚠ A parent ID matching no record promotes the node to root
A record whose Parent Key points at an ID absent from the data is kept but promoted to a top-level root. Filtering the data to one department strands members whose manager was filtered out — they float to the top.
⚠ Initial Focus ID must match a Primary Key value exactly
When Initially focused node matches no record, the chart loads with no focus and no highlight — silently. Bind it to a value you know exists (e.g., the signed-in user's ID).
⚠ Circular parent references split the tree
If records form a reporting loop (A reports to B and B reports to A), every node in the loop stays on the chart, but each one shows as its own top-level root with no reporting line. Records that report to a node in the loop also move to the top. There is no warning, so if a team looks disconnected, check for circular parent references.
⚠ Multiple parents and duplicate IDs
If Parent Key holds a list of IDs, the node is drawn under the alphabetically first parent and the other parents are grouped. Records with a duplicate Primary Key, or an ID that is not text or a number, are skipped.
Common Patterns
Employee Directory with Reporting Lines
Bind flat employee data: Bind Data to your employee records query. Set Primary Key to
userIdand Parent Key tomanagerId.Set initial focus to current user: Bind Initially focused node to the signed-in user's employee ID so the chart opens highlighting their position.
Design the node card: Select the node card in the canvas. Bind the avatar's image to
{{ orgChart1.context.item.photo }}, the name text to{{ orgChart1.context.item.name }}, and the role text to{{ orgChart1.context.item.role }}.Drive a detail panel from On Select Node: On On Select Node, open a Drawer or side panel bound to
{{ orgChart1.events.onSelectItem.selectedItem }}to show the full employee profile.
Related Blocks
Block | Relationship |
|---|---|
For data that is already nested, with expand/collapse; it does not build the tree from flat parent-ID records | |
For stage-based item pipelines with drag-and-drop between columns | |
Prefer for tabular people data without hierarchy |