Involvements

Parent Child Involvements

Parent Child Involvements

A parent Involvement is one that has one or more other Involvements associated with it in a Parent Child relationship. The purpose is to be able to enroll lay leaders (with the OrgLeadersOnly role) in the Parent Involvement to give them the ability to view and communicate with the members and guests of the Child Involvements. It also allows the leader to take attendance for these Child Involvements. This is a better option than enrolling lay leaders in Involvements that they really do not attend just so they can access the members or take attendance.

When viewing a Parent Involvement, you have the option to email the leaders under that Parent Involvement or all the members under that Parent Involvement.

See also

Parent/Child Involvements - Emailing

Facts about Parent Child Involvements

  1. An Involvement can have only one Parent Involvement.

  2. A Child Involvement can itself be a Parent Involvement for other Child Involvements.

  3. You can have only these layers of child Involvements: Child > Parent > Grandparent. In other words the Parent Involvement for a Child Involvement can, itself, be the Child Involvement of another Parent Involvement. However, you cannot carry that relationship any further.

  4. The Child Involvements must be in the same Division as the Parent Involvement.

  5. Those enrolled in the Parent Involvement must have a Leader Member Type in order to access the Child Involvements.

  6. The leaders should also have the roles Access, OrgLeadersOnly, and Attendance (optional).

  7. If you use a normal Involvement for the Parent Involvement - one that has regular members - only the leaders will be able to access the Child Involvements.

Note

A user with the Admin role can view the Member Types in Admin > Advanced > Lookup Codes to see the Attend Type for each one, and edit them if necessary.

See also

Lookup Codes

Make the Parent Child Association

You must have the Edit role to access the Child Involvement Management page.

Step 1

For the Parent Involvement, either create a new Involvement or use an existing one in the same Division as the Child Involvements.

Step 2

Enroll those you want to have access to the Child Involvements, assigning them a Member Type that has an Attend Type of Leader.

Step 3

While on that Involvement page, select Blue Toolbar > Gear > Child Involvement Management.

Select the Involvements that you want to be the Child Involvements. This makes the association immediately. There is no save button.

Caution

Involvements that already have a Parent Involvement will display in pink. Any Involvement that is a Parent Involvement will display in blue.

You will not be able to select an Involvement that is already a Child Involvement for another Parent Involvement. However, you can select a Parent Involvement and make it a Child Involvement under this Parent Involvement.

Removing Parent Child Associations

Step 1

Go to the Parent Involvement and select Child Involvement Management from the Toolbar.

Step 2

Uncheck the Involvements you no longer want to be Child Involvements. This takes effect immediately. There is no save button.

Note

Before making an Involvement Inactive, you should remove the Parent Child relationship.

Use Case 1

To give a lay leader with the OrgLeadersOnly role access to the youth Life Groups he oversees, without enrolling him in each class, enroll him as a Leader in the Parent Involvement (for example, Youth General Officers). Once the Parent Child association is established, he can view the Child Involvements and their Members to email them, track their attendance, and more.

Use Case 2

To give a leader coach access to the groups he coaches, set his own disciple-making Involvement as the Parent Involvement, with him as the Leader, and set the other disciple-making Involvements he coaches as its Child Involvements. He can then access those groups from his own Involvement.

See also

Lay Leaders as Users on TouchPoint

Report

A recipe is available for a SQL Report that a user with the Admin role can add to your database. When you run this report, it will display every Involvement that is in a Parent Child relationship. The Involvement ID# is a link to each specific Involvement. Use it to keep track of which Involvements are using this special relationship.

Note

Be sure the Admin user adds the report to the Report Menu so that other users can access it.

See also

Parent Child Involvements Report



Latest Update

10/23/2026

Added role requirements, updated the Lookup Codes path, and rewrote the Use Cases.