IBM WebSphere Portal 8.5: User assistance for administrators |
---|
Defining roles within a library
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.
Before you begin
About this task
You can assign roles to both a whole library, and the item types within a library by using either an additive or subtractive strategy.
For example, with an additive strategy, you apply the "All Authenticated Portal Users" to the "Contributor" role to the entire library. This strategy grants "All Authenticated Portal Users" access to the library and any authoring portlets that are configured to use the library. You then apply Editor, Manager, or Administrator roles to specific resource types to grant extra access to specified users or groups.
With a subtractive strategy, 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 strategy reduces the access to different item types for specified users or groups.
Propagation from the web content library is the preferred strategy because this strategy simplifies administering library access and because disabling propagation might result in access-related errors.
Procedure
Assigning access permissions to a library and library item types:
What to do next
By default, each role's access is automatically inherited down to each item in a library. To prevent a user or group from automatically inheriting access to an item, you must 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 give you access only to specific tasks and views within the authoring portlet.
- Property name: default.inherit.permissions.enabled
- Value: false
You must restart WebSphere Portal to enable any configuration changes.