IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.

Add a new idea Subscribe
Status Functionality already exists
Workspace IBM Envizi - ESG Suite
Categories Base Platform
Created by Guest
Created on Aug 22, 2024

RELATED IDEAS

An API access token can be used by multiple people instead of a API access token per person so a report using an API can be refreshed by multiple people but cannot be accessed by someone who has left the organisation.

The new API access tokens have been introduced to replace the previous method of a username and password. My understanding is that:

  • Each user should have their own API access tokens
  • If that user leaves the organisation then by disabling that user then the access token would also be disabled.

However, how do you deal with the scenario where a single report that uses an API needs to be refreshed by multiple users? This happens all the time for us. It would not be practical for the user to have to enter their API access token every time they wanted to refresh a report.

Idea priority Urgent
Needed By Month
  • Post comment
  • Admin
    Eugene Yu
    Reply
    |     Aug 26, 2024

    Hi Martin - we would suggest you to create a separate contact & login in the system soely for API purposes. Tokens can be generated off from this generic login and be shared and embedded among your organization.

    In fact this would be a preferred method as tokens will then not attach to any individual user logins.

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.