Group Maps

Clicking the map marker button will take you to an interactive group map showing the members of the group. Depending on the configuration of the group other features may be enabled.

If the group has a geopoint (determined through the address geocoding process or by selecting the point on the map) the location of the group will also be present on the map.

If the group has a defined geofence this fence will be shown on the map. The presence of the geofence will also enable the display of connection status labels at the top of the map. Clicking these labels will show everyone with that connection status in the database who lives within the geofence. This allows you to view possible 'prospect' group members.

Along the top of the block, you can click the labels (e.g., Decker Group or Group Members) to toggle the display of the group's location or member locations. In the example pictured below we're displaying the location of the Decker Group and we clicked the Group Members label (with the green circle) to show the locations of individual members.

Adding a Group

You can add a new group to the tree by clicking the icon and then selecting the location from the list. Adding a group using Add Top-Level will place the group at the root or top of the tree. Selecting Add Child to Selected will place the group under the currently selected group.

Group Details

The group details section displays all of the information about the group. The group type and campus (if configured) will be shown as labels in the banner at the top. A map of the group’s location will also be shown, if configured.

Editing a Group

Clicking the Edit button from the detail section will allow you to edit information about the group and provide additional configuration settings.

The key features of the edit screen are discussed below.

1 Name

Update this field to change the name of the group.

2 Active

You can inactivate the group by deselecting this checkbox. See Inactivating a Group for additional details.

3 Public

Only groups that are marked as Public can be viewed in the Group Finder.

4 Description

Providing a good description for the group lets people know what the group is all about.

5 Group Type

Changing the group type of an existing group is possible, but it does have some consequences. All group attribute data for the group will be lost if the group type is changed.

6 Parent Group

Changing this will move the group to a new parent in the hierarchy. Removing a parent group will move the group to the root or top of the tree.

7 Administrator

Select the individual who is responsible for administrating the group. This will only appear if Show Administrator is enabled for the group type, and may be labeled differently (e.g., Coordinator, Director) if an Administrator Term has been configured. Group administrators don't have the security privileges of Leaders, and they aren't members of the group. Generally, this is only used for internal purposes to identify who is responsible for the group from an organizational perspective without having to add that individual to the group as a member.

8 Security Role

This option will enable the group to operate as a security role. The members of the group will be granted access to whatever privileges the group is granted.

9 Campus

Providing an optional campus will link the group to a specific campus. This isn’t shown if you have only one campus.

10 Require Signed Document

This setting is only used if you have a legacy signature provider in place. If you're using a legacy signature provider like SignNow, you'll need to transition to the native electronic signature features in Rock soon. In a future release the Require Signed Document setting for groups will be going away entirely. For details on electronic signatures in Rock check out the Admin Hero Guide.

11 Meeting Details

This area allows you to add locations and times based on the configuration provided through the group type.

12 Group Attribute Values

Any group attributes values added by the group type will be available here for editing.

13 Member Attributes

In this area, you can configure attributes to be assigned to each member of the group. These attributes will be available for editing when adding or editing group members.

14 Group Member Workflows

This section allows you to configure workflows that will be launched when specific events occur with group members.

Inactivating a Group

If enabled in the Group Type settings, you’ll be prompted to provide additional details after inactivating a group.

1 Inactive Reason

Select a reason for inactivating the group. Depending on the Group Type settings, the Inactive Reason may be optional or required.

2 Inactive Note

Additional details can be recorded here for future reference. For instance, you might indicate why the group was made Inactive. Notes are optional, even if a reason is required.

3 Inactivate Child Groups

If there are child groups, you can choose whether to inactivate them also. You’ll be given this option any time an inactivated group has child groups.

The list of Inactive Reasons is maintained under Admin Tools > General Settings > Defined Types > Inactive Group Reasons. You can restrict which Group Types the reason can be applied to. If no Group Types are selected, the reason can be used with groups of any type.

Group Hierarchy

One of the most important concepts to understand as you create new group types is the relationship that groups have to each other. There are two basic hierarchy types to choose from:

• Structured Hierarchy: In this configuration, the levels of hierarchy are defined and limited. For example, you may want to define the hierarchy of your small group ministry to have a single leadership team, under them a level of lay leaders who act as coaches to the groups, and then the groups themselves. In a structured hierarchy you can be sure that this structure is enforced.

  

• Flexible Hierarchy: For some ministry types, you want your groups to have a more unstructured hierarchy. An example of this might be how you set up serving teams. You may want serving teams to be able to have sub-teams that might have additional sub-teams themselves. These hierarchies may be very deep in some ministry areas (like First Impressions) but shallow in others.

  

You define these hierarchies by configuring what child groups each group type can have. In the structured example, you would create a group type called Small Group Leadership, which would allow child group types of Group Coaches, which would allow child groups of Small Groups. The Small Groups would not allow any child types, ensuring that your hierarchy was fixed at the third level.

In the flexible hierarchy example, you would configure Serving Teams to have child-types of itself. This guarantees that you can have an unlimited hierarchy.

Administering Group Types

You administrate group types under Admin Tools > General Settings > Group Types. When adding or modifying a group type there are many areas of configuration, as pictured below:

Let's look at the different Group Types settings you can configure in the Group Type Detail block.

Group Member Roles

People often have special roles in groups. Some are leaders; others have unique duties. To help differentiate the members of a group, you can give each a Group Member Role. The list of possible roles is defined on the group type. For more information on the roles available, you can check out the chapter on Group Members.

Securing Group Types

By adding security to a group type, you control the base security of every group of that type. Let's say your organization adds a new type of group to help manage some classes you're starting. You may want to create a new group type for this initiative where every class is a group of this new type. By adding security to the group type, you can ensure that every group can be viewed and edited by a select handful of people.

To add security to a group type, go to Admin Tools > General Settings > Group Types. There you will see a list of group types in a table. In the far right column, you will see a button. Clicking this will allow you to set the security for the selected group type.

Securing A Group

There may be occasions where each group will need different security settings. Don't worry, this is super easy in Rock. To secure a specific group, find the group in the group viewer (People > Group Viewer). On the group details page, you'll find the same button. Clicking this button will bring up the Rock security dialog where you can adjust the security settings.

Groups have a special Manage Members security tab. Anyone with Manage Members security can add, edit and delete group members, but they can't edit or delete the group itself. If no permissions are listed under Manage Members, it doesn't mean that members can't be managed. Anyone with Edit access has Manage Members access by default. Also, group Leaders can manage members even if no Manage Members permissions are set or if they don't have Edit permission.

Note the inherited permissions at the bottom of this screen. Inherited security is a very powerful concept with groups. By default, a group will inherit the security of its parent groups and group type. This limits the amount of security configuration each group requires. These inherited rights are only a starting point. You can either build on top of these permissions or override them. The choice, and power, is up to you.

At first you may be tempted to go overboard with your group's security settings. In general, it's best to keep them simple. For instance, in the case of home-based Bible studies you may be tempted to secure each group differently to only allow the leader to edit them. While in certain cases you may need to do this, you could also secure all groups with a generic Small Group Leader role. You could then limit which groups a leader was able to navigate to through the configuration of your leader toolbox blocks.

Group Member Roles

Group member roles play an important part in how groups are secured. Each role can be configured to provide View and / or Edit rights. This is configured under Admin Tools > General Settings > Group Types.

Inherited Permissions

When determining the security of a group it’s important to consider not only the specific permissions of the group but also the inherited permission rules. The inheritance rule for groups is:

Current Group > Group Type Security > Parent Group Security > (continue up the hierarchy until it reaches the root group) > Group EntityType Security > Global Default.

The primary inheritance rules come from the group’s hierarchy, but the system has a built in ‘choke point’ check on the security of the group type first. Why is this? Adding a quick check of the group type's security allows specific types of groups to have unique security considerations. Take for example a group type for ‘Addiction Classes’. Adding a check for the group type's security allows a way for limiting visibility to these groups without having to worry about inconsistencies in the security of the group hierarchy. In most cases the group type will not have specific security so this check will not matter, but it’s there if you need it.

If when checking the group’s security, the person is blocked access there’s still one last check to be done. Roles defined on the group type can be configured to provide access to the group. For instance, you can configure the leader of a group to have view/edit rights to that group. Likewise, the member of a group could be set up to have view access. This allows a very simple and flexible way of providing access to external individuals.

Multiple Group Viewers

Rock comes preconfigured with a general group viewer People > Group Viewer, but you can add more. Say, for instance, your church has a strong small group ministry. You may want to create a new Group Viewer page just for this ministry. You can do this by adding a new page under People (or any other page you like) and adding the group viewer blocks to the page as described below.

The following blocks are used to make a group viewer page. We recommend that you use the LeftSidebar Panel page layout.

1 Group Tree View

Add a group tree view block to the sidebar zone to help you navigate your group hierarchy.

2 Group Detail

Add the group details block to the top of the main zone.

3 Group Member List

Next, add the group member list block under the group details.

When you set up the Group Tree Block you can set the root group to start with, and limit which types of groups it will display. This allows you to make a very specific small groups viewer with just a couple of clicks.

Group Folders

