There is currently no supported, configuration-level way to enroll a group of people into an LMS Learning Class. Every existing "add people to a group" tool in Rock — Group Sync, the Group Member Add workflow action, and the Bulk Update block — is unaware of the LMS and cannot produce a valid enrollment. The only built-in enrollment paths are the manual class roster and public self-enrollment, both of which are one-person-at-a-time and person-initiated.We would like Rock to provide official ways to enroll people into a Learning Class in bulk and from automation, so that common scenarios (e.g. "everyone in...

---

DescriptionGive people a personal calendar subscription URL that delivers everything their immediate family is committed to at the church: events they and their spouse are registered for, events their kids are registered for, the groups they are scheduled to serve in, and any event types or calendars they choose to follow. It is a live subscription feed, so it lands in Google Calendar, Apple Calendar, or Outlook alongside work and school and stays current on its own. The mobile app and website are where a person generates the feed and manages what is in it.Ministry NeedThe most common piece of...

---

When people manually enter new families using the New Family page, the data could be coming from many sources: connect card, cash/check contribution, etc.  Add the Record Source selector so the person entering the person/family can denote the real source, instead of having to go back and then manually edit each new family member's record.

---

Add the new property Record Source to bulk update so we can easily go back and update all of our pre-18 records.

---

Right now, we cannot sort the accounts for the Mobile Giving Block. During different seasons, we would like certain accounts to be higher up on the list. We also want to be able to default to a specific account.It would be awesome if we could select a default account and/or sort which accounts show up first on the list of accounts.

---

Add Record Source field to Edit Family > Add New Person.

---

It would be helpful to have a view that displays each classroom with its current attendance alongside the room's capacity, making it easy to determine where another child can be added.Color-coding would make this even more intuitive:Green: Room has available capacity.Red: Room is at capacity.This would allow staff and volunteers to quickly identify which classrooms are available without having to calculate occupancy manually or have to memorize all room capacities.Also noticed there isn't the ability to open/close rooms from that view anymore

---

Protection profile may not make sense for staff and super volunteers when attempting to sign-in with passwordless login. Please expose this error message to the obsidian Login Block similar to other error messages so churches can provide context as need.

---

Add a checkbox to check-in group/type configuration that enforces a group's Group Requirements at the point of check-in, preventing a group member who does not currently meet those requirements from checking in to that group.Current Behavior: Check-in configurations can already restrict check-in to existing group members. However, this "must already be a group member" setting does not take Group Requirements into account. A person can be a group member in good standing on paper, but out of compliance with a requirement (background check expired, required training not completed, document missing, etc.), and still be allowed to check in.Group Requirements themselves can...

---

The Connection Opportunity Signup block collects mobile phone numbers but does not provide an option for the individual to grant SMS consent. Other public-facing Rock experiences—including Registration Entry, Group Registration, Family Pre-Registration, and workflow person entry forms—can display Rock’s standard SMS opt-in control. The Connection Opportunity Signup block should support the same consent experience. Current Behavior The block can collect a mobile phone number. The current Obsidian implementation explicitly hides the SMS opt-in control using hideSms="true" in the block source . A Connection Request Boolean attribute can be displayed as a workaround, but it only saves an attribute value. It...

---