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
Created by Guest
Created on Jul 17, 2018

ACL in NSF on who can replicate/copy the database and copy/paste documents

A user can make a copy or a replica of a 50GB database and you can not do much about it ,

We all know the annoying (and wonderful) feature that a user can mark thousands of documents and just copy them.
Then the user can paste them many different places, A local database, same original database (very annoying),..
You no longer have the essential control of the data.

There is a setting in the ACL presently to allow "Replica or copy documents" !
That sounds sweet ...and I am sure IBM meant well, but this one also prevents users from doing a copying of text from a document, which will prevent any user from doing their daily job.

This is my suggestion to fix this:


In the ACL on a database add these options instead, to set who are allowed to copy/replicate a database

and these to who are allowed to copy/paste documents

I would probably also consider splitting replica and copy permission into two separate entries

Maybe also creating an entry for copy text etc. is needed, I don't know if this will ever be use

See this blog entry for more background


  • Attach files
  • Guest
    Aug 6, 2018

    I agree, there is something that can definitely be better. Of course, you want to allow the user to copy text that appears but prevent database and / or document copying.
    A workaround that solves today's problems:
    Add an textitem named "$KeepPrivate" with the value "0" in all documents, that allows user to copy text (and print) even if the user is not authorized for "Replicate or copy documents".