Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Under Consideration
Workspace Domino
Categories Administration
Created by Guest
Created on May 28, 2019

Remove privacy and GDPR relevant information from person document

There are a couple of fields in the person document, which could be seen as privacy or GDPR relevant.
For example the last password change field is something that customers want to hide from users.

The client information (version, machine name) can be disabled via notes.ini setting on client.

But still some admins would like to keep this information.

We got questions from multiple customers to have those fields hidden from users.
But usng the not well supported xACL functionality might be something that adds a lot of complexity and there should be an easier way.

I am also adding it here to see how many other customers have similar requests for the person doc.

 

[ Daniel Nashed / http://blog.nashcom.de ]

  • Attach files
  • Guest
    Reply
    |
    Oct 19, 2022

    agree +1.

    we could hide more field to be read out, e.g. dspHttpPassword, MailFile etc. even to enable 'don't allow url open' in names.nsf>>application properties, if no side effect to Traveler or Sametime.

  • Guest
    Reply
    |
    Jun 3, 2019

    I totally agree

    In my opinion using a combination of standard ACL functions would be enough to achive this gole.

    No new Role is required.

     

    Unless you havn't any higher Access level than author in combination with an available role (user.modifier f.e.)

    should enable you to show these GDPR relevant informations.

     

    If you do not have this role assigned or have only read Access to names.nsf this GDPR relevant informations should be hidden.

     

    Hide When formula on the whole Tab or on the relevant Fields shoud to the Job.