Option to prevent seeded Fusion roles from giving Visual Builder Studio access

Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

Computershare

Description (Required):

We would like an option to prevent the Seeded Fusion Roles from giving access to Visual Builder Studio.

Use Case and Business Need (Required):

To help speed up development our developers will often use the seeded Fusion administrator roles in the non-prod Fusion environments for build, troubleshooting and migrating. We find though that that most of those roles will also give them Organisation Admin access to Visual Builder Studio which is not what they intended to do and presents a risk as they're then able to delete projects, change permissions in VBS and the override guardrails put into the CI/CD pipeline. It is a constant cat and mouse game to ensure only the necessary people are organisation admins whilst not impeding the work they're