Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Submitted
Workspace Planning Analytics
Created by Guest
Created on Sep 10, 2026

Allow end users to select their own PAW theme from admin-approved options

Background: In the current scenario, administrator(s) in PAW can define a theme and activate it. This theme is global in nature i.e. all the users inherit the theme set by the administrator(s).

Challenge:

  1. No team-level branding — When multiple teams or business units share a single PAW environment, they are all forced into one theme. Admins must settle for a generic, one-size-fits-all branding rather than reflecting individual team identities.

  2. No personal preference support — Users have no ability to select a theme suited to their own working style or accessibility needs. For example, User A may prefer a light background, while User B may prefer a dark background to reduce eye strain — but PAW currently offers no way to accommodate both.

Proposed Enhancement 1:

The feature to have Administrators create new themes will stay as-is. For ex: PAW admins create 4 different themes in addition to the System default. Admin activates theme #2.

However, now allow admins to assign a default theme per security group. For ex: the Finance team's group defaults to Theme #1 (their brand colors), while the Sales team's group defaults to Theme #3

Proposed Enhancement 2: Add a new user-level setting under each user's profile that allows them to:

  • By default, inherit the admin-activated theme (Theme #2 in this example).

  • Optionally override this default by selecting from the pool of themes the admin has already approved/created (System Default, Theme #1, Theme #2, Theme #3, Theme #4).

  • If possible, allow a preview of the theme before applying.

Benefits:

  1. Improves user satisfaction and accessibility without compromising governance.

  2. Requires no new theme-creation capability — purely exposes existing admin-created themes to users via a selector.

Needed By Not sure -- Just thought it was cool
  • Guest
    Sep 26, 2026

    +1

    From a governance and accessibility perspective, I think the user-level selection is a useful extension of the current admin-controlled model.

    One point I would add is that the selected theme should ideally be respected consistently across the PAW experience, including books and widgets. If individual books use fixed colors, users may still get inconsistent results when switching between themes.

    A semantic color/token approach could help here: administrators could control the available themes and branding, while books use theme-aware values instead of hard-coded colors. This would allow more user flexibility without losing central governance.

  • Guest
    Sep 26, 2026

    +1

    One additional aspect I would consider is how the selected PAW theme interacts with existing books.

    Allowing users to choose an approved theme is useful, but many dashboards contain explicitly defined background, text, and widget colors. If those remain hard-coded, changing the PAW theme may have little or no effect on the published book.

    It would therefore help if book and widget styling could use semantic or theme-aware colors, so the same book can follow the selected PAW theme without a separate light and dark version. That would also make branding and accessibility easier to keep consistent across themes.