Show TOC

Background documentationPermission Scenarios Locate this document in the navigation structure

 

This section describes a scenario, which emphasizes the importance of permissions when working in the portal.

Creating iViews

The following flow depicts a typical scenario describes how permissions would be set up for a single iView in the portal from its inception as PAR file to its delivery to an end user:

  1. A content developer develops new a portal component and wraps it in a PAR file.

  2. A system administrator (User A) deploys the PAR file to the portal. By default, the system administrator gains owner permission on portal components in a PAR file.

  3. User A delegates the read permission on this portal component to a content administrator (User B). User B belongs to the content manager role, and therefore is able to gain access to the Portal Content Studio.

  4. User B creates an iView template based on this portal component, in a folder to which he has owner permission. User B then creates an iView (iView 1) based on the template. That person then edits the iView and defines its default property values and determines which properties can be personalized by end users.

  5. User B delegates the read permissions on iView 1 to User C, whose responsibility it is to create content-based roles for the end users in his organization.

  6. User C assigns iView 1 to his portal pages; a delta link instance (iView 2) to this iView is generated. User C assigns one of these pages to the structure of Role A.

  7. User D who has owner permissions on the company's roles in the portal, assigns to Role A the role assigner permission to User E.

  8. User E, who belongs to the user management role and has access to the Role Assignment tool, assigns end users from the user directory to Role A.

  9. The result is that portal end users assigned to Role A are able to display iView 1.

Note Note

If the iView requires access to a particular system landscape, then User D, who also belongs to the system configuration role and therefore has access to the System Landscape Editor, must also delegate end user permission for the relevant system object to Role A (for end users viewing the content retrieved by the iView).

End of the note.