You can create a Group through this workflow action by providing the Group Type, Parent Group and a Group Name, which are required to create the group. You may provide the Group Name and Description as either a text string (which can be generated using Lava in the case of the Group Name), or directly from the values other attributes.

If the "Group Attribute" is configured, the newly created Group will be stored in that attribute.

This action sets the selected attribute to a child group of the configured Parent Group that matches the selected Campus attribute. This action is useful when you need to find a matching 'campus' group that exists as a child of a particular parent group -- a common configuration in certain multi-campus group folder designs.

This action adds a person to a specific group that you select in the action settings.

Here's an overview of the settings available for this action:

• Group Member: An optional GroupMember attribute to store the group member that is added. v15.1
• Ignore Group Member Requirements: If "Yes" is selected, the group member will be added regardless of whether they qualify for the group, bypassing defined requirements. Use with caution. v17.0

This action adds a person to a group provided via a workflow attribute. The default role will be used for the add. Optional parameters allow you to prevent the person from being added to the group based on the group's use as a security role, the group's type or its parent group.

Here's an overview of the settings available for this action:

• Ignore Group Member Requirements: If "Yes" is selected, the group member will be added regardless of whether they qualify for the group, bypassing defined requirements. Use with caution. v17.0
• Group Member: An optional GroupMember attribute to store the group member that is added. v17.3

This action will add a person to a group's attendance. You can also specify the date/time and location. There is also an option to add the person as a group member.

v13.6 Added the ability to optionally specify the Campus.

This action will update a group member's attribute with either a text value or an attribute. There is also the option to filter by the group role.

Adds a new note to a group member. The person must already be in the group for this action to work.

The Caption and Note fields are Lava capable so you can include something like this:

This is the note field for {% assign p = Workflow | Attribute:'Person','Object'%}{{p.FullName}} in
the {% assign g = Workflow | Attribute:'Group','Object'%}{{g.Name}} group.

Removes the person from a group that is provided by a workflow attribute.

Removes a person from the group that is selected.

This action sets the selected attribute to a random group member. This action is useful when you need to assign a workflow to a random person in a specific group (e.g. for assigning requests). You can also filter by a Group Member Attribute.

Sets the group member's note property. Keep in mind that a group member can have as many 'Group Member Notes' as you'd like, but this is different. This is updating the note property on the group member.

This action updates a person's status in a provided group.

This workflow action will create either a one-time or weekly schedule. Settings can be hard-coded or set using the values of other attributes. If a name is provided for a one-time schedule, this will make it a "Named Schedule" which will appear in certain places in Rock where named schedules are shown.

If the "Schedule Attribute" is configured, the newly created schedule will be stored in that attribute.

• Adding a Name will make it a "Named Schedule" so it will appear in certain places in Rock where named schedules are shown.
• The "Weekly:" settings will not work for Sign-up Groups/Project Opportunities.

This workflow action will create a sign-up project opportunity. All settings can be set using the values of other attributes, with some allowing hard-coded values.

Note that the allowed location and schedule types for the new opportunity will be limited by the types allowed on the specified project's group type. Weekly schedule types are not compatible with sign-up projects, and will not be allowed regardless of whether they're allowed by the group type.