Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Created by Guest
Created on Oct 7, 2025

Implement Team-Based Admin Privileges for Applications

The Problem

Currently, only the original creator of an application can edit it. This creates a significant bottleneck for teams that rely on a shared application. If the creator is unavailable, no one else can make critical adjustments, such as adding a new API. This dependency on a single person slows down development and can halt progress entirely.

The Solution

I propose introducing a system that allows the application creator to grant administrative privileges to other users or team members. This would enable teams to manage shared applications collaboratively and ensure business continuity.

Proposed Privilege Levels

To address potential security concerns, these privileges could be tiered, allowing the creator to assign the appropriate level of access to each team member.

Level 1: Limited Admin

Can add new features (e.g., new APIs).

Cannot change or delete anything set by the original creator.

Level 2: Partial Admin

Includes all "Limited Admin" permissions.

Can also edit existing features and configurations.

Level 3: Full Admin

Includes all "Partial Admin" permissions.

Can delete the application.

Can grant or revoke admin privileges for other users.

Benefits

Implementing this feature would:

Improve Team Collaboration: Allow teams to work together seamlessly on a single application.

Eliminate Bottlenecks: Remove the dependency on a single person for application management.

Increase Efficiency: Speed up processes and prevent unnecessary delays.

Reduce Duplication: Avoid the need for teams to create multiple, redundant applications.

Idea priority Medium