Core Docs - Engagement - Defining Group Requirements

Rock Version: v19.0
Last Modified: 2026-03-02 8:59 AM

You manage group requirements under Admin Tools > Settings > General > Group Requirement Types.

Editing a requirement allows you to provide the following configuration options.

As noted above, the Expire Duration is how many days Rock will wait before checking requirements again. With background checks it typically isn't necessary to re-check every day, or even every week or month. But there are edge cases to consider. For instance, let's say someone passed a background check yesterday and, as a result, shows up as meeting the group requirement. Then today something changes with the requirement (e.g., the Data View is updated) and the person no longer meets the requirement. The Calculate Group Requirements job will not re-check this person's requirement until after the Expire Duration has passed. In such cases the person will appear as meeting the current requirement, even though they don't.

If someone does not meet a requirement and the due date has not been reached, then the person is considered to be in a warning state.

Tips for Creating Data Views and SQL Expressions
When creating data views and/or SQL expressions for group requirements keep these two things in mind:
- Meets The data view/SQL expression for meets should return a list of all the people in the database that meet this requirement.
- Warning This data view/SQL expression should return a list of all the individuals in the database in a warning state.

When you apply a requirement type to a group or group type (see the following sections below for instructions on that) you have the option of allowing group leaders to override the requirement for individual group members. For other staff or volunteers, you can indicate who can override requirements by accessing the security for the requirement type by clicking the ti ti-lock icon and adjusting permissions for Override.