We have moved to GitHub Issues
Created by Claus Jensen 02 Jan 2018, 08:11:30 Updated by Sebastiaan Janssen 31 Jan 2018, 09:58:48
Subtask of: U4-10796
It should be possible to mark a property as sensitive and then the values would not be displayed in the UX unless for Users with a special role. This only makes sense for Members and Form data and I suggest we only add this to the Member Type Editor (and of course Forms). It should be as simple as a checkbox under permission of a property saying something along “Sensitive Content (don’t show values in the back office)”:
For v1 it’s enough that it’s hidden for everyone - then we can add the users who can read sensitive content later on.
This will actually require some UX changes because currently the checkboxes for properties for member type for "show on member profile" and "member can edit" are not available on 'locked' property types however we will need to enable editing these values on locked property types.
This will also require some database changes to store these values. I think the story points here should be "5"
I'll leave it at 3 for now and see how I go... so far I'm making pretty good progress
Backwards Compatible: True
Due in version: 7.9.0
Sprint: Sprint 77
Story Points: 3