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.

---

If we provide a way for site visitors to find upcoming RSVP occurrences, the RSVP Block requires that they be logged in, even though it provides a form asking for the person's name and email. If the visitor is logged out, it will always show a message "Sorry You are not authorized to view this invitation."We'd like people to be able to RSVP for upcoming community events even if they're not logged in. So this idea is to allow the form to be displayed, and an RSVP to be added for a new or existing person who matches the information from the...

---

Calendar Lava hides events once their start date time passes. I am suggesting that the Calendar Lava block include events until their EndDateTime passes or allow churches to choose which they prefer.

---

For each collapsed group there is a gender count. Currently it counts everyone on the group. Add a setting so that it would only count the non-leaders in the group.

---

I was working with a delay action in a workflow earlier and forgot that the lower minute limit of the delay action is limited by the "Processing Interval" in the "Advanced Settings" section of the workflow.If the “Processing Interval” is set to 480 minutes (the default) that causes the delay to have a lower minute threshold of at least 480 minutes regardless of the number value entered in the “Minutes To Delay” field.I think it would be a good idea to add a reminder to the information pop up for the “Minutes To Delay” field on the “Delay” action something...

---

Communication Flows currently expose no per-flow security, no audit details, and no send dates in the performance overview. This request covers three related gaps. 1. Per-flow security CommunicationFlow inherits Model<T> and is already ISecured, and the detail and list blocks already call IsAuthorized. However, no block exposes the security editor. The Communication Flow List block computes an isSecurityDisabled field but does not render a Security column, and the Communication Flow Detail block is a wizard with no panel header, so there is no Security button. Request: add a Security column to the list grid and a Security action to the...

---