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...

---

We're interested in enabling RCS messaging in Rock RMS using our existing Twilio integration, primarily so messages can be delivered over Wi-Fi/data when recipients support RCS.Can you evaluate what would be required to make this work and provide an estimate of the development effort?Specifically, we're looking to understand:What limitations exist today in Rock RMS that prevent it from using Twilio's RCS capabilities?Would this require changes to Rock core, or could it be implemented as a custom communication transport or plugin?If Twilio already supports RCS with automatic SMS fallback, how much work would be required for Rock to leverage that functionality?Are...

---

Summary Add the ability for users to select and copy scripture text rendered by the mobile Rock:BibleReader control — either through native text selection (press-and-hold → select → Copy) or a built-in per-passage/per-verse “Copy” action. Problem The BibleReader is display-only. Because it renders verse text as native .NET MAUI Labels (which are not selectable by default), users cannot copy any scripture from within the app. People regularly want to: Copy a verse into a text/message, social post, or notes app Paste a passage into a small-group discussion or sermon-prep doc Share the exact wording (not just a deep link) Today,...

---

Description: The Communication Wizard v2 only recognizes the single top-level category set in the block settings when displaying Personalization Segments. Segments organized into subcategories under that parent are not shown in the wizard picker unless they are also directly assigned to the top-level category, creating a significant organizational gap as segment libraries grow.Additional Details: The current workaround is assigning every segment to both its subcategory and the top-level Communications category simultaneously. While this keeps segments visible in the wizard, it eliminates any practical benefit of subcategory organization from the sender's perspective. The picker remains a flat, undifferentiated list regardless of how segments...

---

When using check-in kiosks to add a family, adult phone number may be missed. An adult phone number should be required when at least one child under a set age is in the family. 

---

It would be more efficient if Site attributes could be scoped by the theme applied.

---

Add a "Clear Cache" button to the hidden settings screen (the five-finger press) in the Rock Check-in App that wipes the device's locally cached check-in data and reloads everything fresh. Description When a volunteer or admin does the five-finger press to reach the Check-in App settings, there is currently no built-in way to clear the app's cached state. This request adds a single "Clear Cache" button to that settings screen that resets the cached check-in data so the device pulls the latest configuration on its next load. Additional Details Clearing the cache resolves a couple of recurring issues in one...

---

There have been a number of times where we've wanted to modify how an interface looks and/or functions based on if a person has interacted with a piece of content, prayer request, person, etc in some way in the past.Currently, there doesn't seem to be a simple way of getting to interactions tied to CurrentPerson for a given entity.AppendInteractions Lava FilterOne of the ideas that we came up with was to add a "AppendInteractions" lava filter that works similar to how the "AppendFollowings", "AppendWatches" and "AppendSegments" filters do, but just for interactions. We realize that there are exponentially more interactions...

---

Event schedule durations are currently limited to hours and minutes. It creates confusion when setting up camps, retreats, mission trips, conferences, and other multi-day experiences.For example, a 5-day camp must be entered as 120 hours. A 10-day mission trip must be entered as 240 hours. This is not intuitive for church staff.I recommend adding a Days field alongside the existing Hours and Minutes duration fields.

---

Rock’s page editor currently renders inside the same front-end context as the page content itself. Because the editor view is nested within the content being edited, custom stylesheets, JavaScript, Bootstrap versions, and jQuery-based libraries can conflict with the editor.This creates a major limitation for building faster, more interactive websites in Rock. Modern public-facing sites often rely on optimized CSS, newer JavaScript patterns, animation libraries, interactive filtering, sliders, dynamic cards, responsive menus, and updated framework versions. However, because the editor shares the same rendering environment, these enhancements can slow down or disrupt the editing experience.I am proposing that Rock’s CMS editor...

---