Skip to Main Content

This is an IBM Automation portal for Integration 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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace Aspera Ideas
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.