My initial thought on this is that maybe if you want to prevent a user from modifying the security group of other user, using different projects might be a good idea for that, since then the user will be isolated on their project and not able to change the security groups or any other resource from a project they don't have access to.
However there might be a different use case I'm not aware of that cannot be resolved this way, I will be happy to know more about it. For now I'm setting this as opinion since this is expected behaviour and not a bug, but we can keep discussing and change the status as needed.
Hi there! Thanks for your report.
My initial thought on this is that maybe if you want to prevent a user from modifying the security group of other user, using different projects might be a good idea for that, since then the user will be isolated on their project and not able to change the security groups or any other resource from a project they don't have access to.
However there might be a different use case I'm not aware of that cannot be resolved this way, I will be happy to know more about it. For now I'm setting this as opinion since this is expected behaviour and not a bug, but we can keep discussing and change the status as needed.