Skip to Main Content
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.

Status Future consideration
Categories Source Control
Created by Guest
Created on Jul 11, 2025

Restrict movement of snapshots from one Team's Stream to other Team's Stream

To improve the access to the SCM Streams in same PA, we have a concept where the Visibility of Stream is set to a specific access group that can be accessed through access request. In this concept, the Visibility of each component should be inherited from the stream.

If a stream will be deleted, a snapshot will be created and it has to be assigned to another Stream.

To avoid that Snapshots from Stream with access group A will be assigned to a stream with access group B (Two different Teams) and the components inside the snapshot become visible for Team B, Delete stream permission is assigned to only 1 role "Central Config Manager" .

To use the concept, we need to forbid to move the snapshots to other stream too.

Idea priority Medium
Needed By Quarter
  • Guest
    Sep 11, 2025
    The EWM Ideas Review board looked at this request and decided to keep it on the Backlog as an uncommitted candidate for a future release.
  • Guest
    Jul 28, 2025
    The EWM Ideas Review board looked at this request and requests confirmation on the understanding of the request:
    1. User has a stream which is visible to AccessGroup1. Likely a small group has visibility to the stream.
    2. When you try to delete the stream, it gives you an option to create snapshot for the stream and parent it to another stream. This way you can get it back later if needed. But when you select the stream for associating snapshot, it can have any visibility. That would mean that someone who did not have access to stream earlier may be able to access the snapshot now.
    We are unclear about the statement "Delete stream permission is assigned to only 1 role 'Central Config Manager'."

    From our initial understanding, we think that the behavior being requested is - if stream being deleted has visibility limited to an access group, and the stream being parented-to has accessibility to a different access group or project area/team area, then a warning should be given to the user.
    Request confirmation and clarification on expected behavior.