What is a Parent-Child relationship?

a parent child relationship refers to the way you structure your customer database here are some scenarios where a parent child relationship can be useful you have customers that have different subsidiaries, and you want to keep them as separate accounts you have customers that use the product differently depending on the department/team, and you want to track health per department each of your customers has different products/projects/campaigns that you want to track individually, so you need a third entity to be tracked as a child of the parent company this type of structure is common, especially if you want to track https //kb custify com/health scores , https //kb custify com/lifecycles , usage, renewals, and so on for both the parent and child entities assigning companies in a parent child relationship there are multiple ways of assigning companies in a parent child relationship through an api you can find more details in our http //docs custify com/ through a csv import you can bulk assign the child companies under the corresponding parent companies using the data importer tool available under settings —> https //www custify com/kb/knowledgebase/csv data importer/ the type of import you need to use is company csv, and the only prerequisite is that the parent company needs to exist in custify in the csv file, it is mandatory to add the parent company’s id when mapping the company attributes, make sure to map the parent company id under the attribute parent company for the relationship to be correctly created directly from the ui there are a few different ways to assign the parent company directly from the interface from the https //kb custify com/customer 360 profile —> actions —> add parent company from the https //kb custify com/customer list view , select the company/companies you want to assign under a particular parent —> actions —> add parent company from https //kb custify com/playbooks —> playbook step assign parent company child parent data flows child companies once you assign one or multiple companies to a parent, you will be able to see the list of child companies under the child companies tab on the parent https //kb custify com/customer 360 profile there is also a default custify metric named child companies count that returns the number of child companies a parent has assigned events events will bubble up from the user to the company they are assigned to if this company is assigned as a child company to another company, the events will also bubble up to the parent company company only events (events that are sent at the company level and are not generated by users) also bubble up from child to parent company attributes the parent company’s attributes will not be influenced in any way by the child companies’ attributes if you decide to structure your data using the parent child relationship, you need to send attribute values for both entities alternatively, you could use the https //kb custify com/calculated metrics module (function add entity ) to build metrics based on the child companies attributes (e g , average of child companies attributes, sum of child companies attributes etc ) email communication sending emails you can send emails from custify only to the people directly assigned to that company mapping emails emails sent through gmail/outlook are being mapped to the person in custify, as well as the company/companies they are directly assigned to if a user is assigned to a child company and is not assigned to the parent company, you will not be able to send emails from the parent company to the people assigned to the child company also, you will not see the emails sent/received to/from the users assigned to the child company at the parent level depending on how your processes are built, you can consider assigning the users to both parent and child companies tasks the tasks you create for a child company do not bubble up to the parent company notes the notes you add on a child company do not bubble up to the parent company tickets tickets sent through integrations are mapped based on the email address of the user the ticket will also bubble up to the company the user is assigned to, but not to the parent company