Domino.Doc 3.5 User's Guide - Lotus documentation - Lotus software

About binder security
• If the creator is an Editor, the folder is created on the server by the
scheduled DelayedFolderCreate agent. In this case, there will be a delay
between the creation of the binder and the creation of the folder. If you
access the binder Table of Contents during this delay you will get an
error message that the Table of Contents has not yet been created.
Every binder has a user group that defines who can access it and what tasks
users can perform. The binder user group defines the following users:
Readers — can view the binder; they cannot change binder properties, or
add documents to the binder, or remove them from the binder.
Editors — can view and edit binder properties and profile information;
they can add documents to the binder.
Managers — can modify the binder’s security, delete the binder, move
documents to a different binder, and edit all documents in the binder. The
creator of a binder is its manager.
Binder security defaults from the file cabinet level. All File Cabinet Readers
and Editors are automatically given access to the binders contained in the
file cabinet. Any user can view a binder’s security settings from any of the
Domino.Doc user interfaces.
You can set binder security when creating a new binder, or let it default to
the file cabinet user list. The binder user group is limited to the file cabinet
user group, but the binder Manager (creator) can change the access, limiting
access by removing users from the binder list, or reducing certain users
level of access to the binder.
You can change binder security settings only if you have Manager access to
the binder and have it checked out. Thus, you can change binder security
only from the Notes client, or the browser interface. However, if binder
security has been turned off for the file cabinet, the list of binder readers
and editors cannot be changed. You cannot add any users not already in the
file cabinet’s user list. You cannot elevate the access level of a user. For
example, if a user has Editor access, you can remove that user from the
Editor list, but you cannot elevate that user to Manager.
When you change binder security, the security of all documents in the
binder will be updated to reflect your changes when the binder is checked
in. Specifically, if you remove a user from the binder access list, that user
will be removed from the access list of all documents in the binder.
Similarly, any users who are added to the binder access list, will be added
to the access list of each document in the binder.
Chapter 4: Working with Binders 35