Roles and Worksets
Roles |
Worksets |
Roles are the largest semantic content object. A role is a folder hierarchy comprising other content objects (worksets, pages, iViews). |
As in roles, worksets let you bundle iViews and pages in folder hierarchies. Worksets represent generic, re-usable structures or modules that can be added to roles. A workset may be used in any number of roles, and a role may consist of a number of different worksets. |
The contents of a role are based on company structure and information requirements of the portal users of a company. |
Whereas the contents of a role are based on company structure, worksets contain user-specific tasks and activities. |
Roles are assigned to users. Users access the content that is relevant for them by being assigned to the appropriate role. |
Worksets are not assigned directly to users. A workset must always be part of a role. By adding worksets to roles, you define the appearance of the Enterprise Portal for your users. |
The role structure
defines the navigation structure of the portal for the end user. By defining role structure, you define the entries
that appear in top-level and detailed navigation. For more information see
|
A navigation
structure can also be defined for worksets. However, we recommend that you first add worksets to
roles, and then define the navigation structure within the role. For more
information see
|
You create roles and worksets by creating folder hierarchies and adding content objects to these folders.
Roles can contain the following objects: roles, worksets, pages, and iViews, as well as templates for pages and iViews.
Worksets can contain the following objects: worksets, pages, and iViews, as well as templates for pages and iViews.

