Application Template Roles portlet

 

+

Search Tips   |   Advanced Search

 

Use the Roles portlet to manage the roles defined by a template for the members of the composite applications that will be created from the template.

The roles defined in an application template specify the levels of access that application members have when they work with instances of composite applications created from the template.

We can...

  • View membership roles already defined
  • Create new roles for the application
  • Edit the definition of a role
  • Delete a role

When you create or edit a membership role, you specify...

  • Name of the role
  • Description
  • Access settings

The roles defined in the template are also available for editing by application users with permission to edit the application, becoming available to application users when they work with the membership portlet.

Application users who have permission to manage members also use the membership portlet to...

  • Add users to the membership list
  • Assign them roles
  • Reassign member roles
  • Remove members
  • Restrict application access to members only
  • Make the application available to all authenticated users

 

Viewing roles

From the drop-down menu of an application template that is listed in the Application Template Library, click...

Manage Roles

...to display the Roles portlet.

If no new roles have been created in the template, the list of roles includes only...

  • Default roles
  • Administrators
  • Users

From the list of roles, we can view the roles that are defined for the application and see a description of the access that each role provides to members assigned the role. The role description generally identifies the limits of application access and is useful for distinguishing roles that provide manager access from roles that provide non-manager access.

A role that provides manager access to the application can include permission to edit the application and its pages or manage the membership of the application, or both.

A role that provides non-manager access to the application allows application members in the role to participate as general users; general users do not have permission to edit the application and its pages or manage the membership of the application. These application-specific permissions are indicated by a check mark that indicates whether these permissions are enabled for the role...

  • Edit Application
  • Manage Members

If the role is not the last one that permits users to edit the application, we can delete the role.

 

Create and editing roles

Clicking New or the name of a role opens the window for creating a new role or editing an existing role. We can choose to base the new role on an existing role. When you create or edit a role, you select options for...

  • Application and Page Access Settings
  • Component Access Settings

...to choose the level of access that users will have for the application and its pages, and the components of the application.

  • Application and page access

    All members of an application can view application pages, regardless of their assigned roles.

    Two additional settings grant permission at the application level:

    • Allow members of this role to edit the application and all pages of the application
    • Allow members of this role to manage the membership of the application.

    Select one or both settings to extend the access provided by the role.

    If you are editing a role that provides manager access and it is the only role that provides manager access, we cannot edit these settings. An application template must have at least one role that provides manager access.

    If you are creating a new role or editing a role that provides non-manager access, we can edit these settings.

    Choosing to allow members of the role to edit the application automatically grants permission to manage members; that is, if the role allows application editing, it must also allow membership management. We can, however, choose to allow members of the role to manage membership without allowing application editing.

  • Component access

    Access to the components that are deployed as portlets on the pages of an application is controlled first by page access and then by levels of access that are defined for each component. The levels of access that are available for selection for each component vary and include descriptions.

 

Parent Topic

Work with application templates