Rock U - Groups - Group Requirements - OLD

Transcribed Video Content

So let's look at group requirements and what they can do to help make sure that everybody in a group has certain requirements met. So if we were to look at, say the serving team for children's, we'll notice here that Cindy Decker has this warning, note next to her name and that's basically saying she doesn't meet all the requirements of this group. So how do we set up these requirements? It's done on a group by group basis. Okay. At this point, you can't set up our group requirement, for every group of a certain type. So you come under the group details and you would just add a group requirement and these requirements are pre configured and I'll show you in a bit how to create those. In this case, we're just gonna say, hey, we're gonna add a new group requirement called background check required and then that's set. Now, typically, again, you set this on a per group basis because not every serving team will have the same requirements. But in a future release, we do hope to be able to put that onto a group type also. Okay. So that's pretty simple. Let's let's look at how we actually define these group requirement types. And so that's found under admin tools, general settings, group requirements. Okay. So admin tools, general settings, group requirements. So from here, we'll see that out of the box, come with one, the group. I'm sorry. The background check required, requirement. So let's go ahead and look at this one. It's a really good template to look at to better understand that. So, again, name description. Definitely, again, in description, future self will appreciate the fact that you put a good description in there. And let's just jump down a little bit and some of these other things will make a little bit more sense when we look at some of these other configuration steps. The the big one here is this, how are we gonna check that the person meets that requirement? And our options are to do a SQL statement, to do a data view, or manual. So, manual basically is just gonna put a button that says meets this requirement. And it's up to the user to say whether they do or not. So this is good if you have a group leader who, maybe needs to do a specific in person training. And so there's really no way for us to know that based on a data view or SQL. So you can just give them a button performed in person training and then that requirement will be met. But more commonly, what you'll do is you use this data view. And so this is gonna give you a list. What you're gonna do is provide it a data view that gives it a list of people who meet that requirement. So in this case, we'll have a data view that people who meet the requirement of background check is still valid. Okay? Then optionally, you can give another data view that says, okay, here's people we should probably warn about. Okay. So this is background check is about to expire. So as we go through checking for requirements, what we're gonna do is we're gonna run these two data views, match it against people in that group. And so if they match, we'll give them the positive label of background checked. If they don't meet this first data view, they'll get the the label of no current background check. And if, they meet the, the warning data view, then they'll get the background check is expiring soon. Okay? So hopefully that that's that's pretty simple. Over here, we do have a couple other settings. One is can this requirement ever expire? Now, in background checks, of course, they can expire. We usually set, , a two year, maybe a three year date that we need to do a new background check. But some some requirements maybe would never expire. And so by unchecking this box, you can keep your system performing just a little bit better because we don't have to keep checking that. Also, you might say, well, how many days do we need to check to to see if they if if if do we need to do this again? So for this one, we said every thirty days, let's check and make sure that they don't they haven't have an expired background check. And that's a good setting. Again, the the bigger this number, the less stress your system will be under checking this requirement. So in this case, thirty days is a good balance between keeping your system healthy and not taxing the system. So that's how you create new type. And this is just showing you the same screens that we just kind of walked through and that is group requirements.