Cloud Management and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
As (1) from the original idea is already in development, I'd suggest limiting this idea more to the "team admin/manager" concept (2).
This is also already on our roadmap, as "limited access to access control" where users with the team/role/user management permissions would only have access to teams/roles/users for which they are also a member of already.
This would prevent the Owner-like authorization of these permissions and not allow the team manager user to elevate their own access.
1. Create a team named team1.
2. Create a role named role1 without "User Management" and "Team Management" permissions.
3. Create a role named role2 with "User Management" and "Team Management" permissions.
4. Create a user named user1, and assign role1 in the default scope.
5. Add user1 to team1, and assign role2 as their role within team1.
6. In the default scope, user1 cannot manage users or teams.
7. When the scope is set to team1, user1 can manage "all users" and "all teams".
➔ We would like to restrict this so that user1 can only add or remove users who belong to team1.