Add a feature to categorise roles, so we can differentiate between privileged and non-privileged roles and apply restrictions

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

Post comment

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.

Shape the future of IBM!

Search existing ideas

Post your ideas

Specific links you will want to bookmark for future use

Add a feature to categorise roles, so we can differentiate between privileged and non-privileged roles and apply restrictions

Please enter your email address

RELATED IDEAS

Add a feature to categorise roles, so we can differentiate between privileged and non-privileged roles and apply restrictions