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.


There should be an easy way to prevent a user from making a copy of a database.

The new functionality would allow the manager of the database to disable file > application > new copy through the database ACL or some other easy to use way.  It should be possible to disable making a copy, regardless of the user's ACL level of access, without losing any of the user's other ACL rights.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 24 2018
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 24, 2018 16:35

    What is the use case? To prevent users from creating documents in the application copy and then asking that they be added to the application on the server?  To prevent users from using a secure app off company premises?

  • Admin
    Thomas Hampel commented
    August 27, 2018 13:50

    Prevent replicate/copy documents in the ACL should provide this already now. 

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 27, 2018 14:07

    I believe that replicate/copy documents prevents too much.  It disallows a user from copying even a single document to the clipboard, if I recall correctly.

    My interest is in only disabling the ability to make a full copy of the database.  Which leads to the discussion of the use case.  It just seems scary to me to allow anyone who uses a database to make a full copy of the database.  Someone with a thumb drive could walk away with a complete copy of our CRM database for example.

    I realize that a user could still copy individual views to a spread sheet.   But, allowing anyone to make a full copy of a database seems to 'wide open' to me.

    For example, we don't want our customer database stored on a sales rep's notebook.  If that notebook is stolen, the thief has potential access to our database.  We prefer to only allow rep's to access the database on our server.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    August 30, 2018 15:58

    An additional item on database advanced properties "allow" local replicas" checkbox should suffice.

    If someone tries to replicate to Server "Local" and the checkbox is not set, prevent creation of the replica

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    September 10, 2018 17:44

    Prevent replicate/copy documents in the ACL should be TWO distinct properties. We cannot implement  response with history using the formula inheritance when the copy/replica is disabled. 

    We don't want users to create a local replica. They just need to create responses  inheriting the data form the parent documents. 

    How many times we have to deal with replications from an OLD replica when the deletion stubs already expired. 

     

    We should be able to control who can create local replicas and how long the deletion stubs should be kept (may be forever in a separate file, like index)