Rock U - Groups - Group Requirements

Transcribed Video Content

In this video, we're gonna look at how to set up requirements that a person must meet before they can join a group. Just remember that this applies to fundraising groups as well as traditional serving teams or small groups or things that. Let's take a look. First, we'll navigate over to admin tools and then general settings and then group requirement types. And we'll open that up. Let's take a look at the background check required, requirement type. So as we're looking at this, of course, we have the name and the description. We we can associate it with an icon. We have the category and the summary. Note that the, name will be seen internally, but also with the fundraising groups pages externally. The summary is also visible to the public. Now let's shift down to the requirement criteria. So your first option is SQL or SQL. You can create a SQL query that will return the people, that either meet the requirements or are in a warning state for the requirements. Next, and probably what's most often used, is a data view. So you can simply create a data view that selects the people that you that meet the criteria or are in a warning state for the criteria. And then the last option is manual. And that just means that somebody needs to go in and manually clear the requirement for the person, for each person in the group, who who meets it, whatever that may be. In those cases, you can provide a label for the checkbox to make it relevant to, , the group leader or whoever is clearing them. Okay. Then down below that, we have descriptive labels. Keep in mind that these can be seen externally on the fundraising groups pages. So we have requirement labels for meets and does not meet and a warning so that you can tell what state the person is in, across those three states. Alright. Moving down, we have the workflow section. So you can provide a workflow that the logged in person on your external website would be able to see and activate to help them complete a requirement. So the workflow may be a form or include a signature document or something that. And you can tell that there's a couple workflows that you can use, one for does not meet and one for the warning. You can have these auto initiate if you'd , and that means that they'll just be initiated as soon as the person is determined to not be meeting the, requirement. And then lastly, you have the link text. And that's, , if you want somebody to click to get to say a workflow or something, you can change the text of that link, to maybe make more sense for the context in which they're using it. And then at the bottom of the page, we have some additional settings. First of all, we have the can expire, setting. And that just means that the requirement, whatever they use to fill it, can expire. So this is really popular with background checks because background checks don't last forever. And then you can give it an expired duration in days. And then over here we have the due date. So your requirements can have a due date. You can make it immediate, so as soon as they join the group, it's due. You can set it to a configured date. And when you do that, it's configured on the requirement when it's added to a group type or or a group. Alternatively, you can use a group attribute. The due date will be based on a group attribute that would be a date. And you can choose if you want, an offset number of days. And then lastly, days after joining is pretty self explanatory. It's just you'll the requirement will be due x number of days, whatever you choose here, after joining the group. So let's look at a group requirement itself. And to do that, we're gonna go to admin tools, general settings, and group types. And we're gonna look for the serving team group type. And if we scroll down to group requirements, we can see that we've got one here for background check required, the one we were just looking at. So I can click the pencil here to edit it and we can take a look at, the options that we have here. So first off is the group requirement type. It'll you just pick which requirement it is that you want to apply. And then you can have that requirement apply only to a specific role. So if it should only apply to leaders and not members, you can do that. If you leave this blank, then it applies to everybody. You can also choose, an age classification to make the requirement required for. So you can do it just for adults or just for children or for everybody. Then you can say applies to data view, and so you can create a data view that returns the people that this requirement would apply to. Then below that, you can allow the leaders to override. So if the person doesn't meet this requirement, the specific requirement that we're putting in, you can allow the leaders to override that and basically make it as though the person meets the requirement. And then the last setting we have there is that members must meet this requirement before adding, which is pretty self explanatory. If you do this then anybody who doesn't meet the requirement will not be able to go into the group. Lastly, let's take a look at how this looks on the group viewer. So to do that we're gonna go over to people and group viewer. And we're gonna take a look at our serving teams and we'll look at, the AV team for instance. So on the front page here, on the group member list, you can see Alicia Marble has a yellow triangle next to her name and Jim Simmons has a red triangle next to his name. And if you're not sure what those mean, we can click over to the requirements tab where it'll list all of the requirements and there'll be different colors depending on their state. So, Ted Decker has met the requirements, so his is green. Alicia Marble is in a warning state, so hers is yellow. And then Jim Simmons does not have a background check, so his is red. We hope you found this to be helpful. For more information, check out the Rock Your Groups Guide and the other groups videos. Thanks for watching.