As you start to think about your group hierarchies, make sure that you plan for growth. This might mean that you create special groups in your hierarchy to help categorize your groups. You can think of this like using folders on your computer to help manage all of your files. You could throw all of your files in one folder, but you’d never find anything. Adding folders helps you arrange and sort your groups. While folders add little value to your computer’s file system, these category groups can actually be beneficial beyond just organizing. For instance, if you add these category groups to your serving teams, the categories can act as leadership teams for their sub-groups. Take a look at this example of the first impressions serving teams at a large multi-campus church:

Notice how each campus and ministry area has a leadership group. These groups not only help arrange the serving teams, but they can also have members of their own that represent the leadership team for each area.

Types of Group Schedules

There are three types of group schedules that can be configured for a group. To help simplify the editing of a group we allow you to configure which of these options are available to groups of each particular type. For instance, you'll probably want to configure your Small Groups to only be configured to allow the Weekly schedule. You can select which of these options are available for a specific group type under Admin Tools > General Settings > Group Types.

Schedule Exclusions

Picture this: you've just finished entering all of your small groups into the system with their correct schedules and your supervisor just announced that, "groups are taking a two-week break." Not a problem! Adding a Schedule Exclusion to the Small Group group type will add the exclusion(s) to the schedule of all groups of this type. This is done under Admin Tools > General Settings > Group Types. This not only keeps the schedule accurate, but it also keeps attendance reminders from being sent while groups are not meeting.

Configuring a Group for Attendance

Before a group can take attendance, its group type must first be configured to enable attendance tracking under Admin Tools > General Settings > Group Types. From here you should select the group type you'd like to configure check-in for. Under the Attendance / Check-in tab enable the setting Takes Attendance.

While this one setting is all you need to enable the attendance features, there are a couple of other settings that help improve the attendance tools:

• Group Schedule Options: While a group schedule is not required to take attendance, having a schedule will simplify the attendance entry because it will guide the user to enter attendance on those dates when the group meets.


• Schedule Exclusions: While each group can set its own schedule (including exclusion dates) you may want to set exclusion dates for every group of this type. This is especially helpful when using the simple schedule option where you only specify the day of the week and the start time for a group. Adding these group type schedule exclusions helps to keep email attendance reminders from being sent.


• Send Attendance Reminder: This checkbox will enable the sending of an attendance reminder email or text message to the group leader the day the group is scheduled to meet.

Entering Attendance Information

Internal Attendance Features

There are several ways to collect group attendance. The first is to use the internal attendance features built into the Group Viewer under People > Group Viewer. You'll notice an attendance button on the group details block for groups that are configured to take attendance.

Selecting this option will bring up the group attendance grid. This grid lists the previously entered attendance for the group and allows you to enter new attendance records from the add button in the grid's header or footer.

Selecting the button will take you to the attendance entry screen pictured below. From this screen you can check off all those who attended the group or note that the group did not meet on its scheduled date and time. You can also print an attendance sheet, which allows attendance to be collected via a register.

1 Attendance For

The date for which attendance is being recorded.

2 Schedule

If a Named schedule is being used for this group, it will be shown here.

3 We Did Not Meet

Select this checkbox if there was no attendance because the group did not meet. This distinction is helpful for record-keeping, but also impacts areas like Streaks.

4 Attendance Location

If enabled in the block's settings, here you can select the type of attendance, like physical (in-person) or virtual (online). If you need other options, you can manage these values using the Attendance Types Defined Type. Edit the Attendance Entry block's settings to restrict the available options to only certain Attendance Types, or to change the "Attendance Location" header to say something else.

5 Attendance Count

After attendance has been entered, the count of attendees is displayed.

6 Search

For larger groups it can be helpful to search for the people you're looking for.

7 Notes

If enabled in the block settings, notes can be added here. Notes will appear in the Attendance Summary Notification email if you are using that feature. The label “Notes” can be customized in the block settings.

8Attendance Roster

Click the Roster button to generate a printer-friendly version of the attendance page. This will be a Word document that you can then update, print or save.

9 Members

Attendance is tracked by clicking the cards of those who attended. You can see here that nine people were in attendance on that day.

Rapid Attendance Entry

The Rapid Attendance Entry method of recording attendance may come in handy for your groups. To learn more, see the Rapid Attendance Entry chapter of the Checking-out Check-in manual.

Attendance Reminders

You can also configure Rock to send a communication to the group leader on the day that their group meets to remind them to take attendance. This communication will include a link to take them straight to the attendance detail screen. Since each group leader gets an individual communication, we have enabled this link to not require a login to help simplify the process (the user however must have edit rights to the group to enter attendance).

There are two other key configuration points for attendance reminders.

The first is the system communication that is used as the template for the reminder. This template can be edited by navigating to Admin Tools > Communications > System Communications > Group Attendance Reminder. See our Communicating With Rock guide for more information. If the template is configured for both email and SMS, and if your system is set up to send emails and text messages, then the reminder can use either medium. Group leaders will receive either an email or a text, depending on how the job is set up.

The other configuration point is the job that is run to send the communications on a daily basis. This job must be created for every group type that requires reminders. For more information on this job see the Service Jobs Relating To Groups chapter below.

Group Attendance Digest

The Group Attendance Digest is an email containing a summary of attendance information for one or more groups. See the Service Jobs Relating to Groups chapter for information on setting up the Send Group Attendance Digest job.

The Group Attendance Digest may not be the right fit for all of your groups. It’s only intended for a specific type of groups structure that we’ll describe below.

1 Parent Group

This is the Parent Group for all of the other groups below it. This group will be added to the Send Group Attendance Digest job configuration, which we’ll talk about in the Service Jobs chapter below.

2 Region or Area

Individuals in these groups who have a group role that’s configured as Is Leader will receive a digest email for the associated child groups. If these groups have multiple Leaders, then each will receive their own email individually.

3 Attendance Group

These are the groups where attendance is being recorded. The attendance in these groups will be emailed to the Leaders of their respective parent groups. For instance, the attendance in ‘Group #3’ and ‘Group #4’ will be emailed to the Leaders in ‘Region #2’.

The Leader of the attendance group will be contacted when the ‘Email Leader’ link is clicked from the Attendance Digest email as shown in the prior screenshot above.

The chart above has three “Regions” with two “Groups” below each region. But you’re not limited to those numbers. You can have only one region with five child groups below it, or ten regions with a single child group each. The only requirement is that you need all three hierarchical levels, with a single parent group at the very top.

Configuring Group Sync

Configuring your groups to sync takes only a few one-time steps. After you've got it all set up, you can sit back and watch Rock do the work for you.

To get started, you'll want to make sure that Group Sync is enabled for the groups you're working with. This is set at the Group Type level, as described in the Group Types chapter above.

Next, you'll need to create a Data View that returns the people who should be synced as group members. The list of people in this data view will be compared against the list of the group's current members. If there are any differences between those lists, the group's membership is updated so that it matches the data view.

With Group Sync enabled and your data view in place, go to the group you'd like to sync and edit its details. If you have Administrate access to the group, you'll see a panel labeled Group Sync Settings. At first, when you're just getting started, there won't be anything listed in this panel. Click the to add your sync as described below.

1 Sync Data View

This is the data view you created to use as the source of your sync. The people found by the data view are compared against the current members of the group, and changes to group membership are made if there are differences.

2 Group Role to Assign

Select the role you want to assign to group members added by the selected data view. Each sync works with one role at a time, so you'll need a second sync like this one if you want to automatically manage both 'Leaders' and 'Members'.

3 Sync Interval

This setting controls how frequently this group should be synced. Having a lot of group syncs running constantly throughout the day might create performance issues in your system, even if no changes are made. So, try to keep the frequency as low as possible according to your needs. When setting the sync interval here, you'll want to keep the Group Sync job in mind, which we'll discuss a little later below.

4 Welcome Communication

If you'd like to notify new group members of their new status in life you can configure a system communication to let them know. We've provided a good template called Sync Welcome To Group that covers most cases. If the member already had a login, it even reminds them what their username is (not their password though, we store that in a super-secret way that not even we can decrypt). If you've enabled Create Login During Sync below, and if the person doesn't already have a login, the communication will include their new username and password (we know the password in this case because we just created it).

5 Exit Communication

You can also choose to send a notification letting people know that they're no longer part of the group. This can be helpful in some cases but isn't required. We've provided a template called Sync Exit From Group for this purpose.

6 Create Login During Sync

When syncing with security roles, you may also want the job to create logins for new group members. This will give those members access to use their new permissions.

Group Sync Job

As noted in the prior section above, the Sync Interval setting for the group controls how frequently the group's members are checked against the data view. However, this is only part of the equation.

There's a system job called Group Sync that actually does the syncing we've been describing in this chapter. By default, this job runs once every 20 minutes. Most of your groups won't need to be synced that frequently, so you generally don't need to worry about when the job runs. The only time it might cause an issue is if you've configured a group to sync at a more frequent interval than the job. That should be an extreme case, but if you need to change the frequency of the job you can do so under Admin Tools > System Settings > Jobs Administration.

Managing Synced Group Members

Once a Group Role is managed by a sync, members cannot be added to that role manually. You can still manually add people to the group, just not with that role.

That's because if you're manually adding a person to a synced group, then it means the person doesn't meet the criteria of your data view. The sync would remove that person from the group the next time it runs, undoing your manual work. That's why each sync is specific to a role, so you can have some roles that are synced and others that are managed manually.

For the same reason, you can't manually remove synced group members. If you did, they would just be put back in the group by the sync the next time it runs. If you need to remove a synced group member, consider updating the data view to account for that person's scenario.

