We are in the process of evaluating Huntress and its many products, but the first thing I am noticing is that if we deploy Huntress internally than all of our Staff who we give access to Huntress would have way too much access to our Internal Configuration. ISPM, for example, I discovered that even the lowest role, User, in the Huntress portal can still make changes to the Conditional Access Policies within ISPM, so not even leveraging this role would prevent the ability for a staff member to degrade the security of our Internal MS365 if we were to integrate it with ISPM. This is very concerning. What I would really like to see happen is User Scopes, where we could assign selected Organizations for any given Account User to have restricted access to only selected Organizations within their User Scope.