Parent-Child User Hierarchy

The relationship between Parent-Child users also referred to as "User Hierarchy," is crucial in determining access levels and interactions among users. It highlights the importance of each role within your organization. Understanding the dynamics of Parent and Child users reveals a structure that controls capabilities and shapes how your organization operates. Below, we’ll discuss this user-type relationship and why it is a key element in user hierarchy within an integrated organizational environment.

Parent & Child Users

As mentioned above, the parent-child user relationship is essential to each user’s access capabilities.

A Parent User is the first user set up to when boarding an entity (Merchant, Referrer, or Facilitator-level).
A Child User is any user created by a Parent User for an entity.

Parent/Child User Relationship vs. Multi-Merchant Location Structure

While both concepts take advantage of user access, there are some distinct differences between their purpose and usage:

Parent/Child User Relationship

Purpose: Limit access to particular features and functionalities on a per-user basis within the same entity account.

Use Case: 1 business with 1 location and multiple users, with only one needing access to create a payout.

Multi-Merchant Location Structure

Purpose: Enable one main Merchant user to easily view and access other Merchant entities operating under the same corporate umbrella on the platform and generating revenue.

Use Case: 1 business with multiple locations, where the primary business owner needs access to each location’s Portal account.