How to prevent Nomad users from opening both server and local replicas

HCL Domino Domino Forum
,
1

Domino/Notes Version: Developer Release 14.0.0FP1
Add-on Product : Nomad
Its Version: Release 2026.03 (1.0.19.145-127)
Operating System: Windows 11 Pro v25H2
Client: Nomad Web using Chrome v151.0.7922.170

We’ve set up Nomad Web to load our application as the Home Page, using policies and Kiosk mode, so when our users start Nomad, they’re automatically presented with our application; and that is their home page, so to close it, they have to exit Nomad.

Our issue arises when they create a local replica, allowing them to edit a database both locally and on the server. We’re need a way for users to open the server or local replica, but never both at the same time. Does anyone know a way to do this that is efficient, easy to maintain, and as smooth as possible for the user?

Any input would be greatly appreciated.

Mario

2

Hi Mario,

we have solved similar scenarios with MarvelClient.

MarvelClient has a real-time action called Nomad Restrict, which can be used to control whether a database can be accessed on the server or from a local replica. The action can also be driven by conditions, so you can define different behavior for different users or groups.

For example, you could configure it so that users work locally when a local replica is available, while falling back to the server if no local replica exists. This can be handled automatically, so users don’t have to worry about which replica they should open.

If that sounds like it could help with your scenario, feel free to contact me at christoph.adler@panagenda.com. I’m happy to demonstrate how it works and can also provide a trial version so you can test it in your environment.