Controlling accessAdded by IBM on June 11, 2010 | Version 1 (Original)
|After creating users and groups, you can assign them access to specific resources, roles, and policies to control what pages and components they have access to. If a user or group does not have access to a component, then that component will not be an available customization option.
After creating users and groups, you can assign them access to specific resources, roles, and policies to control what pages and components they have access to. If a user or group does not have access to a component, then that component will not be an available customization option.
The following lists ways to control what a user or group has access to:
- Managing place members: The place manager can add or remove members. Alternatively, the place manager can enable the self-join option on a place, allowing users to add or remove themselves as members.
- Managing place roles: Each role has a set of allowed actions that are associated with a place. A place manager associates a place member with either custom roles or existing roles. Those roles determine what actions the members can take (for example, ability to read content or read and edit it) and what components they have access to.
- Component-level access: Using the portlets in Advanced administration an administrator can control component-level access. To find out more about the portlets available in Advanced administration refer to the WebSphere Portal information center
- Template access: Manage template access by editing roles and permissions in the WebSphere Portal template catalog. Click the in the Templates tab, and then click the Manage Templates link in the sidebar to open the WebSphere Portal template catalog.
Managing place members: qp85
A place manager must add or remove a member, unless the place was created allowing users to click Join
to join the place themselves.
Creating and managing roles: qp85
Place roles determine place access and what actions can be taken within that place. Roles can have different levels of access for different pages within a place. Places can have custom roles as well as common roles.
Setting user and group permissions: qp85
The User and Group Permissions portlet allows you to view and modify the roles that users and groups have on resources.
Setting resource permissions: qp85
Use Resource Permissions
to manage server resources and assign roles to users and groups.
Managing places catalog access: qp85
Manage places catalog security roles to control which users can administer places catalog, create places, and view public places.
Setting session timeout: qp85
Change the authentication timeout value in the security configuration to indicate how often users must re-authenticate with Lotus® Quickr™.
Parent topic: Administering: qp85