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



Add a new idea Subscribe
Workspace Cloud Pak for Data
Components Cloud Pak for Data Platform
Created by Guest
Created on Sep 30, 2026

RELATED IDEAS

Restrict Data Visibility in IBM SaaS Asset Preview, Profiling, Visualization, and Catalog

Organizations often onboard sensitive, regulated, or confidential datasets into IBM SaaS environments for governance, lineage, metadata management, and data product publication. While business and technical metadata should remain discoverable, the actual data content should not be exposed within the platform.

I propose a capability to disable or restrict access to data values across the following areas:

  • Asset Preview
  • Data Profiling
  • Data Visualization
  • Catalog Published Assets

This would allow users to discover, govern, and request access to data assets without exposing underlying records or sample data. Metadata such as schema, column names, descriptions, ownership, classifications, lineage, quality scores, and governance information should remain available, while data content remains hidden.

Benefits:

  • Improved protection of sensitive and regulated data.
  • Reduced risk of unauthorized data exposure.
  • Better alignment with privacy, security, and compliance requirements.
  • Supports metadata-driven governance without requiring data visibility.
  • Enables organizations to safely publish data assets to catalogs while maintaining strict control over data access.

How it should work: Provide an asset-level or catalog-level configuration that allows administrators or data owners to:

  • Hide asset preview data.
  • Disable profiling results that expose data values.
  • Disable visualization features that render actual data.
  • Publish metadata-only assets to catalogs.
  • Apply the setting through governance policies or classifications for sensitive datasets.
Needed By Yesterday (Let's go already!)
  • Admin
    Susanna Tai
    Oct 1, 2026

    It is on our product roadmap to support functional credentials for Profiling and Discovery. Development is well underway, and once available, connection credentials can be provided for use for specific functions only, such as running metadata import or running profiling.

    It will be through the proper understanding and use of personal credentials, shared credentials and functional credentials that will determine if and how data can be accessed by users via a connection.

    Data access through the following areas are enabled through personal or shared credentials provided with the connection. Therefore, if the desire is to disallow access to data, then one should not create shared connections at bare minimum. You can set up connections to require personal credentials, then in order to preview data, profile data etc, the user will need to provide his own personal credentials. Functional credentials provided for profiling or discovery can only be used for those purposes only, and they cannot be used for asset preview, data visualization etc.

    • Asset Preview

    • Data Profiling

    • Data Visualization

    • Catalog Published Assets

    Regards,
    Susanna Tai
    Product Management Team

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.