This is an IBM Automation portal for Cloud Platform 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
Our Admin team currently manages roles in UrbanCode by allowing Team Leads to add other users to roles they are already part of. However, recent audits have highlighted the need for a more thorough method of verifying that users have been correctly granted access to privileged roles. We have provided guidance to our Team Leads on which roles they can and cannot add users to.
Despite this, if a Team Lead has access to a privileged role (necessary for running their deployments), they still have the ability to add users to that role.
To address this, we propose introducing a new feature, such as a drop-down box, that categorizes roles as either privileged or non-privileged. For non-privileged roles, Team Leads would have the freedom to add any users they wish. However, for privileged roles, restrictions would be applied to prevent Team Leads from adding users. Only the Administration team, part of the System Team, should have the authority to add users to these roles.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
Our development team has a question for you if you can help us get an answer. If you like, we can discuss on our next call if that is better.
What are the permission of the system role that Lloyds describes?
Thank you and let's all discuss priority of this when we meet. A screen share sounds like a great idea. We will take notes for our dev team and share with them.
It is our understanding that the 'Create with Team Permission' is a new feature that comes with version 8. We are yet to fully test this feature. But given the description, (Allow user to create objects with any team mapping so long as they have create permission for that object from some role on any type), we don't believe it would provide the type of restriction we are proposing.
Happy to discuss this with you on our next call, as it might be easier to explain via a screenshare.
Our development team has reviewed this request. They have a question for you and the team. Is it possible that the 'Create with Team Permission' will help with this request? Could you please consult with the team to see if this would help?
The development team has some reservation about the complexity of this request. We could add a priviledged user checkbox to the user that has the right. The user would need a high privilege user to set this flag or checkbox.
Please let us know, and if needed, we can discuss on our next call that is scheduled in January or February. Thank you very much!
We are creating a Jira discussion topic for this Idea and we will review your request with our development team next week. Thank you very much for submitting this idea. We will be providing feedback soon.
Thank you for submitting this Idea. Due to the holiday break that is beginning, we will review this as soon as possible. I will leave in the Submitted state for now, and at the right time, we will move to the Review state.