Note: |
Lotus Notes must be installed on the same computer as the Administration Console in order for you to be able to modify the permissions on a Domino archive. |
The list shows the users who have access to the archive and the type of access that each user has.
Note that, if the Windows account that owns an archive is deleted, you can still change the archive permissions and there are no errors. It is good practice to tidy up archive permissions when an account is deleted.
. This column lists the names of users who have access to the archive. Click any name in the list to display the permissions that user has with respect to the archive.
. Use this to remove a user's permission to use the archive. Select the user and then click .
. Shows the type of access each user has to the archive. Click any user in the list to display that user's permissions.
The permissions can be any of the following:
. The user has read access to all items in the archive. The user can restore items from the archive.
. The user has write access to the archive. The user can save items in the archive and can also retrieve items from the archive.
. The user is allowed to delete items from the archive. Note that, even though you grant the delete permission here, the user cannot delete from the archive unless you also select on the tab of the Site Properties dialog box.
The first two columns show permissions. Select these to turn the permissions on or clear them to turn the permissions off.
The second two columns show permissions (mailbox and journal archives only). These are set when Enterprise Vault synchronizes the archive permissions to the folder permissions.
You can modify the permissions as required. These permissions always override the permissions (if any). For example, if you select for , this overrides in the column.
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.