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 Instana
Categories Access Control
Created by Guest
Created on Feb 6, 2026

Possibility to hide API tokens permanently after initial creation

Hi,

API tokens in Instana can always be lookep up after creation and copied by everyone with the appropriate permissions.


In our organisation there is a regulation, that access credentials or similar data needs to be placed in the company PIM system where it can be tightly controlled and nowhere else.


Hence API tokens need to be placed there and not be available anywhere else.


We would need a way to hide the API tokens permanently after the initial creation (like GitHub and others are doing it).


Right now we need to implement a detailed alerting based on the access/audit logs which alerts when someone looks up a token but that is a mere patch and is not fully compliant with our regulations.


Thanks and regards,

Rainer


Idea priority High
  • Admin
    Máté Návay
    Feb 10, 2026

    While the idea makes sense and might be something we'll pursue later, we currently have different changes planned around API tokens and usage which are more widely needed and without any real workarounds.

    To control the access to tokens, I would suggest reducing the number of admins in the Owner group and maybe instead use a new Role which has all permissions, except API token management.
    Currently viewing and creation are tightly tied together and the security aspect of exposing an existing token or creating a new token with even more permissions are not significant enough compared to the pending API features we have on our plans.