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 and 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 when boarding an entity (merchant or partner level).
A Child User is any user created by a Parent User for an entity.
The parent (admin) user of any child (standard) user can access and view the child user’s associated entity (merchant) because its hierarchy is the source of the child user’s access to the portal. As a result:
The parent user will have full view of the child user’s merchant account, but the child user is unable to view the parent user’s view.
Deactivating partner-level parent users that are associated with the entity’s API key or are the primary parent user login will remove access from all associated child users to their respective entity (merchant).
Parent-Child User Relationship versus 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: One business with one 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: One business with multiple locations, where the primary business owner needs access to each location’s Portal account.