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 Feb 8, 2023

Faspex - ability to assign specific storage locations to general users & improved privacy settings

Currently in Faspex v5.0.4, the only workaround for assigning specific storage locations to users is to create a workgroup for each single user. Creating a workgroup for each user would allow for the option to assign a specific package folder to each user (client). If a package is sent to someone outside of that client's organization, then the package will show up in the default storage location. This makes tracking and managing packages (and storage size allotment) much trickier, cumbersome, and time-consuming.

It would be vastly preferred if users did not have to be part of a workgroup or shared inbox.

The other issue is that if one client were to send a package (via their own workgroup) to another organization (to *that* client's separate workgroup), there is a lack of privacy in terms preventing that first workgroup from seeing all other workgroups from the web GUI.

Thank you


Idea priority Medium