Have a red dot or icon, a note, or color change signify that a known relationship to a person is deceased.We sometimes mark them with a Deceased / Survived By relationship, but if we just connect as a relationship and they are deceased it would be worth making that directly visible.

---

It would be incredible if there was an option on pages/blocks that allowed you to choose a dataview or group(s) to allow access to a page/group.I know currently I can create a dataview and then create a group sync to a security role and then do it that way. But I thought this might come in handy and be a little quicker. Also not require creating a bunch of security roles. Vote if you think so. :)

---

The Connection Request Detail block displays the connection status options when editing the connection request. Each Connection Status has a description field available when the Connection Type is defined, but that field is not made visible to the user.A tooltip with this description when the user hovers over a particular status would help users better understand how to use the defined status values.

---

I thought it would be nice if there were channels for each individual plugin. So when you bought the plugin you were given access to that channel. It could become a great place to get support and also share how you are using the plugin.After thinking about this - I guess it wouldn't have to be private groups. If someone was thinking about buying a plugin they could go see the channel and see how people are using it.

---

The RockU videos should keep playing the next video in a series or at least have a button to watch the next video. It's annonying when in full screen to have esc out, click the next video, and then re-fullscreen. especially when most of the videos are 3 min or less.

---

We would like the ability to do everything the "Person from Attribute Fields" does, but WITHOUT creating a new record.  Essentially, we could create a workflow that identifies a "potential match" that a worker could then verify in a second workflow step.  Real Life Scenario: We have a digital connection card. an overwhelming number of people are entering their firstname, lastname, phone and email but in the firstname putting things like "Joe and Mary" instead of just a single name "Joe."  On the backend we have tons of extra records being created that then have to be merged.  The software assumes...

---

Have the ability to allow inactives in the check in process to be part of the workflow or block settings of the search rather than controlled in the Check-in Configuration so that it can be set differently for Attended check-in or Unmanned self check-in. We use the Attended Check - in plug in which has a separate workflow and separate page structure, so this could be managed differently in Attended or Unmanned check in, but since it is tied to the configuration which is the same for both instances of check in we can't have a difference.

---

The Family Pre-Registration block does not seem to show a family address as an editable field. It just appears when you pull up the form. It would be awesome to have the ability to make the address a required field to collect that information from new families. If it had the feature of other fields on the form we would have the ability to make the field hidden, optional, or required.

---

I would love for the prayer system the see a major overhaul allowing people to created prayer request lists based on needs. Ideally lists could be created for campuses, groups, or people and easily associated with them. If a prayer request is associated with a group it would be even more amazing to allow leaders to enter prayer requests for group members and choose if the request stayed just in the group or could be shared back with the prayer team and/or staff. When someone entered a prayer session allowing them to choose the prayer lists from groups, or campuses they are...

---

We would like the ability to add custom fields (attributes) to benevolence requests. There is other information we collect on our application that we would like to track. 

---