Hi Chris,

As I am marked as having "Supervisor" rights and do not belong to a "Group", the additional unwanted fields are still showing up for me in webview.

My request that as in database view they can be "Hidden" for all via Config, this needs to be either replicated in webview or made possible in webview.

Thank you everyone! This is exactly the information I was looking for. We will be looking into this and will update you just as soon as we have this planned out.

Thanks Chris. While I appreciate that we can still hide the field by adjusting individual user/group permissions, the system-wide setting should be functioning as expected in web view to reduce the manual effort required.

Having to hide the field individually for each user/group adds unnecessary administrative burden, especially in databases with a large number of users/groups. The system-wide setting was intended to streamline this process.

Further, as mentioned by other commenters, the "Display As" functionality for fields does not translate over to web view.

Hi Chris, I am finding that I am not in the group listed when I hide these fields. When I go to my user profile, I do not see the same option to hide fields. Any help on this would be appreciated

Chris, here is an example of how this isn't working (marked one way in DB view and still appearing in Web View). None of the settings for these fields are transferring over to the web view from DB view.

If they are all going to appear in web view we need same ability to rename. Web view now displays "Religion" as our data for alumni married to alumni.

Chris, I see now that you are talking about Security settings, but what about Configuration > Fields > Constituent settings? This is where we have the Religion field marked as hidden.

Just checked my system and it does indeed function properly now. If I uncheck view in DB view, it makes them go away in Web view as well. Takes about two minutes for the changes to apply in web view. But as you can tell from the trail of comments below, that wasn't initially the case. Thanks.

We have Religion hidden, but it still appears in NXT.

We have Birthplace, Target, and Income all selected as Hidden in database view but those fields still appear on constituent records in NXT. The settings in database are not controlling NXT.

Hi Chris...I personally haven't tested it lately but when it was initially released, when you on checked those boxes in db view, it was not hiding them in web view. Going to check now to see if that has since been corrected.

Hi everyone, I am keen to understand this in more detail. These fields can already be controllable using database view security roles (see image attached). This applies to web view and database view so I am keen to understand the scenarios where this is not working as expected. Thank you for all your feedback!

I really hope the option to hide these fields is developed. In this day and age, having an ethnicity or religion field seems very inappropriate. Also, income should be a dropdown with ranges, as that also seems very intrusive. It also really crowds the panel, making it more difficult to find other information. Please make the display of these fields optional!

It would be best if the field configurations would just carry over from database view to web view. I would prefer to not have to mark a field as hidden in both views.

Oh my word, I completely agree, We don't need most of this information and could with the ability to hide it as it is not helpful clogging up the page.