In the Micro Focus Identity Manager User Application, themes are specifically designed to control the visual "look and feel." This is achieved by creating a custom theme package that contains Cascading Style Sheets (CSS), images, and other resource files. These files allow an administrator to override the default styles, thereby changing elements such as the color palette for pages, headers, and footers; replacing the default logos with corporate branding; and altering the appearance of navigation tabs and other user interface components to align with organizational standards.

A. Modifying the HTML layouts for individual portlets.

This involves changing the underlying JSP (JavaServer Pages) files, which is a deeper structural customization and is separate from the CSS and image-based changes managed by themes.

B. Assigning different themes to different users upon login to the User Application.

This describes the application of a theme based on user attributes or roles, not what the theme itself controls. The theme defines the appearance, while other configurations handle its assignment.

D. Restricting the pages and tabs that are available to a particular user upon login to the User Application.

This is an access control function. Visibility of pages and tabs is managed through role-based security and provisioning request definitions (PRDs), not through visual themes.

1. Micro Focus Identity Manager User Application: Administration Guide 4.8.

Section 10.1, "Introduction to Customizing the User Application Look and Feel": This section explicitly states, "You can customize the default theme to match your company’s branding requirements. For example, you can change the logo, colors, and fonts." This directly supports answer C.

Section 10.2, "Creating a Custom Theme": This section details the process, which involves creating a JAR file containing custom CSS files to control colors and styles, and image files to replace logos. This confirms that themes control the elements in option C.

Chapter 4, "Managing Roles" and Chapter 5, "Managing Provisioning": These chapters describe how access to User Application functionality (pages, tabs, etc.) is controlled, confirming that this is a security/role function, not a theme function (refuting option D).