---
title: "Owner Hierarchy Connector Guide"
slug: "owner-hierarchy"
updated: 2026-10-22T15:02:22Z
published: 2026-10-22T15:02:22Z
canonical: "docs.safe.security/owner-hierarchy"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.safe.security/llms.txt
> Use this file to discover all available pages before exploring further.

# Owner Hierarchy Connector Guide

The **Owner Hierarchy Connector** allows you to configure the [Roll-Up Owner Reports](/balbixhelp/docs/roll-up-owner-reports), which displays a hierarchical view of asset ownership within a selected asset group. It shows each owner, their assigned assets, and allows users to expand entries to view team members and their associated asset data. Users can manually refresh the report to update it with the latest information.

To add a **Owner Hierarchy Connector**, follow this procedure:

[Embedded content](https://scribehow.com/embed/Owner_Hierarchy_Connector_Guide__igfWJQ_eRpala2Pq6I77bg?as=scrollable)

This is an example of the required table structure:

| first_name | last_name | email | supervisor_email |
| --- | --- | --- | --- |
| Alice | Smith | [alice.smith@example.com](mailto:alice.smith@example.com) | [bob.jones@example.com](mailto:bob.jones@example.com) |
| Bob | Jones | [bob.jones@example.com](mailto:bob.jones@example.com) |  |

This table defines people and their reporting relationships. Each row represents one person, with their name and email. The `supervisor_email` field links them to another person in the table, creating a hierarchy. In this example, Alice reports to Bob. Balbix uses this to build ownership chains and assign responsibility across assets or risks.

> See Also:
> 
> [Roll-Up Owner Reports](/balbixhelp/docs/roll-up-owner-reports)