RequestRock’s phone-number fields currently use one system-wide default country code—the first ordered value in the Communication Phone Country Code defined type.For churches using shared forms across multiple countries or international campuses, this creates unnecessary friction. For example, our primary/default code is Australia, but a person completing the same form from another country is initially shown Australia’s code and must manually change it before entering their phone number.Proposed enhancementAdd configurable country-code defaulting for Rock phone fields, with a priority order such as:Explicit field/block configuration — an administrator-selected country code, where applicable.Campus or site context — use a country code configured for...

---

Drafted with Claude Code on behalf of Geoffrey Roberts (Saddleback Church), who reviewed it and is posting it. Churches with campuses outside the US often find that their members use WhatsApp rather than text messages. Twilio sends and receives WhatsApp through the same Messages API Rock already uses for SMS, so Rock could support WhatsApp with very little change. We tested this on Rock 19.8.1 with Twilio’s WhatsApp Sandbox: Incoming messages already work. Twilio posts WhatsApp messages to Rock’s existing TwilioSms.ashx webhook with the numbers prefixed whatsapp:. Rock’s person matching strips the number to digits, so the sender is matched...

---

The REST API v2 OpenAPI document (/api/v2/doc) describes every enum as a bare list of integers with no names. Generating a typed client from the spec (NSwag, Kiota, OpenAPI Generator) therefore produces enums whose members are _0, _1, _2 and so on. Where an enum has two names for the same value (for example GroupType.AttendanceRule), the generated code has a duplicate member and doesn't compile. We checked against Rock 19.8.1. The spec has about 220 inline enums and none of them carries names. The v1 Swagger configuration calls DescribeAllEnumsAsStrings() (Rock.Rest/Swagger/SwaggerConfig.cs); the v2 configuration (SwaggerConfigV2.cs) has nothing equivalent. Suggested change: add...

---

We built a custom AI Agent skill, "Ark Rock Ops," so Claude can triage Rock issues for us the way a second admin would: read the exception log, check job health, and look at the web server itself. It has changed how fast we find and fix problems, and none of it is specific to The Ark.Seven of those tools would help any organization running Rock, and we would like the core team to consider shipping them (or something like them) as a built-in administration skill. Four of the seven are built on `{% execute %}`, which we understand is being retired in an...

---

I created a defined value for cities for filtering with the core group finder block. I enabled adding new items so that group managers can add new cities when they create groups instead of going to defined types to add another value. The core group finder block includes the Add Item button in the filters for end users to use. I suggest removing this ability so that filters work as view only.

---

Content Components that personalize or pull data from the source of truth rely on the global attribute Default Enabled Lava Commands. When that setting is cleared, those content components break. Adding Enable Lava Commands for each Content Component would ensure templates continue to work as security improves.

---

Communication templates rely on the global attribute Default Enabled Lava Commands to include rock entities such as campus address or defined values. When that setting is cleared, communication templates break. Adding Enable Lava Commands for each communication template would ensure templates continue to work as security improves.

---

I didn't find this already suggested.When I want to build an email, I can't drag and drop blocks (Title, Paragrqaph) into the email builder using the touch screen on either my phone or Chromebook. On a notebook this would be a mere convenience, but on a phone or tablet this is necessary to build emails on those devices, where a mouse/cursor is not available.

---

I’d like to propose displaying signal icons next to registrars and/or registrants in registration instances. Many Rock users primarily work in registrations more often than in the groups they’re tied to, so currently the only way to catch a signal is to open each profile individually or view them in a group (which for now is a good work around, but many won't go this route). Surfacing signals in the registration and registrant view would help users spot potential security concerns early, especially when a registrar signs up others and may be unaware of a concern involving someone in their...

---

With the new code editor using Monaco Editor, I think the most useful one is code folding and color highlighting. I understand I can use Magnus but it doesn't support everything and the UI is still useful.

---