If you want to stop syncing a group, you can remove the sync from that group’s settings, and it will keep the members. At that point, members of the group would need to be managed manually.

You’ll also notice a icon on the group's member list, to notify you that the group and that member are being automatically synced. The icon is also displayed in the upper-right corner of the list. If you hover your cursor over the icon, Rock will display the roles being used to sync the members of the group.

How To Follow

Following is super simple. First navigate to the group you'd like to follow. Then, press the follow star in the upper right of the group detail block.

Also note that when you have an event registration that places registrants into a group, you can configure the registration to notify all individuals who are following that group.

Group Member Roles

People often have special roles in groups. Some are leaders; others have unique duties. To help differentiate the members of a group, you can give each a Group Member Role. The list of possible roles is defined on the group type. Each role has the following configuration options:

• Is Leader: Determines if the individuals in this role are considered leaders within the group. This option enables additional functionality within Rock.


• Receive Requirements Notifications: Individuals in this role will receive notifications of group members who do not meet the group's requirements. This only applies if you've configured the Send Group Requirements Notification job.


• Can View: This gives the members of this role the ability to view the group information in various group toolbox blocks.


• Can Edit: Allows members to edit group information in various group toolbox blocks.


• Can Manage Members: Individuals with this role will be able to manage group members (e.g., change their role, status, etc.) regardless of the security settings on the group itself.


• Minimum Required: Rock allows you to have rules on how many individuals can have certain roles. This setting configures the minimum number of individuals who must have this role. This will keep you from deleting a group member if the deletion will drop the number of individuals with this role below the minimum.


• Maximum Allowed: This setting is like the minimum but limits the number of people who are allowed this role. For instance, you might configure a group type to only allow one person to be the leader. You can also use this option to limit the number of adults in a family. A family is a group type.


• Default: When someone is added to a group, this will be the default role they'll be assigned to. Note: Some blocks will have a block setting that overrides this default. This setting will handle cases when a block does not provide an overriding setting.

Group Member Status

The status of the group member tells you the person's standing within the group. The available statuses are:

• Active: The individual is currently participating in the group.


• Inactive: The individual is not currently participating in the group. Usually, this status denotes that the person did participate at one point but isn't doing so anymore. How you choose to use this is up to you.


• Pending: The individual has not yet fully joined the group.

Group Member Attributes

Group members can also have attributes. This allows you to track custom data points for each person as it relates to their membership in the group. Usually, these Group Member Attributes are defined on the Group Type under Admin Tools > General Settings > Group Types. When they're configured here, the attributes will apply to every group member in groups of this type.

You can also add Group Member Attributes to a specific group under People > Group Viewer > Group if you have Administrate access to the group. This also requires that there is at least one Group Member Attribute defined at the group type level, or that the group type has Allow Specific Group Member Attributes enabled.

Editing a Group Member

Selecting a group member from a group member list will take you to the group member detail screen shown below. From here you can change the role and status of the group member. You will also be able to modify any of the Group Member Attributes defined for the group.

1 Person

The name of the person is shown here for reference. You can't change the group member from here. Instead, you would add a new group member or remove an existing member.

2 Notified

This indicates whether the group leader has been notified about the person's membership in the group. This only has an effect if you're running the Group Leader Notification job.

3 Role

We talked about group member roles above. This is where you set or change the role that this group member has in the group.

4 Note

Here you can add a note about the group member or their membership in the group.

5 Member Status

Group members can either be Active in the group, Inactive or Pending.

6 Communication Preference

This sets the person's communication preference as it relates to this group's communications. This does not impact the Communication Preference that would be set on the person's profile.

7 Quick Communication

Click this icon to send a quick SMS or Email communication to the group member.

8 Move Group Member

Click this icon to transfer the person from this group to a different group. See the next section below, and the Alternate Placements chapter, for more details.

9 Group Member Notes

Here you can track notes about the group member. These can optionally stay with the group member if they are moved to a different group.

As pictured above, you'll see a note field for the group member. This is useful for keeping basic notes. Rock uses this field to provide specific information about the group member when processing things like workflows and alternate placements.

If a group member has a note attached, a small note icon will display on the group member list to help identify this fact.

As noted above, you can send a quick communication to the group member from the group member detail screen by clicking the icon. You can send either an email or an SMS text message. This is best used when you just want to send a quick note to a single group member.

Moving Group Members

From the Group Member Detail screen discussed above, it's also possible to move a group member from one group to another by clicking the icon. When you do, you'll be given the option to transfer any group member notes to the new group. If you're working with Fundraising Groups you'll also see an option to move donations to the new fundraising opportunity.

If the group member's current group and the destination group share group member attributes with the same key, then those attributes will be retained. Otherwise, when the group member is moved, the member's attribute information will be lost.

Group Member Workflows

By now you realize that groups are the backbone of Rock. So, it makes sense that we'd invest in making them as powerful as possible. Group Member Workflows are one of these investments. So, what do they do?

Group Member Workflows are an easy way to trigger workflows to launch when the state of a group member changes for a specific group. These events include:

• Being added to a group
• Being removed from a group
• Member status changes (e.g., status changed from Pending to Active)
• Member role changes (e.g., role changed from Attendee to Leader)
• Member attendance
• Member alternate placements (discussed in detail in the next chapter)

The workflows you define for these triggers can be configured for all groups of a specific type under:
Admin Tools > General Settings > Group Types or for a specific group under People > Group Viewer > Group. Below is the screen you'll see in either case. Note that workflows for a specific group can only be added if Allow Specific Group Member Workflows is enabled for the Group Type.

1 Name

This is the name you want to use to describe the trigger.

2 Active

Indicates whether this trigger is currently active.

3 Start Workflow

The workflow type you'd like to start when the trigger conditions are met.

4 When

This determines when the trigger should be considered.

5 With Status Of

This allows you to filter when the trigger is applied for members with a specific status.

6 With Role Of

This allows you to filter when the trigger is applied for members with a specific role.

7 From Status/Role Of

Determines what the original status/role was to use as a trigger filter.

8 To Status/Role Of

Determines what the new status/role must be for the trigger to fire.

9 First Time

Determines if this trigger should only be activated the first time a person attends this group, or every time.

See our Blasting Off With Workflows guide for more information on working with workflows.

Tips For Creating Triggered Workflows

When workflows are started from the group member triggers, they will pass in a few attributes for your convenience (as long as the attributes are defined). These include:

• Person: The person that the group member represents.
• Group: The group that the person is a member of.
• AttendanceDateTime: Only applies to the Member Attended Group trigger type and is the date/time that person attended the group.

Whenever possible, the workflow will also pass in the Group Member model as the entity of the workflow. You can access the group member properties and attributes by using the Attribute Set From Entity action combined with Lava like the following:

Tips For Creating Triggered Workflows

When workflows are started from the group member triggers, they will pass in a few attributes for your convenience. These include:

• Person: The person that the group member represents.
• Group: The group that the person is a member of.
• Note: The note that was entered by the group leader.
• Group Member Status: The status that the group member was when the workflow was launched.
• Group Member Role: The role name of the group member when the workflow was launched.
• Any attributes that match those of the group member attributes configured for the group.

Enable Group History

To enable Group History for all groups of a certain group type, begin by locating the group type in:
Admin Tools > General Settings > Group Types.
In the General section of the Group Type Details screen, check the Enable Group History checkbox. You can customize the group type's display options in the Display Options section by assigning it a color and icon. These options come into play in a number of the Group History views, but we'll get into that later. For now, click Save and Rock will enable the history and options for that group.

View Group History

Now that you have Group History enabled, you can jump to that 40,000ft view. Locate the group in the Group Viewer and click the button.

This brings up the group's timeline view, shown earlier, including both member and group history information. The Group History screen shows the history of the group by day for the lifetime of that group. Each event on the timeline has an icon that corresponds to a type of action.

• - Member added
• - Member removed
• - Group edited
• - Other/general group action

If there is more information than space available for an event on the timeline, you can view the entire contents by hovering your mouse over the text. For multiple occurrences on the same day, Rock will display a link to expand the area to display all of the actions for that day.

To hide member history and view only actions made on the group level, click the button.

You can also zoom in from that 40,000ft view and get a closer look at the history of the members of a group. Click Member History to display a group's members and the history/dates of their involvement in the group. Click on a specific person to view a timeline of their involvement with the group.

View Group History in a Person's Profile Page

Individual group history is also available on the Person Profile, under the Groups tab.

Hover your mouse over any of the events on the person's timeline to display the details of that event. Note the timeline colors correspond to the color assigned to the group back when Group History was enabled. If the person is a group leader, the color will be slightly darker. You can also click on a specific event to drill down into the group. As with all of the tabs on the Person Profile, the information is filterable. Click the button to display the filter options.

My Account - Groups

Along the right of the My Account page is a listing of groups to which the person belongs. The individual can also see their role within the group. Through block settings you can configure which group types to show or hide. Using Lava, you can adjust the look of this block to your heart's content.

Clicking on any group in which the person is a leader will open the group leader's toolbox.

Group Toolbox

This is the money block. With this block, you have access to every detail of a group that's accessible in a Lava template. It also has some special Postback Commands that allow you to enable editing of the group details and its members. If enabled in the block settings, you can even allow individuals to set their communication preference for the group. The sky is really the limit when it comes to customizing the look of this block.

