- Public individual: a natural person with no relation with other contact type.
- Individual subsidiary of a parent individual: binding relationship between two individuals.
- Relay individual of a structure: a natural person who serves as contact point for a legal person.
- Individual member of a structure: a natural person identified as workforce of a legal person.
- Public structure: file of the legal person that gathers the historicals of different individuals associated with it.
- Structure subsidiary of a mother structure: binding relationship between two structures.
...
A "member" is an individual that is a Member of a structure. Imagine I am Bertrand Bechet, individual contact Then Jean-Marie is a relay of adidas. If Bertrand Bechet is a member of adidas, then Jean-Marie will see Bertrand in the Manage my members section of b2b portal and Jean Marie will be able to distribute tickets to Bertrand from the b2b portal.
...
Contact files (both individual and structure ones) can be linked to one another. In this page we are going to explore the different connections that can be established between them.
These are the connections that can be established between individual contact files:
When linking individual contact files you will establish a hierarchy between them. This hierarchy, in Secutix, is defined by the terms "Parent" and "Child". This doesn't mean that those contacts are really family, but that one of them is the principal one -the "parent". For example, it could be a group of friends, and the "parent" one the one that usually pays and manages purchases and reservations.
Depending on your institution and whether the contact is a relay or not, the available options can vary.
A "child" contact file, in relationship to the "parent" connections, can have different roles:
- Member: Any individual who is a member of a structure (aka.: works at that company) could be linked as a “child” to a relay contact of that structure. The relay would then be able to see the member list of the structure and distribute tickets to them through his account on the internet ticket shop. The relay would also be able to remove members from the list.
- Subgroup (Subgroup member): As relays can also be linked between them, there is the possibility to establish this very particular kind of relation: Contact A is a relay of a subsidiary company. Contact B is the relay of the mother company of that subsidiary. Contact A would be linked to contact B as a "child" with a "subgroup" role.
- Invoice contact: The "child" contact billing address can be used by the "parent" contact for the order he is buying on ticket shop. If the "child" contact is a relay (and the shop is configured as "structure buying"), the addresses of the structure he's linked to will be proposed instead.
- Shipment contact: The "child" shipping address can be used by the "parent" contact for the order he is buying on ticket shop.
- Distribution partner: The "child" contact, as a distribution partner, would be a relay. The "parent" contact would then be able to send tickets to him.
- Family: Family and friends of the "parent" contact, who would be able to buy tickets on behalf of the "child" and see his orders.
- There are a couple options that are no longer used even if they are still available: Structure member and sponsor.
A "parent" individual contact file, in relationship to the "child" connections, can have different roles:
- Family: Only "parent" individuals can select this option.
- Shipment contact
- Distribution partner: Only "parent" relays can select this option.
When only a relay is set for a structure, they will become the primary contact. If a structure has more than one relay, you'll be able to change and choose who needs to be the primary relay: They'll be able to see and modify the information of their structure on the ticketshop, including the structure criteria and financial management.