---
title: Family Systems
slug: docs/family-systems
docTags: 
createdAt: 2021-08-04T18:22:15.000Z
---

Regpack projects will be one of two structures: family/group or individual. An individual structure is advised for single applicants, and a family/group structure allows a single *parent* applicant to register a series of *child* *a*pplicants. This nested structure is very flexible, and some examples might include:

- A parent registering their children for camp
- A manager (*parent*) registering employees (*child*) for a conference
- A single individual (*parent*) registering multiple grant applications (*child*)

Essentially, if there is ever a set of forms that should be filled out *multiple times, *then it is advised to use a family/group structure.

To determine whether a project has been established with a family/group structure, log into the back end. The Users tab will look as follows and contain a tab for all users, a tab for your parent users, and a tab for your child users:

![](https://api.archbee.com/api/optimize/uAn0OdaGcbD9zMQmvOuP7/CjpuAOrH69g5oydfibtYd_screen-shot-2021-09-08-at-111429-am.png "In the provided example, the parents are organizers, and the children are attendees.")

# Key Parameters

There are a few parameters that are necessary to link the parent to the child. 

| Name           | Type    | Required | Description                                                                                                              |
| -------------- | ------- | -------- | ------------------------------------------------------------------------------------------------------------------------ |
| `clogin_id`    | integer | false    | This is used to identify both parent and child users. Each level (both parent and child) has its own unique `clogin_id`. |
| `connected_to` | integer | false    | This is the `clogin_id` of a parent.                                                                                     |