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
I think I just created a copy. we have similar apps where people are given access to documents via groups. but we would like to exclude people from certain documents via such field type
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.
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?