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 Jul 15, 2022

AoC - Default Authentication Configuration Option

Request a feature to allow configuration of the default authentication for all new users.

Customer has Packages app set to all members for "Who can send packages to external users"

When packages are sent to external users it creates a new user that has authorization set to Any.

Alternatively, if a user is not sent a package and logs in with SAML their authorization is set to SAML auth.

The customer would like to allow for users to send packages to external but still have all users created with SAML Auth. Currently the only way that can be sure new users are created with SAML auth is to stop users from sending packages to external users. So they have limited this even though they don't want to do so.

Idea priority Urgent