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

---

I think it would be a great cost savings for churches to be able to use Amazon Fire or Android tablets for the Rock Check-In. They are less than a third of the cost. Many churches have these tablets and the only purpose is for checking in and printing labels. Too much of a resource for the costly iPads.

---

The new option to automatically skip the "Skip" screen when using the select all schedules option is probably a great addition if your check-in is configured for it. We have situations where select all schedules is not desireable, but skipping the "skip" screen automagically would be a huge help. If it's possible we would like to request that the skip the skip screen be an option even when not using select all schedules.Our use case applies to both Volunteer check-in kiosk and Children check-in kiosk. In each case, multiple schedules are available but probably should not all be selected, and...

---

Event registration is getting better all the time with new additions such as the newest addition that lets people add new family members during the registration process. However, there are some situations where this is not desired. With the recent new addition we now have no option to ony let people select existing family members without also showing the add new family member action.It would be nice to have an option that turns this new feature off when using the registration options for Registrants In Same Family set to “Ask,” and Show Family Members is enabled. Previously, this was the...

---

Next-Gen Labels Rock. I just wish there were a few more features to super charge them in situations where you want images, icons, or conditional labels to show\print. It would be nice to have Conditionals for "In Group" or "In Dataview" so that we can build out groups\dataviews and display label content based on this.If we had this it would open up many new use cases. At this time, you can choose person properties, attributes, check-in related items and achievements which are great, but there are situations where we don't want to add new person attributes just to be able...

---

For our missions teams, we have created a Short Term Missions Team group type that inherits from the Fundraising Opportunity Group type and these groups are all included in the fundraising blocks on the public website.However, when we attempted to create a group type for our Youth Missions Team that inherits from the Short Term Missions Team group type, it is not included. This is needed as there are additional group attributes, member attributes and group requirements needed for the youth teams.While it is possible to create two separate group types that each inherit from the Fundraising Opportunity Group Type, this...

---