Rock U - Groups - Group Requirements v13

Transcribed Video Content

Group requirements ensure that everybody in a group has certain requirements met, whatever requirements exist to to get into or stay in that group. In this video, we're gonna show you how to set up group requirements and how to apply them to groups. So, we're gonna start by going over to people and group viewer, and we're gonna look at some of our small groups. So we'll open up, section a or section b here, and we'll look at, Greg's group. And as we scroll down, you can see how the members of this group have a little red icon next to their name. And in this case, is red, which means the person does not meet the requirements of this group. You'll see a yellow icon if the person is in a warning state, which we'll look at in a minute. But first, let's show you how to set up group requirements. And so, to do that, we're gonna go to, general settings under admin tools, and we'll click on group types. And we'll come down here to our small group. , there's a couple ways that you can add requirements to a group. You can set them up at the group level for individual groups if the group type is configured to allow that. So, here we have an option, enable specific group requirements. And so, that lets you put requirements on at the group level rather than at the group type level. The other way to do it is to define the requirement at the group type level where it applies to all groups of this type. And that's what we'll do here. So, we'll come down. Again, we already have our requirement created and in place for this example. But to add group requirements, you would simply come down here. And, , we'll we'll get rid of this one just so you can see what it looks to add it from scratch. And, and we'll go ahead and add one. So, you have the group requirement type. And in this case, we only have one configured. And we're gonna show you how to set this up in a minute. But we only have one background check required. Then you can determine what role, if any, needs to have this requirement met. So, if you only required a background check for your leaders, then you would pick leader. Or if you only required it from your members, then you'd pick members. But to apply it to everybody, we'll just leave it blank. And then you have this option here, members must meet this requirement before adding. And that's pretty straightforward. If this is checked, then you won't be able to put people into the group unless they meet the requirement. We're gonna leave that unchecked for now and just leave it set up this. And so we'll save that, and then save our group type. And there we've got our requirement applied to the group type, so it'll apply to all of the groups of that type. Now, let's take a look at how to actually set up a group requirement. And so to do that, we're gonna go to admin tools and general settings, and we're gonna go to group requirement types. And here we have one, background check required. That's the one that ships out of the box. So let's go ahead and click on this one and take a closer look. Okay. So at the top, you have the name. That's pretty obvious. And then down below that, you have, the description. Just remember, your future self will thank you for putting in a good description of what this does. And then down below, we're gonna skip over a little bit and go to the check type down here. And so the check type is how we can tell whether or not someone satisfies the condition of the group requirement. And there's a few different options. So you can choose manual. And manual will just add a checkbox. You can give the checkbox a label here, but it'll add a checkbox that a person, typically a group leader maybe, would manually check or uncheck to indicate whether or not the person meets the requirement. You might use this in cases where you have a group leader who needs to do maybe a specific in person training. And, , there's really no way for us to get that information through SQL or data views, but you can give the group leader a button that says something completed an in person training, and the leader can then check that box to indicate that the person did the training and therefore meets the requirement. But more commonly, you'll probably be using a data view. And when you're using a data view, you have the option of picking actually two data views. One is the data view for people who meet the requirement. And so in this case, we have a data view. , background check is still valid. And those are the people who meet our background check, requirement. And those people would get a positive label. So they would show up as background checked, because they meet the conditions of the data view. You can also provide a warning data view, and that's people who meet the data view probably, but they're they're in a state where they're not gonna be meeting it very soon. And so for that, we have a data view that's background check is about to expire. And those are the people in a warning state, and they would get the warning label. And then if nobody meets, if a person doesn't meet either of these requirements, then then they just don't meet the requirement, they get the, negative label that's applied. And then we have SQL, which is an option. And this is a lot the data view configuration, but, in terms of it has the SQL that you'd need to find the people who meet and the SQL that you'd need to find the people who are warning. But this is much less likely to be used. Most of the time, you're gonna be using data views to get what you need from requirements. Going back up a little bit here, we have the, can expire option. And this just sets whether or not the requirement can ever expire. ? Of course, background checks can expire, so this is checked for background checks. But other requirements might not ever expire, maybe submitting a document or something that. So by unchecking this box, what you're doing is lightening the load on your system because we don't have to keep checking that. And then down below, last but not least, we have the expire in days. And so this is how often we need to check to see if the requirement has expired for a person. So I said, in this case, it's set to check every thirty days. The more frequently you check, the more strain there is on your system. So thirty days is a good balance between being effective, but also not overtaxing the system. And and that's how you'd set up a, group requirement type. And, of course, as we mentioned, you can apply group requirements down to the group level. We didn't show you what that looks , but it works exactly the same as it does in the group type, so you can know what to expect. For more information on groups and group requirements, be sure and check out our Rock Your Groups guide posted to the Rock Community website. And thanks for watching.