True RBAC is needed here. Ideally we could assign certain roles to certain organizations in order to restrict visibility to those organization from others at the account-level. Either the ability to create custom roles or the ability to create separate "organization groups" (or something to that effect) that allows us to define which account-level users can access which organizations. More specifically, engineers that require "Admin" role in order to perform their job duties (including creating organizations or managing integrations) but also need to be restricted from seeing certain organizations (your own internal organization, for example).

It's bonkers to not be able to apoint users usage and access to multiple and specific organizations.

Tech X might need access to org A,B,C... But should not be even able to see that D,E,F even exists

Agreed with the 2nd part, we would love to be able to restrict certain organizations to certain techs.

You can already do Organization Only users, but I too would like a tech that can do a group of Orgs instead of a 1 or all approach.

This is a must need in any tool.