Company Structure: Parent and Child Organizations

The short answer: If your company has more than one organization in Proof, those organizations are connected in a company structure — a hierarchy where parent organizations can manage settings and access data from their child organizations. Understanding this structure helps you know who can see what, and how settings flow across your company.

You can manage your own child organizations with Command Center. Learn more about Command Center.

Key Terms

Here are the terms you'll see when navigating your company structure:

• Root organization: The foundational organization for the entire company. All other organizations are children of this org.
• Parent organization: Any organization with one or more child (subsidiary) organizations. Users in a parent org have access to its children.
• Child organization: A subsidiary of a parent org.
• Home organization: The primary organization a user belongs to. If their home org is a parent, they can navigate into any child org below it — always with the same role, regardless of which org they're viewing. Learn more about roles.

If your company has only one organization, that org is both the root and the home org for all users. An owner is required only at the root org level — no other level requires one.

The maximum depth of an organizational hierarchy is 4 levels. A parent organization can have unlimited child organizations.

The image below shows an example of a company structure as it appears in your account.

Settings Across Your Company

The table below shows which settings child organizations inherit from their parent.

¹ The child org inherits the parent's logo unless the child specifies its own logo or has branding set by Command Center. If the parent updates its logo after the relationship is established, the change carries to the child only if the child was still inheriting at that time.

² The child org inherits the parent's plan details at the time the account or relationship is created. After that, the plans are separate — if the parent changes its plan later, that change is not inherited by the child.

User Access and Permissions

A user's access to each organization depends on both of the following:

• Their user role
• Their home organization

Owners and admins of parent organizations can access and manage child organizations. Users in child organizations — regardless of role — cannot access their parent org.

• Owners and admins can switch to a child organization to act on its behalf.
• Notaries at the parent level can answer calls for transactions created at the child level.
• Team members can access transactions created for their home org and any child orgs below it.
• No user in a child org has any access to the parent org — including admins and notaries.

Read more about user roles and permissions for your organization.

Example: Company Structure and Permissions

The example below shows an organizational structure with Headquarters as the root org.

Here's how permissions work in this example:

• Headquarters can access transactions, settings, and data for all organizations in the company.
• Any team member from Regional Office 1 can access transactions from North Office, County Office, and City Office.
• An owner or admin from Regional Office 2 can change settings for Regional Office 2, East Office, and West Office.

Summary Checklist

• Your company structure is made up of a root org, parent orgs, and child orgs — up to 4 levels deep.
• Parent org owners and admins can access and manage child orgs; child org users cannot access parent orgs.
• Some settings (like your logo) inherit from parent to child; others (like billing) are set independently.
• A user's access depends on both their role and their home organization.

Updated May 05, 2026 13:25