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.

---

Today if you want to use the /api/Lava/RenderTemplate to test Lava with specific commands, entity, sql, workflowactivate or other entity command you have to enable those commands in the global allowed commands list. I propose that this endpoint should have it's own settings for what is enabled on it. It is already a secured API endpoint so having it's own configuration without having to allow commands globally would greatly benefit dev's without compromising the entire sites security.A separate setting for the endpoint, for example a Global Attribute or System Setting such as "Lava Render API Enabled Commands," used by `RenderTemplate`...

---

In Legacy Check-in, there is an option that automatically selects all Areas (Group Types) a person is eligible to check in to and skips the Area selection screen altogether. This allows organizations to keep Group Types hidden from end users and present only the groups they can actually check in to.For many churches, Group Types are an internal organizational structure and are not intended to be visible to the public. In our environment, displaying Areas creates unnecessary confusion because attendees often don't know which Group Type contains the group they are looking for. What they do know is the specific...

---

The HTML editor toolbar does not include superscript and subscript toolbar actions for the Content Channel Content property. You can select Code Editor or HTML Editor but can't specify the toolbar type. If you create a new content item attribute and use HTML field, you can set the Toolbar Type to Full. It would be nice to have the option to select the toolbar type or change it to full by default.

---