Group Attendance List and Detail

These two blocks allow you to track the attendance of a group. By default, these options will only show for groups of a type with attendance enabled.

Group Registration

Registering for a group is a simple process using Rock's Group Registration block. Out-of-the-box this block will ask for basic contact information for the individual and their spouse. By adjusting the block settings, you can customize this block in several different ways. Below we'll walk through some of the common settings but be sure to review all of this block's settings to ensure it's meeting your organization's needs.

• Mode: There are three entry modes for the registration form.
  • Simple: This mode only asks for the individual's first name, last name and email address.
  • Full: This mode additionally asks for more contact information including home phone, cell phone and address.
  • Full With Spouse: This mode is identical to the normal Full mode but adds the spouse's first name, last name, cell phone and email.


• Group Member Status: This setting determines the group member status that will be used when they are added to the group. Options include Pending, Active or Inactive.


• Connection Status: The registration form will attempt to find a matching record in the database using the first name, last name and email. If a record cannot be found, a new record will be created in the database. When that occurs, this will be the connection status that is used for these new records.


• Record Status: This represents the record status that will be used for new records. It's best to leave this as Pending so individuals on your data integrity team can manually review them for possible duplicates and merge the records if needed.


• Workflow: This option allows you to launch a workflow after the registration. The group member will be attached to the workflow as the Entity.


• Lava Template: This is a Lava template that will be applied to the top of the registration block. This allows you to customize the experience for the individual.


• Result Lava Template: This Lava template is used to craft a response message after the registration is completed.


• Result Page: You can optionally send the individual to a new page after the registration is processed.

Scheduling Tools

Any organization needs a way to manage which workers are assigned to what positions. Many approaches are used to schedule workers, from a paper on a clipboard, through Excel spreadsheets, to complex and costly specialized scheduling software. Sometimes all of these approaches and more are in use within the same organization. In Rock, all of these methods can be put to rest by using the Group Scheduling feature as your one-stop-shop for coordinating people for any event.

Overview

The general point of using this tool is to quickly drag and drop people into a room for a specific time. The tools are very customizable for you to configure this so it will work for your organization's flow. A typical example here will be scheduling volunteers for your nursery team for the weekend. You'll pick the group, week, time, and location—the people will then be filtered based on those selections. Now you will drag and drop people's names into the desired areas or use the auto tool. Make sense? If not, don't worry, we'll break each step down into detail.

Scheduling Toolbox

Let’s start with the power each person has. On the Schedule Toolbox on their My Account page they can:

• See what upcoming opportunities they are assigned to.
• Choose the frequency of serving. This could be once a month, every week, 1st and 3rd, etc.
• Choose which room/area of volunteering they prefer, plus preferred times.
• Set blackout dates—vacation, work, etc.

The Schedule Toolbox relieves your staff of a significant load because individuals can do that work for themselves. When each person logs in to the external website, within their My Account, they have access to their Schedule Toolbox. Don’t worry; we'll still have some work for you to do.

1 Copy Calendar Link

Clicking this button will copy a URL to your clipboard that can then be used to download an iCalendar file which can be used by programs like Outlook.

2 Accept/Decline

Simply click Accept or Decline to record the response. Accepted assignments will be marked as Confirmed, while Declined assignments will be removed from the list.

3 Unavailable

This indicates an assignment that occurs during a period of unavailability, which the volunteer can configure for themselves (see below screenshot). Clicking the icon will let the person remove such assignments from the list.

4 Confirmed

Confirmed assignments can be cancelled if needed by clicking the icon and selecting Cancel Confirmation. This will give them the opportunity to either Accept or Decline the assignment.

5 Actions

Each of these buttons will direct the volunteer to a new screen where they can manage different aspects of their schedule and schedule preferences. Each of these actions are described in the following screenshots below. The list of available Actions can be modified by editing the block's settings.

Next, we'll look at how a person can set dates on which they are unavailable to serve. The below screen can be accessed by clicking on the Schedule Unavailability button from the main Schedule Toolbox page.

1 Date Range

This is where volunteers can select which dates they are unavailable to serve. This will prevent the person from being scheduled to serve on those dates.

2 Description

The person can optionally provide a description, indicating why they are unavailable for the selected dates.

3 Group

A volunteer can be unavailable for scheduling in a single group, or across all groups.

4 Individual

If a person is unavailable, it's often the case that others in their family are unavailable as well. The volunteer has the option to also indicate that family members are not available to serve on the selected dates.

The screen pictured below can be accessed by clicking on the Update Schedule Preferences button from the main Schedule Toolbox page. Among other things, this is where volunteers can go to set their time and location preferences for serving.

1 Send Reminders

Each volunteer can select how long before a scheduled serving time they want to receive a reminder that they're scheduled to serve. They can also choose to not be sent a reminder at all.

2 Current Schedule

This is where volunteers can set the frequency of their serving. Options include:

• No Schedule
• Every Week
• Every Other Week
• 1st and 3rd Week
• 2nd and 4th Week

3 Assignment Preferences

This is where the volunteer can set their preferences for when they would like to serve (i.e., what service time) and where. As pictured above, a person can choose not to select a location, indicating they don't have a location preference for the selected schedule. Only schedules marked as Show Publicly are available for selection.

The person's assignment preferences can also be changed when viewing the group member details page, as pictured below.

The last stop on our tour of the Schedule Toolbox is the Sign-Up screen. Volunteers can come here to sign up for additional serving opportunities, which will then be added to their schedule. This screen is accessed by clicking the Sign-Up for Additional Times button from the main Schedule Toolbox page. Note that the text near the top of the page (in blue) can be modified with a custom template by editing the block's settings.

1 Select Schedule

All a volunteer needs to do is check the box next to the time they want to serve for the given date. It's just that easy! Only schedules marked as Show Publicly are available for selection. What displays for the schedule (e.g., 10:30 AM) can be changed in the block settings.

2 Select Location

Optionally, the person can provide a location preference for the selected time.

Auto Schedule Vs. Manual Schedule

Auto scheduling works based on the preferences set by volunteers. In both an individual's My Account page on the external site, and on the groups page on an internal site person profile, there is a scheduling toolbox. These are the same, connected toolboxes so whatever a person sets on their external account will appear on the internal site for Rock administrators to view. Sometimes a verbal conversation will happen about someone’s preferences so a staff member can manually set that on their profile for them – whatever works for your organization, you can do.

So how does the auto scheduling feature work? Well, it involves some complex logic, and thankfully we already figured that all out for you, so sit back, relax and we’ll take a brief look at an example.

We all know those multi-talented people who can greet everyone at the door, run the lighting console and keep the attention of 10 three-year-olds for an hour, so naturally they set their preferences to every service, in every group which is a huge blessing. Only problem is how do you avoid double booking this individual?

This is how Rock solves that conflict: If you’re using the same schedules to represent the same time frames, (which we know they are from the foundation of your schedule configuration), then the auto scheduler won’t schedule the same person twice. Auto scheduling scans the person’s preferences and sees that they are not assigned anywhere so the first time a staff member clicks on auto schedule it will always pull them first.

Manual scheduling is in the name. It’s physically placing people into their serving locations. If we are being realistic here, we know there are going to be those few people who never get around to setting their preferences, so in those cases you’ll have to manually place them. We know you know each and every one of your volunteers’ time and location preferences, so this isn’t a big deal anyway.

Note that when people have a blackout date, they cannot be auto or manually scheduled, but they will appear in the list with an icon by their name. If someone is scheduled in one group and you're doing scheduling for a different group the person will also appear in the list with an icon by their name, indicating potential conflicts with the group you're scheduling.

If you have multiple sites that are close enough to each other that some people volunteer at more than one location, you will run into a scheduling conflict that doesn’t appear as one if the locations have different schedules. For example, one site might have a 4:30pm and 6:00pm schedule while the other only has a 5:00pm schedule. If someone was already scheduled for the 5:00pm time, Rock would not see that they are elsewhere on the people list for the other site since the schedules are different.

Confirmation Communication

You will typically send a mass communication once you have your teams set up for them to accept or decline. Click on the Send Now button near the top of the block to send a confirmation. Rock will automatically send either SMS or email confirmations based on the person's preferences and available information.

Alternatively, you can send an individual a communication to accept or decline by clicking on the three dots near their name. This opens a drop-down list of options where you can choose the Resend Confirmation button to send the email or SMS message to confirm or decline again.

Scheduling with Multiple Groups

Most of the time you'll just want to look at scheduling for a single group before moving on to the next one. However, you can view multiple groups at once in the Scheduler by selecting them from the picker near the top of the block.

In the example below we've selected the Greeters, Ushers and Children's groups. As you can see, this changes the look of the page pretty significantly. Each column now represents a group, and all of the schedules and locations for that group are listed beneath it.

Even though you can see multiple groups, you can only do manual scheduling for one group at a time. That's primarily because your list of group members will change depending on which group you're actively working with. To select a different group, click the checkbox near the top of the desired group's column. This will shift the selected group to the left and will update the list of group members accordingly.

Send Group Schedule Notifications Job

Rock will automatically send out confirmation and schedule communications based on the values you set on the Group Type Detail page. By default, these communications will be sent daily at 4pm to people who have not already received them. If you want to change the sending time, you can edit that time in the "Send Group Schedule Notifications" job, which can be viewed under Admin Tools > System Settings > Jobs Administration.

