Welcome to the #dominoforever Product Ideas Lab! 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 jointly by the IBM & 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.


A new NoReaders field type

It would be great to have a NoReaders field type that can be used to stop specified user(s)/Group(s) being able to access a document.  I have been asked often if it is possible to stop some users from accessing specific documents.

In some cases it might be possible to implement it through a new group and a readers field, but not always. 

Having a NoReader field type that allows users, groups, roles to be specified would make this easier and allow us to build application functionality around it, i.e.

 - allow users with specific roles/privileges to add a user/group/role to the NoReader's of a document

 - allow an view to be defined that lists documents where NoReaders != "" so application admins can keep an eye on such usage

 - etc.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 26 2018
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 28, 2018 12:46

    Off the top of my head I would say that thoughtful implementation of Readers/Authors fields would get you what you need, but sometimes that's easier said than done.  I'm assuming you're looking at this from the stand point that overall security works fine, but there may be exception cases where a person, or small group of people, may need to have access denied to subsets of data?  And that those exceptions may not follow a predictable pattern?

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 28, 2018 17:36

    Correct.

    Whilst in some cases you might be able to achieve the requirement via a new group / readers field, I have only seen/done this as an exception (i.e. a one off, temporary requirement when the user base for an application is quite small) because it can quite quickly become un-manageable, e.g.

     - an admin could incorrectly add the user(s) into the group without realising

     - its more difficult to track those documents that have been set-up to stop specific users from accessing it

     - As new users of an application get created, they may also need to be manually added to the new groups so they can see such documents

    Being able to add one or more NoReaders fields to a document would make things so much easier, add a nice new level of security to Notes/Domino.