SAP Fiori Theme Personalization Settings: A Practical Administration Guide

SAP Fiori theme personalization settings control how the launchpad and applications look and how users arrange their working environment. Administration teams manage centrally available themes, while individual users personalize supported launchpad and application settings within the permissions and features provided by the system.

This guide separates central theme administration from user personalization, then provides a troubleshooting sequence for cases where a theme, layout, or saved preference does not appear as expected. For platform context, see the SAP Fiori overview.

01What SAP Fiori theme personalization controls

A theme defines visual elements such as colors, fonts, logos, background treatments, and other brand-related styling used by the launchpad and compatible applications. A user can select an available theme when the system exposes the theme selection option.

User personalization usually covers launchpad organization and application preferences, including home-page content, spaces and pages, tile or card arrangement, table variants, filter values, sorting, and other settings supported by a specific application. These preferences are generally stored for the individual user rather than applied to every user.

The exact visible options depend on the launchpad configuration, assigned content, application behavior, and user authorizations. A theme change therefore does not automatically change the content assigned to a user.

02Central theme administration and Theme Designer

Administrators use the SAP Fiori launchpad administration tools to make themes available and to control which theme is used as the default. SAP Fiori Theme Designer is used to create or adjust theme definitions, preview visual changes, and prepare a theme for use in the target landscape.

A practical administration sequence is:

1. Confirm the target system and client before changing visual settings.
2. Identify the standard or custom theme that should be used.
3. Make the required branding or accessibility adjustments in Theme Designer.
4. Preview the result with representative applications and launchpad content.
5. Publish or transport the theme according to the system’s change process.
6. Configure the launchpad to expose the theme and set the intended default.
7. Test with representative business users and browsers.

Theme changes should be validated with high-use applications, not only with the launchpad shell. Application-specific controls can use their own styling behavior, and custom applications should be checked for contrast, spacing, icons, and readable text.

For the broader administration sequence, see SAP Fiori launchpad administration setup.

03User personalization options in the launchpad

Users can personalize the parts of the launchpad and applications that administrators have enabled. Common options include selecting a theme, arranging launchpad content, adjusting display preferences, creating application-specific variants, and saving filter or table settings.

A user-facing personalization check should follow this order:

1. Open the user menu or personalization area in the launchpad.
2. Review the available themes and select the required theme.
3. Save the selection if the interface provides an explicit save action.
4. Refresh the launchpad and open a representative application.
5. Check whether application-specific preferences remain available after navigation or sign-out.
6. Restore a saved variant or layout when the application provides that function.

Personalization is separate from role-based content assignment. A user may be able to rearrange assigned content without being able to add applications that are absent from the assigned catalogs, spaces, pages, or groups. Review SAP Fiori role and catalog assignment when the required application or tile is missing.

04Theme settings versus SAP GUI transaction behavior

SAP Fiori themes affect the launchpad shell and compatible Fiori applications. They do not redesign the classic SAP GUI transaction interface opened through a transaction tile or another SAP GUI connection.

When a business process is available through both a Fiori application and a GUI transaction, compare the user task, required data, navigation, device, and authorization model. The Fiori application uses launchpad content and personalization, while the GUI transaction follows its own screen layout and user settings. Use SAP Fiori versus SAP GUI transaction choice to document the intended user path.

This distinction is important during testing. A successful theme change in the launchpad does not prove that a classic transaction screen has adopted the same visual settings.

05Troubleshooting a theme that does not appear

Start by confirming that the theme was published successfully and is available in the target system. Then verify that the launchpad configuration exposes the theme to the affected user population and that the user is connected to the intended system and client.

Use the following checks:

• Confirm the user can see the theme selection option.
• Check that the selected theme is assigned or available to the user’s launchpad configuration.
• Sign out and sign in again after a central theme change.
• Test in a private browser session to separate server configuration from local browser cache.
• Compare the result with a second authorized user.
• Check whether the affected application is a custom application with its own styling or CSS.
• Review browser developer tools and launchpad logs when loading errors accompany the visual problem.

If the theme is available to one user but not another, review role and content assignment before changing the theme definition. If no users can select it, inspect publication, transport, launchpad configuration, and system routing.

06Troubleshooting saved personalization

Saved filters, table layouts, and application variants can be affected by user identity, application configuration, device type, and changes to the underlying app or content. Confirm that the user is signing in with the same account used when the preference was saved.

A controlled test helps isolate the cause:

1. Record the user, application, browser, and affected setting.
2. Reproduce the behavior with the existing personalization.
3. Open the application in a private browser session.
4. Test with a second user who has comparable roles.
5. Reset only the affected personalization where the application provides a reset option.
6. Recreate the setting and confirm that it persists after sign-out.

If a setting disappears after a role or application change, review the assigned launchpad content and application version. For launchpad structure and content behavior, see SAP Fiori launchpad designer basics.

07Administration checklist for safe theme changes

Before publishing a theme, record the target system, intended user groups, source theme, branding changes, accessibility checks, and rollback path. Test both desktop and supported mobile layouts when users work across device types.

After publication, validate the default theme, user-selectable themes, launchpad navigation, high-use applications, contrast, logos, and application-specific variants. Keep the change coordinated with role and content administration so that a visual change is not mistaken for a missing authorization or catalog assignment.

A clear ownership model also helps: the design or UX team defines the visual intent, the platform administration team publishes and configures the theme, and application owners validate behavior inside their applications.