When using KeyPass in the enterprise, there will typically be an administrator who updates a reference database located in a network shared folder, and a number of users who synchronizes with it.
The administrator first installs KeyPass on his local machine, creates a master database and adds one or more read-only passwords to the database. He then configures the network location of the reference database. Finally he makes the reference database available over the network by selecting(or manually copying KEYPASS.DAT to the shared folder).
Note: The shared folder where the reference database resides should be read-only to all users except the administrator.
The user installs KeyPass on his own machine and imports the reference database from the shared folder using. He logs in to KeyPass using one of the read-only passwords assigned by the administrator. He can then make use of his local copy of the database and even configure some personal settings (eg. hotkey, browsers/applications etc.), but he will not be able to modify any of the database entries.
Now when the administrator updates the master database on his local machine and wants to publish the changes, he simply selectsto update the reference database in the shared folder. When KeyPass (running on the user's machine) detects that the timestamp of the reference database has changed, it will replace the local copy with the new content, but the user's personal settings will be preserved.
It is also possible for the administrator to prevent certain users from accessing parts of the central database by using security tags. Basically, this involves assigning matching tags to both read-only passwords and database entries so that only those passwords with the relevant tags can access matching entries. For more information, see Security tags.
When using KeyPass in the enterprise configuration, the administrator and each user will require a KeyPass Enterprise Edition license. This is because only the Enterprise Edition supports read-only passwords and security tags.
|Converted from CHM to HTML with chm2web Standard 2.84 (unicode)|