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 Not under consideration
Workspace Cloudability
Categories Other
Created by Guest
Created on Jun 18, 2025

Ability to limit API Access/Generate API Keys

While Cloudability API access keys can be generated by any user, the role assigned to the user with the key dictates what the users can and can't do with API calls. For example, a base CLDY User role can't do anything with business mappings, as that's an admin level task. See our documentation here: https://www.ibm.com/docs/en/cloudability-commercial/cloudability-premium/saas?topic=api-about-cloudability

We want to allow normal users to create cost reports in the UI but do not want them to us the API to download cost reports.  This is not possilbe today.  We are ok with teams running reports in the UI and manually exporting data on occasion but we are trying to prevent teams from creating integrations with other downstream systems via the API without checking with us first.

We want to control integration access to the data to ensure that it is being used correctly and we properly document the integration so that we can support it.

We’ve had issues in the past where teams have created unknown integrations which become mission critical or don’t use the data properly because they don’t understand the data and then when things go wrong or the #s don’t look right, FinOps gets blamed for something that we didn’t even know existed.

Idea priority High
  • Admin
    Matt Gerow
    Jun 23, 2025

    Thanks for the submission! we appreciate the feedback and walk through of the pain points you are facing. At this point, we have no plans to change the permission model. We limit access to functional areas of the product via role/permissions and limit access to particular data via views, but we don't currently differentiate between accessing cost report data between accessing via UI or accessing via API.

    We'll monitor this for additional feedback and interest we get from other customers as well, but for now this is not on the roadmap.

  • Guest
    Jun 18, 2025

    We'd like to have the ability to generate API keys restricted by a separate permission in FrontDoor.  Currently any active Cloudability user can generate an API key.  Most other tools limit API access to specific administrative roles