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
@Thomas: I sort of agree (entering dozens of user names into an ACL is nonsense), but then again I don't: of course using groups is a proven method and to be preferred over entering single names. But "never change the ACL later on" is just not realistic, esp for long-running and complex workflow applications. Consider situations like:
change of group naming schema by administrators (don't laugh: we had those cases!)
adding / removing groups due to an application update
temporarily removing access for standard users during design updates / migrations (in those cases you'll be very happy to know how to restore the original ACL)
QA/QS documentation of effective access at a given time
etc.
I'm aware that we can accomplish all or most of those tasks using various tools (good old design synopsis, copy entire ACL to a different database, best of all use 3rd party tools like Ytria etc.).
But still: having something like this built-in wouldn't hurt at all. That's why upvoted this idea.