We have "Scheduling Confirmation Email" and "Group Attendance Reminder" system communications already set up for you, which are of course customizable to fit your organization’s lingo. Just like all system communications, you can view and modify them under Admin Tools > Communications > System Communications.

See our Communicating With Rock guide for more information on working with system communications.

Custom Group Scheduling Communications

While schedule and confirmation communications are certainly useful, sometimes you’ll want to send other types of communications to your teams. On top of that, maybe you just want to contact volunteers who have Accepted the invite, or only those that are serving on Sunday. The Group Schedule Communication block lets you do all that, and more, quickly and easily. You can navigate to it directly from People > Group Scheduling > Group Schedule Communication or you can access it from the Group Schedule Status Board.

1 Groups

Members of the group or groups selected here will form the initial list of individuals that will receive the communication. If you don’t want to send the communication to everyone in this list, you can use the other settings on this page to narrow it down.

2 Include Child Groups

If you have a lot of groups, you don’t always have to select each one individually. Enabling this option will include members of any child groups a selected parent group has. You can select multiple parent groups if needed.

3 Invite Status

You can choose to send the communication only to individuals with a certain Invite Status. If you want everyone to receive the communication, select all statuses.

4 Locations

You can limit the communication to people serving in certain locations. The list of locations you see here is automatically filtered according to the group selections, so it may change as you add or remove groups from the communication.

5 Schedules

Like the Locations field, you can select certain schedules to further refine the list of communication recipients. For instance, you may only want to communicate with volunteers for the Sunday morning services.

6 Week

The list of volunteers will probably change from week to week. Select a week here to send the communication to those scheduled during that week.

7 Create Communication

After you’ve made your selections above, clicking this button will take you straight to the Communication Wizard with the list of recipients conveniently pre-loaded for you. At that point you would proceed with creating a new communication as normal.

Group List

As its name suggests, the Group List block lists all groups that match a specific filter. The power of this block lies within its block settings. They allow you to:

• Include Groups Of Type: Specify which group types to include in the list.


• Exclude Groups Of Type: Specify which group types not to show in the list.


• Detail Page: The page you would like to navigate to when someone selects a group from the list.


• Limit to Security Groups: Remember that security groups are a bit special. While there is a group type for security groups, any specific group can be configured to act as a security group. This setting shows groups that meet any of these criteria.


• Display Filter: Determines if the filter panel should be displayed above the list.


• Display XYZ Column: This block also has several block settings to hide or display columns for displaying group type, group description, active status, group member count and system status.

Below is an image of a sample group list.

Group Tree View

The Group Tree View block is very similar in configuration to the Group List block except that it displays the groups in a hierarchical tree view. Below is a sample of what this block would look like.

Group Details / Group Member List / Group Member Details

While these are three different blocks, they are usually used together to fully display the contents of a group with the ability to edit.

Group Type Map

The Group Type Map block maps the location of every group of a specified type. This is different from the Group Map, which shows members of a single group. While not included on a page out of the box, the Group Type Map is a very powerful block for mapping all of your small groups. Small organizations could even use it to map all the families in the database (remember families are groups too). Below is a sample of this block in action.

Group Member Add From URL

Say what? OK, this is easy... this block when passed a PersonGuid and GroupId through the query string will add the person to the group and display a Lava template of your design. This is very useful in crafting various group registration scenarios. To get the juices flowing think about all the things you could do with this using the Dynamic Data and Group Finder blocks. There you go!

Group Member Remove From URL

This block is just like the Group Member Add From URL block - but the opposite. It takes a PersonGuid and GroupId through the query string and will remove the person from the group and display a Lava template of your design. This allows you even more flexibility in creating group registration situations. Alright!

Group Simple Register

This block is another block that's handy for registration scenarios. It provides a simple form that accepts a first name, last name, and email address, registers the person to a group, and then forwards them on to a confirmation page. This block is most useful when it's used on an external facing site as a simple first point of contact but is flexible enough for many other scenarios!

Group Simple Register Confirm

This block is designed to pair with the Group Simple Register block as a confirmation page. When a user is redirected to this page it provides either a success or a failure message. It's that simple!

Group Registration

This block is the big brother of the Simple Register block. This block takes a GroupId as a query parameter for context and allows you to do a few neat things like fire off a workflow when a user registers and use Lava options to format the registration form. It also has a full mode that takes down address details and phone details and a full with spouse -- which does exactly what you might expect. Use this mighty block when you want to get more than your standard information about a person or when you want to use a specific workflow process for your registrants.

Group Map

