Skip to Main Content

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portal, please send email describing the issue to for resolution. For more information about IBM's Ideas program visit

Status Future consideration
Workspace Aspera
Created by Guest
Created on May 7, 2022

Per-user private distribution list in AoC

Provide a feature where an AoC user can create their own distribution list.

In the list they can enter existing AoC usernames as well as external recipients. They can then save their list with a name. When sending a package they send to the list and package is sent to all recipients on list. There is already a facility to do this in Faspex.

I can't seem to find a good workaround. You can create a shared inbox but if you send to the shared inbox all users are required to authenticate and that will seem clunky to some users, having to create an IBM ID just to download the package.

Idea priority Low
  • Guest
    Jun 22, 2022

    As a workaround you could create a group that contains all the users you would like in a DistibutionList. Then users can add the group instead of a user when creating a package. Note this is not exactly the same thing as a DL that is only for a user. The group would be available for any user in the workspace to send to....But this might be a usable workaround.