You can preserve multiple users’ data when Nomad for web browsers is being accessed
on a shared computer.
Nomad for web browsers may be accessed on a shared computer in the following ways:
- Recommended: Using different operating system logins. This would keep all
user data separate at the OS level including browser configuration and
data.
- Using different browsers. User data is isolated between the browsers but
co-located on the same OS login.
- Using the same browser with different browser profiles. User data is isolated to
the browser profile but co-located on the same OS login.
- Using the same browser with the same browser profile. There is no separation of
user data so each time the user is switched, the local data must be removed and
the user must start fresh. Because of the user having to start anew each time,
this method is not recommended.
Note: Only #1 keeps the data private from other users. The
other methods allow for user data to be kept separate, but the data is not protected
against users that have access to the same OS login. It is recommended to adhere to
your organization's policies on OS access.
Browser profiles
Nomad data will be isolated to the browser profiles, safely allowing multiple users
to use Nomad.
Consult your browser’s support page for setting up profiles:
Using the same browser with the same browser profile
We recommend using different operating system logins (#1 from the
list). However, if
separate operating system logins or browser profiles are unavailable, Nomad can be
reset to allow another user to login.
Note: If separate
operating system logins or browser profiles are unavailable, Nomad can be reset
to allow another user to login. Reset logs out and removes all Nomad data from
the browser for the previous user, including recent applications, and any local
replicas the user may have created. User data on Domino servers remains
unaffected.
There are three methods within Nomad to reset local Nomad data. One method is
enforced by the administrator via the
resetNomadInstance=1
notes.ini; see
Shared usage for additional instructions.
The other two methods involve the Nomad users:
- In an existing Nomad session, the logged-in user can click Reset
Nomad under the profile menu in the top-right corner.
In
the Reset Nomad dialog that displays, click
Reset Nomad to confirm the action. The user
will then be presented with the login page after resetting
Nomad.
- When a new user is logging into Nomad, if the previous user’s local data had
not been cleared, the following dialog displays:
Click
Log in with original credentials to logout
and log back in as the original user. This should only be necessary when
the logout was not done previously or you have multiple users'
credentials and logged in as the wrong user.
Click
Continue as <user> to reset the original
user’s data and continue setting up Nomad as
<user>. For security reasons, we never
reveal the original user's name.