Skip to Main Content
Cloud Management and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps products. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

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.

Status Submitted
Workspace Apptio
Created by Guest
Created on Jul 11, 2024

Report Visibility permissions looking at all a user's roles

We have a single landing page report for a large number of users in our Apptio. This landing page includes links to a range of different reports - some of which are available to all users with access to the system, but others which are restricted to a specific role. We use role-based visibility of the links at current to limit access to the restricted reports, so users only see the reports they are able to access.

There are a significant number of users who fall across multiple categories - for instance, all users might get report A, but only Service Owners get report B, and Operations Leads get report C. But there are users who are considered both a Service Owner and an Operations Lead, and so they need to be able to see reports A, B and C.

We would like it so the permission settings look at more than just the 'currently active' role. This is how some other permission settings work in the system, to my knowledge, in that if any of your roles has the permission to do something you're able to, so I'm confused as to why this permission only looks at the currently active role. 

Given we have over half a dozen different roles actively used, creating and managing specific new roles for every possible combination of those is highly impractical, and expecting users to shift their own role whenever they need to access a different report is a poor experience. If we were able to restrict component visibility based on all of a user's roles, it would make for a far better user experience for all concerned.