Allow document properties to be marked as Sensitive Data elements. #17221
Replies: 3 comments 1 reply
-
Thanks for the feature idea @wicketbr! There's the Admin Only Property Editor package (not for v14+ yet) that could be used for this: https://marketplace.umbraco.com/package/our.umbraco.community.adminonlyproperty However, I will list some problems I foresee with hiding property data for certain users:
Ultimately, you are working on content that is going to be published, for the public internet (or for logged in members). That is not a great place to store sensitive data. This is why we haven't built this as a feature so far. Long post, sorry, but what I really came here to ask is: what is your use case? What do those certain users need to edit that other users in the backoffice shouldn't be seeing? Thanks again, look forward to hearing back. |
Beta Was this translation helpful? Give feedback.
-
I'm thinking of properties that are used for admin purposes. Things like a Google Analytics code, or settings related to securing content or what layout might be used for a given page. Things that an editor shouldn't see and that don't directly relate to the published content. I have options for whether or not an item appears in the navigation menu, items related to whether or not a page is secured. Also, I'd like to be able to have an area where we can select from and insert blocks used for admin purposes only. We also have fields for adding javascript, css, references to external javascript and css files. There have also been times where we have added fields to turn on or off features that we want to manage at an administrative level and not have the users be able to turn those features on and off. I'm sure there are other examples people would have of items they might want to allow only a specific group of users to be able to edit. The admin setting up the content would be responsible for making sure they are not hiding items related to published content that might cause conflicts. |
Beta Was this translation helpful? Give feedback.
-
We have about 100 different sites that all share the same layout template, so we use these other properties to do customization for individual sites. Our university template is used on all the sites, but there might be slight tweaks needed for a given user that can't be done in the template, since the template is shared between all the sites. |
Beta Was this translation helpful? Give feedback.
-
I would like to be able to make certain properties for document types as Sensitive Data elements so that they are only visible to members of the "Sensitive data" group. As it is currently it appears that the Sensitive Data option is only available for Member Types, but that feature would also be useful to make fields that can only be edited by certain users.
Beta Was this translation helpful? Give feedback.
All reactions