At the moment, when you create an integration, say for ScreenConnect, the integration lives at the parent level of the entire organization.
In some instances, primarily larger MSPs where you have multiple brands under one massive ImmyBot tenant, this can become challenging to manage.
Ideally, if you have child-MSPs under a parent MSP, you would want to also allow them to bring in child integrations that only their customers would be using.
At the moment, you can bring as many integrations as you want from the same product, but that wont protect any of the MSPs inside a large organization from mistakenly mapping the wrong integration to the wrong tenant.
Ideally this is all relational, so if an integration lives at a child tenant, RBAC applies within that child tenant.
Happy to help guide this feature, its a unique problem, but a growing one as the Private Equity future of Managed Services expands.