IP restrictions - org admin

If i lock a project down to an IP which isn’t my own and then login - it lets me login and the project shows as locked (as expected) but the slight downfall is then that because i'm logged in as an org admin i can go to the organisation and update the IP allow list with My IP, which then unlocks the projects.

I think updating the org settings should only be possible if the IP of the currently logged in user matches the allow list. If a user locks themselves out then it would require intervention from the provider to unlock it.