Relationship Between the Parent and Child Organisation
The parent organisation provides flexibility of products. For example, assume that there is a group company (CompanyA) also known as the parent company which has multiple child companies (Company B and C) under it. While creating the parent organisation, that is Company A, grant it the master level configuration. Therefore, while creating the child organisation Company B and C, they actually inherit those configurations from the parent organisation Company A.
With the parent-child relationship not defined, Zeotap is chosen as the parent organisation. Also, when the parent-child relationship is defined, Zeotap is considered as the parent organisation for the parent organisation in the parent-child relationship.
While creating a User, you have the flexibility while granting access. For example, assume that the General Manager (User A) of Company A wants to see have a bird’s eye view of all the activities happening across the Company B and C. These activities can range from the number of segments being created to number of Sources being created. You can grant User A the Admin Role with permission to monitor and control activities across the children organisations.