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 Needs more information
Workspace API Connect
Created by Guest
Created on Mar 11, 2024

Limit number of corg invitations and invitation resents

A penetration test was performed on our internet facing developer portal. One of the findings is the following:

A user (or a script) can invite a large number of people into a consumer organisation and repeatedly resent invitations, essentially spaming recipients.

There is no limit regarding the number of member invitations or resents.

Please provide a fix.

Idea priority High
  • Guest
    Mar 11, 2024

    We do need the Self Service feature, so we cannot disable it.

    It would be great, if the max number of cOrg members can be configured on the catalog level.

    At our company a consumer organisation usually correspond to an application development team. And we want to keep the number of members rather small ("need to know principle"). So the number will probably not exceed 50, but anyway it should be configurable.

    Limiting invitation resents to once per day should be sufficient, ideally, this will also bei configurable

    In the referenced support case to this idea, it is suggested to monitor malicios behavior. That would work for us as well, but we would need to be able to monitor the creation of cOrgs, the members and invitation resents, e.g. via audit log

  • Admin
    Dan Temkin
    Mar 11, 2024

    Self Service can be disabled if this is considered a security risk.

    If we were to limit add the ability to set limits do you have some suggestions or opinions for the different limits you would like to see added to the product. For example

    • max 50 developer/veiwers per Consumer Organization per day.

    • For a consumer organization the same invited email can only be messaged once per day