We use the attribute field type of Group Member at times to use with another Group member attribute. What I find is that it does not limit the choices of the selected group members to only active members. I propose that there be an added option to indicate if you only want to display or use "Active" group members in the referenced group.

---

Right now in Rock’s Group Scheduling, volunteers can only select one preferred role per service time. This creates a limitation when someone is willing to serve in more than one way at the same time.For example, a volunteer might prefer to be an Usher at 8 AM, but would also be happy to serve as a Host at 8 AM if there are already enough Ushers. Currently, there’s no way to indicate that kind of secondary option and allow the automated scheduling to know about it.It would be really helpful to allow a second preferred role for the same service...

---

Hello! Would be nice to set a Step Status as the Default for new entries. Connections has an option as Is Default. One less field to set when doing a Bulk entry. 

---

Current Limitation:Right now, Rock’s Steps feature allows automatic completion of a step based on a selected Data View. However, automation is limited to step completion only.Proposed Enhancement:It would be extremely helpful to enable selecting a separate Data View for each individual status within a Step (e.g., “Started,” “In Progress,” “Completed”). This would allow users to automate progress more flexibly—automatically triggering both the start and progression of a step, not just completion.Example Use Case:Instead of manually marking when someone “starts” a step, a Data View could automatically move people into the “Started” status as soon as they meet certain defined criteria...

---

For larger event registrations like summer camps and classes, it would be great for Rock to offer us an option to require either full payment or a payment plan at checkout for the registrar. This would eliminate the need for manual payment reminders. While the current system makes follow-up easier, requiring payment plans upfront would significantly reduce risk, minimize staff time spent on payment tracking, and lower associated costs.

---

Hey there! DescriptionEnable the ability to add new recipients to an existing scheduled communication before it is sent.Additional DetailsCurrently, once a communication is scheduled in Rock RMS, the recipient list is locked and cannot be modified. This limitation makes it difficult to adapt to last-minute changes or additions—especially when communicating with dynamic groups like event attendees, new visitors, or registrants.I’m requesting a feature that allows users to add recipients to a scheduled communication without needing to duplicate or recreate the communication. Ideally, this would be available via:A simple “Add Recipient” or “Edit Recipients” option available on the communication record until the...

---

The calendar lava block currently allows you to set the audience filters, but does not have a way for certain audiences to be displayed by default. This would be helpful almost anywhere where upcoming events are displayed. Also, there should be a way to set the number of occurrences of an event to be displayed. As an example, when we have classes we want on the calendar that have multiple dates they take place, or the blood drive we host, I don't want the calendar list to be cluttered with the next 5-10 occurrences of that event.

---

Currently, if we want to communicate with a particular campus and then have other communication segments, the current option is to have segments for the different campuses. That creates other issues with the "All segments" or "Any segment" option. If we want to send communications to parents of incoming middle school parents at a particular location, that's fine, but if we are sending to a couple campuses, or sending something to just 9th and 10th grade parents at one campus, that's not possible as no one is in 9th AND 10th grade.

---

This idea is related to another idea that has already been implemented. And we do appreciate that SMS Pipeline Actions can now chose to have an Interaction logged. But now as I'm beginning to work with interactions more and maybe starting to understand them a little better, I would like to suggest an enhancement to how these SMS Pipeline interactions are structured.As currently designed, there is a single Interaction Channel for all SMS pipeline interactions, each individual pipeline has an Interaction Component, and the pipeline actions are the interactions. For churches that only have a single pipeline but LOTs of actions (i.e. keywords),...

---

Our church hosts several conferences and large ministry events throughout the year at various campuses. We've been using eventbrite as a solution since the initial purchase to check-in at the door is a seamless process but eventbrite charges a staggering 20% listing fee to use their platform. We would like if Rock could generate a unique QR code once a registrant has finished payment for an event that would be sent to the registrant's email, similar to ticketmaster or stubhub. We could utilize QR code check-in from a fixed or mobile check-in station camera.Additionally, if it's possible to have live...

---