You can define the access of a user or group for a library to determine who has access to a library, and to define access to the different views within the authoring portlet.
You can assign roles to both a whole library, and the item types within a library using either an additive or subtractive methodology.
For example, with an additive methodology, you apply the "All Authenticated Portal Users" to the "Contributor" role to the entire library. This grants "All Authenticated Portal Users" access to the library and any authoring portlets configured to use the library. You then apply Editor, Manager, or Administrator roles to specific resource types to grant additional access to specified users or groups.
With a subtractive methodology, you apply the Manager or Administrator role to a user or group to the entire library. You then apply Editor, Contributor, or User roles to specific item types and clear the inheritance check box. This reduces the access to different item types for specified users or groups.
We recommend that propagation from the Web content library is enabled because this simplifies administering library access and because disabling propagation results in access-related errors.
Assigning access permissions to a library and library item types:
By default, each role's access is automatically inherited down to each item in a library. To prevent a user or group from automatically having inherited access to an item, you need to turn off inheritance on that item.
The permissions set for item types in a library do not automatically give you access to individual items. They only give you access to specific tasks and views within the authoring portlet.
You need to restart WebSphere Portal to enable any configuration changes.