The Group Map block maps the members of a specific group that is passed through the query string (aka passed in through the address of the page http://server.com/page?GroupId=12). While this block isn't too powerful on its own, it can be very helpful when used in conjunction with other blocks like the Dynamic Data block. Below is a sample of what this block looks like with a sample group.

You'll notice two sets of color-coded labels near the top of this block. Clicking these will toggle the display of groups and families on the map. Below is a description of how and when these label toggles will appear.

Group / Group Member Labels (top left)

• If the selected group has a valid geopoint, or geofence location, that group's name will be displayed as a label in the upper left which can be used to toggle the display of the group. The group will be displayed on the map either as a marker or a polygon depending on whether the selected group had a geopoint or geofence. The color of the marker or polygon is determined by the first color specified in the Colors attribute of the selected mapstyle defined value. Note: this option will not appear if the selected group does not have a geopoint or geofence defined.


• A Groups label will be displayed if the selected group has any child groups with a valid geopoint or geofence location. The child groups may also be either a marker or a polygon. The color of markers is determined by the second color specified in the Colors attribute of the selected mapstyle defined value. The color of polygons is determined by the Polygon Colors block setting.


• A Group Members label will be displayed if the selected group has any members with a valid geopoint location. Clicking the label will toggle the display on the map of those members. Note, if the selected group is displayed as a polygon, these members may or may not be within the boundaries of the polygon. The color of the markers is determined by the third color specified in the Colors attribute of the selected mapstyle defined value.

Connection Status Labels (top right)

• If the selected group has a geofence location and is displayed as a polygon on the map, then the block will also display a list of Connection status labels to toggle the display of families whose locations fall within the boundaries of that polygon.


• The connection statuses that will be included as toggle options are determined by the Connection Status Defined Values. Only those defined values that have a value specified in the Color attribute will be displayed. The color value is also used to determine the color of the markers.


• Only families with at least one active record will be included.


• If family members have different connection statuses, they will be ordered by the connection status defined value order, and the first connection status found will be used for the family. For example, if a family has a member and a visitor, the family will be displayed when the Member label is selected.

Send Attendance Reminders for Group Type

This job (formerly Send Attendance Reminders) sends reminders to group leaders to enter attendance. All individuals in the group with a role that has the 'Is Leader' setting will receive this reminder. Keep in mind that this job will only send reminders to groups of the configured type if the group type's Send Attendance Reminder option is disabled (unchecked).

A couple of key configuration options for this job are:

• Group Type: The group type that the reminders are for.


• System Communication: The system communication that you would like to use for sending the reminder. Rock ships with a Group Attendance Reminder system communication for this purpose.


• Send Reminders: By default, a reminder will always be sent the day the group meets. By adding values here, you can configure additional reminders if the attendance has not been entered. For instance, entering 2,4 would send reminders two and four days after the group has met if no attendance has been entered.


• Send Using: Choose whether the reminder should be sent via SMS text message, email or either according to the group leader's preference. Group leaders can set their preference in the Group Leader Toolbox.


• Campuses: You can select one or more campuses to only send reminders for groups associated with that campus. This does require that the groups are tied to a campus.


• Parent Group: If you choose a group here, reminders will only be sent to groups that are children (and grandchildren, etc.) of the selected group.

Note that the attendance reminder options available on the group type apply to the Send Group Attendance Reminders job described below.

Send Group Attendance Reminders

This job is very similar to the Send Attendance Reminders for Group Type job discussed above. This job sends a reminder to group leaders about entering attendance for their group meeting. The key difference between the two jobs is that Send Attendance Reminders for Group Type requires a group type, while Send Group Attendance Reminders does not. That means you can have one job handling all of your reminders for all of your group types.

Keep in mind that this job will only send reminders for group types where the Send Attendance Reminder option is enabled under the Attendance / Check-in panel. Each group type can continue to have its own Attendance Reminder Communication Template.

This job is configured to run every 15 minutes. It looks for Group Types that have Send Attendance Reminder checked and once a group's scheduled Start Time is within the Attendance Reminder Start Offset Minutes setting, the attendance reminder is sent. This can only happen once per day.

To get a little technical, when a reminder is sent, the Attendance Occurrence record is created, and the current date/time is written to the AttendanceReminderLastSentDateTime property. This ensures that we never send the same reminder twice in one day.

Group Leader Pending Notifications

This job allows you to notify group leaders of newly pending members in their groups. This provides the following customization options:

• Group Type: The group type to filter off for limiting the groups that are checked for pending members.


• Include Previously Notified: This determines if only newly pending members should be sent to leaders, or if pending members who have already been sent once should also be considered. Note that when you initially set up this job, none of the current pending members will have been marked as sent, so they will all be sent to leaders on the first run.


• Notification Email: This is the system communication template that should be used. A sample system communication called Pending Group Members Notification is provided out of the box for you to use or edit as you see fit.


• Group Role Filter/Role: This is an optional setting that allows you to only include pending members of a specified role. If you don’t select a role, all roles will be considered. You must first select a Group Type before specifying a role.


• Pending Age: Only pending members who have been added or updated within the number of days set here will be included. For instance, you might set this to seven to select pending members added within the past week. Leave this blank to not consider the last time a record was updated.

The notification will be sent to all group members of the group whose role has been configured as Is Leader.

Send Group Attendance Digest

This job sends a summary of group attendance information to certain group Leaders. See the Group Attendance Digest section above for details on the group structure requirements for this job. When you’re configuring this job, pay close attention to the following configuration options:

• Parent Group: The job needs to know the highest-level parent group in the group structure to identify which child groups apply to the job. Again, this job expects a very specific group structure to be in place, so be sure to check out the Group Attendance Digest section above to make sure you're set up correctly.


• System Communication: This is the system communication template that should be used. A sample system communication called Group Attendance Digest is provided out of the box for you to use or edit as you see fit.


• Date Range: You can choose to send the attendance digest for either the ‘Current Week’ or the ‘Previous Week’.

In order for the job to work correctly, the groups taking attendance must meet on a regular (i.e., Weekly) schedule.

Process Group History

This job creates historical snapshots of Groups and Group Members for any group types that have history enabled. Once the job runs, groups that have history enabled will show an 'Archive' option instead of 'Delete'. See the Group History chapter for more details.

This job is set to run once per day in Rock.

Group Attendance Reporting

This job will create new Person attributes to track a person's First Attended Date, Last Attended Date, Times Attended in Last 12 Months and/or Times Attended in Last 16 Weeks for groups specified by a Data View. These attributes can be manually assigned categories and security as needed. This job considers all attendance in the specified groups, regardless of whether the person is currently an active member of the group.

When you're setting up this job, you have the following options:

• Group Data View: You'll need to create a data view that returns the group or groups that you want to report on. For instance, you might select all groups of the Small Group type to report on a person's attendance in small groups.


• Reporting Label: This gets used as part of the name of the attribute(s) that will be created by the job. In the example screenshot below the Reporting Label was "Small Group" so each attribute name starts with that phrase.


• Tracked Values: For the groups returned by your data view, select the attendance data you want to track. In the example screenshot below all four options were selected, so four new attributes were created.

In the example pictured below, new attributes have been added to show Small Group involvement. In this case the attributes were manually assigned to the Visit Information category, to allow them to show on the Person Profile.

This job will create a new attribute only if it does not find an existing attribute (e.g., from a prior run of the job) to update. This depends on how the job itself is configured. For instance, changing the Reporting Label will result in new attributes being created with the new label.

Group Leader Absence Notifications

The Group Leader Absence Notifications job is intended to alert group leaders when a member of the group has been absent a configured number of times in a row. This is so the leaders can follow up with absent people or update their status in the group if needed. Rock ships with a System Communication created specifically for this notification, called Absence Group Member Notification. When you’re configuring this job, pay close attention to the following configuration options:

• Group Type: Because the job only runs for one Group Type at a time, you'll need multiple instances of this job if you want to run it for multiple Group Types.


• Notification Email: You can use the Absence Group Member Notification System Communication that ships with Rock, or you can create your own.


• Group Role Filter/Role: This applies to the members of the group. If set, only group members with the provided Group Member Role will be evaluated and reported by this job.


• Minimum Absences: This is the minimum number of consecutive meeting occurrences for which a person must be absent in order to be included in the Notification Email. If left blank, then '3' will be used. Setting this to '0' will cause the job to fail.

Defining Group Requirements

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

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

1 Name

This is the name of the requirement. This will appear on the Group Member Detail screen in the internal site, and within the fundraising groups pages externally.

2 Description

Be sure to provide a good description of the requirements and any of the underlying criteria that are used to determine whether a group member meets the requirement. A little documentation now will save you headaches in the future.

3 Icon CSS Class

You can optionally associate an icon with the requirement. The icon will appear in places like the group member detail screen, or as a requirement for fundraising groups (e.g., for trips).

4 Category

It can be very helpful to categorize your requirement types, especially as your list starts to grow. To add categories for requirement types, navigate to Admin Tools > System Settings > Category Manager and create a new category with an entity type of Group Requirement Type.

5 Summary

The Summary you provide will be shown in places where the requirement is displayed, such as the group member detail screen.

6 Check Type

So how do we determine the logic of whether someone meets a requirement? Rock gives you three options:

• SQL: In this case you provide a SQL statement. This statement should return a list of Person Ids in the database that meet that requirement.
• Data View: You can also select a data view that returns a list of all the people who meet the requirement.
• Manual: This requires someone to manually determine if a person meets the requirement.

You'll notice that the SQL and Data View options give you a separate property to determine the warning state. You can leave this blank if your requirement doesn't have a warning state.

7 Descriptive Labels

People will either meet the requirement, be in a warning state or not meet the requirement. According to the group member's state, these labels will appear where the requirement is displayed, such as the group member detail screen and as a requirement for fundraising groups.

8 Requirement Workflows

You can launch workflows for people who either do not meet the requirement or who are in a warning state. Based on the Auto Initiate setting described next, the workflow will be launched either manually or automatically. The entity passed to the workflows will be a Group Member Requirement entity. If your workflow has a Person attribute with a key of "Person", the corresponding person will automatically be set in your workflow. Requirement workflows must be automatically persisted.

9 Auto Initiate

You can choose to automatically launch a workflow at the point when Rock first determines that the group member does not meet a group requirement or that they're in a warning state. If this is disabled, then the workflow can be manually launched in places where the requirement is displayed.

10 Link Text

If the workflow is going to be launched manually based on the Auto Initiate setting, this is what the link to launch the workflow will say. If nothing is provided here, then default text (e.g., "Requirement Not Met") will be used.

11 Can Expire

Some requirements, once met, will always be true - say for instance a requirement that you take a specific class before serving. Other requirements may expire. A good example of this is a background check or CPR certification. It's important to keep in mind that the Calculate Group Requirements job will not automatically re-check to see if the person still meets the requirements unless Can Expire is enabled.

12 Expire Duration

When a requirement can expire, you can set the number of days in the future to wait before re-checking the requirement. For something like a background check, you don't need to look every day to see if the background check is still valid.

13 Due Date

Each requirement of this type will have a due date, and this is where you indicate how that due date is determined.

1. Immediate: The requirement applies as soon as the person is added to the group.
2. Configured Date: When adding this requirement type to groups or group types, you'll be able to choose a date on which the requirement is due.
3. Group Attribute: You'll use this option if you have a group attribute that contains the date on which the requirement is due. You'll choose the attribute when the requirement type is applied.
4. Days After Joining: This option gives everyone the same amount of time after joining to complete the requirement.

14 Save

Don't forget to save!

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.

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 icon and adjusting permissions for Override.

Applying Group Requirements to Individual Groups

Once you have defined your requirement, and if Enable Specific Group Requirements is enabled at the Group Type level, you can apply the requirement to individual groups. If you have Administrate access to a group, you'll notice a panel on the edit screen entitled Group Requirements. You can add group requirements from this panel. There is also a setting to keep group members who don't already meet the requirements from being added to a group.

Applying Group Requirements to Group Types

You can also set group member requirements at the Group Type level. This allows you to apply member requirements to all groups of a certain type rather than to each individual group.

To access your group types, go to Admin Tools > General Settings > Group Types. Select the group type you want to add requirements to from the Group Type list. In the Group Type Detail screen, expand the Group Requirements section. From here you can either select an existing group requirement to edit or click the button to add a new requirement.

1 Group Requirement Type

This is simply where you pick the requirement you want to apply. This is where having a descriptive name pays off.

2 Applies to Group Role

You might have some requirements that only apply to Leaders or that only apply to Members. Whatever roles you have, this is where you indicate which role the requirement applies to. If this is left blank, then the requirement applies to all roles.

3 Applies to Age Classification

Sometimes requirements like background checks only apply to adults, whereas a waiver for minors would only apply to children. Here you can choose which age classification the requirement applies to or apply it to all age classifications.

4 Applies to Data View

This is an advanced setting that lets you provide a data view to indicate who the requirement should apply to. This is only needed if the above settings aren't targeting the desired population.

5 Allow Leaders to Override

For some types of requirements, it makes sense to allow group leaders to provide an override.

6 Members must meet this requirement before adding

You might set up some serving teams this way, to ensure new members have passed a background check before they get added to the group.

Viewing Group Requirements

Once you enable group requirements, you'll notice in the Group Viewer that certain group members may have warning icons next to their names. The yellow icon denotes that the group member is in a warning state, while the red icon indicates that the group requirements are not met.

While the icons shown above will give you a general sense of whether a person meets requirements or not, you can switch over to the Requirements tab to view the status of individual requirements.

Clicking on a group member will show you details about the group member and the group's requirements. In the group requirements note that you can Upload Passport for Ted or mark his Trip Insurance requirement as met.

Group Requirement Jobs

The Group Requirements features rely on two system jobs. These jobs can be configured under Admin Tools > System Settings > Jobs Administration.

Fundraising Walk Through

Keep in mind that each fundraising opportunity is a group. You'll manage the opportunities from the Group Viewer.

Ok, but that's the boring part. Let's start looking at how these groups are displayed on your external site! Out of the box Rock configures several pages to view fundraising opportunities. The pages are displayed under the Missions pages (found under the Connect menu item). The missions page lists the various opportunities that are marked Show Public. Keep in mind that this block can be filtered by the Fundraising Opportunity Type (e.g., Trip, Internship, Project).

Selecting one of the opportunities will take you to its detail page. In the example below, Ted (who is leading this particular mission trip) is viewing the page. Since we know it's Ted, a summary of his Fundraising Progress is shown. Links are also displayed to take him to his participant's page and for him to make a payment. Also, note that since Ted is a leader for this opportunity, he has access to a leader toolbox.

Pictured below is the same page, but with a fundraising group that's configured to use families. In this case both Ted and Cindy are in the group, and their individual fundraising goals become combined into a single family goal. Note there is a single Make Payment button for the family, but each member has their own Participant Page.

This page is also used for the general public to view. It allows them to easily register for the opportunity if a registration instance was provided.

Fundraising Opportunities can also optionally be configured with a Content Channel for providing updates. When configured, a new tab will be shown to display these updates.

Another optional setting is to allow commenting on the opportunity. This tab will display a Rock notes control. Keep in mind that this feature currently doesn't allow for approving comments and does not email when new comments are added.

Each opportunity participant has a personalized page that they can share with others to help generate interest and help encourage funding.

As pictured below in green, red and yellow, the participant can use this page to track documents that are needed for the trip and, if configured, launch a workflow to upload those documents. These are really just group requirements that have been added to the fundraising group. They could be used to track things like documents, attendance in classes or background checks. In this example, Ted has a driver's license on file but hasn't provided his passport yet. He hasn't submitted his trip insurance either, but it's not due until a date in the future, so Ted is currently in a warning state.

Each participant can provide a custom opportunity introduction and edit their profile image from their personalized page. This block can also be configured to edit specific person attributes if you wish, such as the Facebook example pictured below.

If the person logged in is the participant, they can also view the gifts that have been given near the bottom of the page by selecting Contributions.

If someone doesn't have a link to a participant's profile page, they can choose to give from the opportunity detail page and select the participant they would like to fund.

If the fundraising group is set up for families, and if more than one person from the same family is in the group, you can give to the family as a whole.

After selecting a participant and clicking Next from the page pictured above, the person will be brought to the Fundraising Transaction Entry page pictured below. There are many block settings for this block, so be sure to review them to ensure this process matches your organization's needs.

1 Fundraising Opportunity

The name of the fundraising opportunity comes from the Opportunity Title group attribute that was set when the fundraising group was created.

2 Participant Information

Based on the person's selection in the prior screen (see prior screenshot above) we see the participant's name, their total fundraising goal and how much they have left to raise to meet the goal. If giving to a family, the family's name will appear here, and the amounts displayed will be for the family as a whole.

3 Contribution Information

When a participant is selected from the prior screen, the Financial Account associated with the fundraising group (set as a group attribute) is passed to this page in the URL. The amount entered here will go to that account. Only Public accounts can be used by this block.

If this page is accessed directly without first selecting a participant, then multiple Donation Amount fields will be present, one for each Public account you have. This can be changed in the block's settings by specifying the Accounts that should be used. The block settings also provide an option to allow the person to choose additional accounts if needed, but this only applies if an AccountId is not present in the URL.

4 Donor Information

This information will be pre-filled for the person if they're known (i.e., logged in). The type of address to use can be changed in the block's settings.

5 Additional Options

The block settings allow you to remove the prompt for email, and also give you the option of asking for a phone number. You can also disable the option for the person to give anonymously.

6 Payment Information

This is where the person will provide their card or bank account information. The title of this area can be changed in the block settings.

7 Previous

This will take the person back to the prior screen, where they can select a different participant if needed.

8 Next

Clicking Next will take the person to a confirmation screen. The header and footer text of the confirmation screen can be customized in the block settings.

Fundraising Opportunity Configuration

As we mentioned earlier, Rock's fundraising features are driven by a set of group and group member attributes. Let's take a look at these settings to see how you can customize each fundraising opportunity to meet your individualized needs.

Keep in mind the group and group member attributes below are specific to a single fundraising opportunity (each one is a group). This allows you to have several types of opportunities, each with their own unique settings and configuration.

Group Attributes

Below is a detailed discussion of each setting for the group that represents the opportunity (Mission Trip, Internship Season, etc.)

Name	Type	Description
Opportunity Title	Text	The group name is mainly used internally. This attribute of Opportunity Title is what will show on the external site when opportunities are listed.
Opportunity Date Range	Date Range	Used to show the start and end dates of the opportunity. For a mission trip, we would recommend that you put the trip dates here. This date range doesn't control when the opportunity is shown externally; it just describes when the opportunity occurs.
Opportunity Location	Text	This is the location of the opportunity. For a mission trip, this would be the city or country. Feel free to leave this blank if it doesn't make sense in your situation.
Opportunity Summary	Memo	A brief description of the fundraising opportunity.
Opportunity Photo	Image	If a picture is worth a thousand words, then we'd better include one.
Opportunity Details	HTML	Now we get to the nitty-gritty of what this opportunity is all about.
Individual Fundraising Goal	Currency	This field determines how much money each person is trying to raise. If each person in the opportunity is raising different amounts, you can provide those unique amounts on their group member attribute (discussed below).
Opportunity Type	Defined Value	The opportunity type helps group similar opportunities. Rock ships with three options (Trip, Internship and Project). You can add your own under General Settings > Defined Types > Fundraising Opportunity Type. This setting has two roles: Acts as a filter for opportunities on the external website (e.g., show only mission trips on this list) Provides a label to describe the opportunity type. For instance, should this opportunity be referred to as a Trip, Project, etc.
Update Content Channel	Content Channel	You may want to provide updates on the status of your opportunity. For example, if your opportunity is a mission trip, you might want to file trip reports. Or if it's a project, you might want to provide updates on the overall funding level or project status. This setting allows you to configure a content channel to manage these updates. If you don't provide a channel the updates tab will be hidden.
Enable Commenting	Boolean	Sometimes you want comments, sometimes you don't. When enabled, a notes block will be added to the opportunity detail. Just remember that there is no automatic email when new notes/comments are left and no approval process. These features may be added in a future release.
Registration Instance	Number	This is what ties in a registration to the fundraising opportunity. You must provide the registration instance ID (currently there isn't a registration instance picker).
Registration Notes	Memo	This short description will show up on the opportunity details page to provide any quick notes about the registration (e.g., A $200 deposit is required).
Allow Individual Disabling of Contribution Requests	Boolean	Opportunity participants can have their own personalized fundraising pages. Some participants may want to use this page to share the opportunity and provide updates, but not want to communicate the financial needs. This setting allows you the option to allow them to disable the sharing of their funding status.
Allow Individual Editing of Fundraising Goal	Boolean	This allows individuals to set their own fundraising goals from their external fundraising profiles. The default for this is not to allow editing.
Cap Fundraising Amount	Boolean	This setting determines if an individual can raise more money than their goal.
Financial Account	Financial Account	This configures which financial account the fundraising opportunity should use to track their money.
Allow Donations Until	Date Picker	An inclusive date that specifies how long to allow donations to participants. Once this date passes no more donations will be accepted by Rock.
Show Public	Boolean	This flag determines whether the opportunity should be displayed on the external website. Since it's common for an opportunity to be displayed long before it starts, and for a brief time after it ends, this flag is used to determine when an opportunity should be displayed.
Participation Type	Single-Select	This is where you select whether the participant is an individual or a family. This controls much of how people interact with the group, as noted throughout this chapter.

Since many of these attributes drive the external display of the opportunity, let's look at an example and see where each value is shown.

1 Opportunity Title

2 Photo

3 Date Range

4 Location

5 Summary

6 Details

7 Trip Updates

8 Comments

9 Registration Status

This is determined by looking at the dates on the registration instance. If the registration is not yet open, the future opening date will be displayed.

10 Registration Contact

The contact comes from the Registration if it is configured.

11 Registration Note

12 Spots Available

This is calculated by looking at the number of registrant openings available for the registration.

Fundraising Financial Transactions

Financial Transactions that are created from the fundraising features will all default to the Contribution type. The account for the transaction will be applied based on the opportunity group setting. It is possible to change the transaction type to a different value than Contribution. To do so, you'd need to create a new page with a Transaction Entry block on it. This block has a block attribute to set the transaction type on the advanced setting panel. You'd then need to configure your fundraising pages to use this new page for processing financial transactions.

In Rock, financial transactions can be tied to another entity (event registration, etc.). Donations that are made as a part of fundraising will be tied to the Group Member of the Fundraising Opportunity group. There is no financial linkage to registrations. This is an important point to understand as there is no way to link money coming in to a registration with that given as a fundraising opportunity. Below we cover several ways you can configure event registration to work with the fundraising tools for maximum impact.

Financial Transactions Matching

We've already discussed that Financial Transactions for fundraising are Contributions that are tied to the Group Members of the Fundraising Opportunity Group. The Rock tools mentioned above do all of the connecting of the group member to the transactions. You might be asking, "What about checks or gifts that need to be entered manually?" And that...is a GREAT question!

After entering contributions (either scanning and matching or through another process), you can link a contribution to a fundraising opportunity participant using the Fundraising Matching page found under Finance > Fundraising Matching.

Fundraising Progress

You can quickly track the progress of fundraising campaigns for fundraising groups. Start by going to the Group Viewer page (People > Group Viewer). From this screen you can view the individual fundraising donations for each group member, below the list of group members.

You can also quickly view the group's overall fundraising progress. Click the button to display a snapshot of both the combined and individual fundraising progress.

If the fundraising group's Participation Type is Family, then the chart combines family members into a single line as pictured below.

How Registration Can Work with Fundraising

As mentioned above, Rock's registration and fundraising tools were meant to work together. That said, financial transactions from these two features don't tie directly together. Below are some use cases to show how you can get these two features to sing in perfect harmony.

Enable Group RSVP

The RSVP function is enabled in group type settings, making RSVP features available to any groups within that type. All RSVP features are tied directly to a group. That means you must have a group created before you can use RSVP. The group doesn't need to have any members, but it needs to exist so individuals who accept your RSVP can be added to it.

To enable RSVP for a group type, navigate to Admin Tools > General Settings > Group Types and open the RSVP settings for the group type.

1 Group RSVP Enabled

This checkbox must be selected to access RSVP features for any group of this type. Once enabled, the other two fields related to RSVP will appear.

2 RSVP Reminder System Communication

Select the System Communication that should be used to send reminders to invitees who have Accepted. Only communications in the “RSVP Confirmation” category will be available for selection. The selected communication will automatically be used with all groups of this type. Leave this blank to set the System Communication on each group individually.

3 RSVP Reminder Offset Days

Indicate how many days before the event the reminder should be sent. Like the communication selection, you won’t be able to change the offset days for individual groups if you set a value here. All groups of this type will inherit the offset days set at the group type level. Set this to '0' days if you instead want to manage the reminder offset days on each group individually.

RSVP - Group Viewer

After you’ve enabled RSVP for a group type, you’ll see a couple of changes when viewing groups of that type from the Group Viewer page.

First, you’ll notice the addition of a new icon that will take you to the Group RSVP List page, where you can view or add occurrences. We’ll talk more about occurrences in the RSVP Occurrences section below.

Second, you can Edit a group to access the RSVP Reminder System Communication and RSVP Reminder Offset Days for that group. These settings are only available for groups where RSVP has been enabled on the group type.

1 RSVP Reminder System Communication

Select the System Communication that should be used to send reminders to invitees who have Accepted. Only communications in the “RSVP Confirmation” category will be listed for selection. If you already set this at the group type level, then you won’t be able to change it here.

2 RSVP Reminder Offset Days

Indicate how many days before the event the reminder should be sent. Like the communication selection, you won’t be able to change the reminder settings for individual groups if they’re already configured for the group type.

Group RSVP List

Clicking the icon takes you to the Group RSVP List page. It will be empty when you first start, but after you add a few occurrences to the list (see RSVP Occurrences) you’ll quickly see how useful this page is. Let's take a look.

1 Date

The date of the occurrence is shown in the first column. You can use the Filter Options near the top of the block to narrow the list by date.

2 Schedule

The check-in schedule associated with the occurrence, if applicable, is shown here.

3 Location

If a location has been assigned to the occurrence you can see it here.

4 Response Progress Bar

This column gives you a graph of RSVP response data:

• Green = Accepted
• Red = Declined
• Blank/Gray = No Response

5 Invited

You can view the count of all invitees for the occurrence, so you know how many people were invited.

6 Response Statistics

In this part of the block, you can see how many people have replied to the RSVP with either an Accept or Decline, and a count of how many haven’t responded.

7 RSVP Detail Icon

Click the icon to access the RSVP Detail page (see RSVP Detail).

RSVP Occurrences

Let’s look at how to add an occurrence to the RSVP List. You'll need to have at least one occurrence set up for the group before you can start sending your RSVP emails.

1 Name

You can optionally set a unique name for an occurrence. This applies only to the occurrence being viewed. Invitees will see the name you provide on the external website when they Accept or Decline.

2 Date

Set the date of the occurrence.

3 Check-in Schedule

Choose the check-in schedule associated with the occurrence, if applicable.

4 Location

Select the location of the occurrence.

5 Show/Hide Additional Fields

Click Show Additional Fields to reveal the settings for custom messages and decline reasons (listed below).

6 Custom Accept/Decline Messages

You can customize the message invitees see when they respond to your RSVP request. We'll show you what that looks like in the Responding to RSVP Requests section.

7 Show Decline Reasons

If the Show Decline Reasons box is selected, then invitees can give a reason for declining. You can choose which reasons are available to invitees from the list of Available Decline Reasons.

RSVP Email Requests

Now that we have an occurrence set up, we’re ready to send out some invitations.

Adding an RSVP request to an e-mail is as simple as clicking and dragging the RSVP tool button (look for the icon) into your email. If you’re not sure how to get to this point, check out the Communication Wizard section in the Communicating With Rock guide.

After the RSVP buttons have been added to the body of your email, use the panel on the right to select the group and occurrence.

1 Select Group

Choose the group associated with the occurrence. Only group types with RSVP enabled will be in the list of options.

2 Select Occurrence

Pick the occurrence for which you want to send an email. The RSVP responses you receive will be for this occurrence.

3 Register Recipients

Click the Register Recipients button to keep track of RSVP data for all the recipients of your email. If this button isn’t used, only people who have responded to your RSVP request will appear in the RSVP List or RSVP Detail pages.

4 Show Advanced Settings

You can use the advanced settings to customize how the RSVP buttons are shown to invitees.

RSVP Detail

Now that we’ve sent our email, we need to monitor the responses. We’ll do this from the RSVP Detail page, which you can get to by clicking an occurrence from the RSVP List page.

The detail block at the top of the RSVP Detail page shows the occurrence details and a graph of responses. The list block at the bottom of the page shows your invitees and their responses.

Not only can you view responses, but you can also update responses or add decline notes if you need to. This ensures you always have accurate information, especially if the invitee responds (or changes their response) by phone or in person.

If you didn’t turn on the Show Decline Reasons option for the occurrence, then the Decline Reason and Decline Note columns won’t be shown.

Responding to RSVP Requests

It may be helpful for you to know what individuals will be seeing and doing after they receive your RSVP email.

Clicking either Accept or Decline in the email will bring the invitee to your external site. What happens at that point depends on how you’ve set up your group, occurrence and email.

Public Group Member Attributes

When adding a member attribute to either a group or group type, you'll notice a Public setting. This setting controls whether the member attribute is included as part of the RSVP response process.

If the Public setting is enabled, then the group member attribute will be shown to RSVP invitees who accept your invitation. This allows you to gather additional information from the invitee beyond knowing that they plan to attend. We’ll show you exactly what this looks like in the Accept section below.

Accept

Invitees will be taken to your website after clicking “Accept” in the RSVP email they received. If you’ve attached any public member attributes to your group, then invitees will be asked to provide additional information (i.e., attribute values) accordingly.

For example, the RSVP Response page pictured below has a field labeled “Need Childcare?” with a drop-down menu below it. This prompts the individual to disclose if they need childcare before finalizing their RSVP acceptance. You can see how this particular member attribute was set up in the Public Group Member Attributes section above.

After the invitee clicks the Accept button on the page pictured above, they’ll be brought to the acceptance confirmation page pictured below.

If you didn't add any public member attributes to your group, then the above page is skipped because there is nothing else the invitee needs to provide. Instead, invitees will be taken directly to the acceptance confirmation page pictured below when they click “Accept” from the RSVP email.

The generic acceptance message pictured above can be customized if desired (see RSVP Occurrences).

Accepts Become Group Members

Rock will always add a person who accepts the RSVP into the group as a group member. This is especially needed when, for example, group member attributes are used. If an individual declines the RSVP invitation, they won’t be removed from the group.

Decline

Just like clicking Accept, you control what happens when a person clicks Decline.

If the person declines, and if you enabled decline reasons, then they’ll be asked to provide a reason.

In the above example a custom decline message is displayed near the top of the block. If you didn’t customize your decline message, then the generic message (pictured below) will appear instead.

If you didn’t enable decline reasons, then the invitee will be taken directly to the page below from the email.

Group RSVP Reminders

The Send Rsvp Reminders job will send a reminder to people who have accepted an RSVP invitation. Those who have declined or who haven’t responded won’t receive a reminder.

The job is ready for you to use out of the box, but it must be manually configured and is intended to be run daily. It will use the RSVP Reminder System Communication for the content, as configured at either the group or group type level. If you haven’t selected a System Communication to use, then the job will not send a reminder.

1 Job Type

For RSVP reminder communications, be sure to select the Send Rsvp Reminders job as pictured above. You’ll then be prompted to select a group type.

2 Group Type

The Send Rsvp Reminders job will attempt to send reminders for all group types if one is not specified here. Otherwise, you can pick a group type if you only want to send reminders for groups of that type. In most cases you’ll probably want to configure a single job, without picking a group type, for all of your reminders. You can create multiple jobs if needed but be sure every instance of the job has its own group type specified or you risk sending duplicate communications.

Don’t forget that the Send Rsvp Reminders job will reference the configured RSVP Reminder Offset Days value (either from the group type or for a particular group) to determine when to send reminders for any given occurrence.