Access

By default, the pages you create in a portal are viewable by all portal members. In the Home portal, the personal pages you create are accessible only to you and the system administrator. You can modify the access for a portal or personal page.

There may be pages you want to expose to many users, but certain components on the page to only a select set of users—or even only one user. For example, imagine that you have created a portal for all sales people. The portal's home page includes two Events task flow instances: one for all sales people and one for sales managers only. You can secure the second Events instance so that only those users assigned the custom role sales_manager can see it.

By default, a component on a portal page is visible to all users who have access to the page. You can set the component's Access properties to show or hide the component, or specify more granular visibility by role or user, or by using an EL expression.

Any component that has associated Access properties can be secured in this way. Those components that do not have associated Access properties can be placed inside a component that does (such as a Box component), and in this way be secured.

To set the access (visibility) for a component on a page:

1. Select a Visibility option:

   • Show component (default) to specify that the component is always visible to all users.

   • Hide component to specify that the component is not shown when the page is viewed. However, the component is shown when editing the page in the portal editor, so that you can modify its Access settings.

   • Customize by role or user to select specific roles and users who can access the component. When this option is selected, the current user is given Visible access to the component by default.

   • Customize using EL to enter Expression Language (EL) that must evaluate to true for the component to be visible.

2. If you select Customize by role or user, click Add Access, then:

   • Select Add Users or Add Groups to search for and select individual users or groups of users available in your identity store.

   • Select Add Roles to search for and select defined roles.

   • Select Add Authenticated Role to change component access for all authenticated users (that is, to users who are logged in to WebCenter Portal).

     This selection adds the role authenticated-role under Role or User, with access to the component by default.

   • Select Add Anonymous to change component access for all public users (that is, users who are not logged in to WebCenter Portal).

     This selection adds the role anonymous-role under Role or User with access to the component by default.

     Note:

     To grant component access to the anonymous-role (that is, to enable users who are not logged in to access the portal) the portal must be public. The portal cannot be private or hidden.

   • To remove component visibility, select the user, group, or role in the Role or User list, then click Delete Access.

3. If you select Customize using EL, enter Expression Language (EL) that must evaluate to true for the component to be visible.

   For example:

   • To expose a component only to members of a particular scope who are assigned a particular role in that scope, enter:

     #{WCSecurityContext.userInScopedRole['role']}
     

     where role is a role name, such as sales_manager.

     The scope is implicitly resolved to be the current scope:

     • If you use this EL in the Home portal, it resolves to Home portal GUID and roles defined at the application level.

     • If you use this EL in a portal scope, it resolves to roles defined for the portal.

   • To expose a component only to members of a group, enter:

     #{WCSecurityContext.userInGroup['group_name']}
     

   • To expose a component only to a specific user, enter:

     #{WCSecurityContext.currentUser['user_name']}
     

4. Save your changes.