This portal is to open public enhancement requests against products and services offered by the IBM Data & AI 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,
Post an idea
Upvote ideas that matter most to you
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
Certain metadata for specified tables or databases might be more sensitive than others and require elevated permission to see the details, especially the physical location (Application/Connection/host details) in our systems of that sensitive data. We might specify a role or permission level for select people to see that and require a separate approval to get added to that role. At the same time, we might want to automatically bar access to that metadata based upon the user's physical location, employment type (employee vs. contract), or their role in the company as provided from other sources (i.e. HR systems).
Today, data protection rules can be created to deny access to the asset based on user, assigned terms, data classes, classifications.
Can you provide more specifics on "type of data" and "type of person" that you are thinking of?
Does this relate to access control based on rules/policies in Watson Knowledge Catalog based on department and role?