We would like the ability to edit the waitlist warning message at the end of a registration to be editable in the event template controls for text and messages instead of being across all events and not have a way to edit the message. This general language does not work for all of our use cases with event registrations.

---

When setting up group requirements in the Fundraising Opportunity group (for example, uploading a passport), a user logs in to their Rock account and, under their participant checklist, clicks the “Upload Passport” button. Currently, a pop-up message appears saying, “The new workflow has an active form that is ready for input.” It would be ideal to skip this pop-up and take the user directly to the workflow input page instead.

---

Having the ability to filter to active groups or all groups on the Check-in groups block for the Check-in Details page would help in finding correct groups more quickly.  Some of our group lists are over 100 groups, even when filtered by campus.

---

We want to celebrate peoples birthdays when they check-in, especially the kids. We'd love to add the confetti on the check-in if it's the person's birthday. Currently this function only works for when someone has checked in a number of times. 

---

There have been a few occasions where we have wanted to display a person's progress through the statuses of a connections opportunity on our external website, but we don't want to show every status (some of them are for internal processes). If there were a way to designate which statuses were "Public", we could easily filter out visibility of those internal statuses on external sites/apps.

---

We are looking to anonymize our missionary team members but still have the names be unique so that they can donate.For instance, Group Member John Smith joins the CountryA 2025 missions trip. He tells his family his unique missionary donation codeHis family goes to donate to the his trip but they donate to CountryA25-Member01.This way the members are protected but we can still operate.Some ideas of how it would work:The Group Type "Fundraising Group" has a new standard Group Member Field "Anonymous Trip Goer Name". where you would set what you want the anonymized name to read (missionary, member, goer, etc...) ...

---

Person records have always had a Created Date Time field, starting in v18 they will also have a Record Source field. Currently there is nothing in Rock that makes sure these fields are always the earliest value for the record and there are instances where they could be updated to new values and you lose the original information. Record Source can be edited directly in the Person Edit block by anyone with rights to modify person records and both can be overwritten with newer values during a Person Merge. This leads to some strange reporting when you have a list of people...

---

As part of its link click tracking, SendGrid currently enforces a /uni/* prefix for any deeplinks emailed through their service, requiring some decoding on the client app end (https://www.twilio.com/docs/sendgrid/ui/sending-email/universal-links#flagging-your-universal-links).  Currently, Rock only allows the /m/ prefix for deeplinks.  As a result, deeplinks sent from Rock through SendGrid are broken by the service, always falling back to the web URL, even when the Rock mobile app is installed on the device.  To avoid the deeplinks breaking, a "clicktracking=off" property must be added to deeplinks before sending, leaving Rock organizations using SendGrid to choose between functional deeplinks and click tracking.  So this...

---

A new RecordSourceValueId property was added to the Person entity in v18. Adding this as a new column in the Person Duplicate List and Detail blocks would help to make faster duplicate merge decisions. This can be added as a Custom Column but having it as a native column of the block would enable this block to render faster with lots of results versus something like this.{{ Row.PersonId }}{% assign person = Row.PersonId | PersonById %}{{ person.RecordSourceValue }}See:https://prealpha.rocksolidchurchdemo.com/admin/general/defined-types/118https://prealpha.rocksolidchurchdemo.com/reporting/data-integrity/duplicate-finder

---

RockRMS has a well-established process when adding multiple people to a group... you can select a person with the People Picker, then choose "Save" to be done or "Save then Add" if there's another person to add to the group. This is a well-established process and has not been changed since at least Rock 6.0.The LMS breaks this expected process by neglecting a "Save then Add" feature; only an individual "Save" is available.  This means we have to keep going back to the group, clicking the plus again, and going through the process. It's not a huge timesink, but it's...

---