This, or the ability to block an organization from being recreated and agents registered under it. We frequently get billed for agents that re-register even after the customer has departed, for a variety of reasons (device offline for weeks, GPO not purged, etc.).

After the client is gone, we don't have any ability to remediate this other than send uninstall from Huntress, as we no longer control the environment. And if a GPO reinstalls, we're at the mercy of the client/new MSP to remove that GPO.

I believe this to be a super important addition. We have cases where offboarded clients fail to remove huntress deployment scripts from their RMM tools, causing agents to reregister with old org ids. Having unique registration keys would allow us to revoke access without needing to redistribute installers to the rest of our clients.

Im looking to rollout huntress to a community of users were each person is limited to enrolling a limited number of seats. Ideally i would like to limit the number of systems individually per tenant. Having single use keys that deployed to a specific tenant would be ideal

This would be a great addition as some clients are a co-managed IT relationship where actual deployment is done through existing client infrastructure and account key is exposed in some way (i.e. powershell script / GPO deployment)

This could also allow for some unique future customization on a per client basis. For example, custom insights and reporting based on compliance requirements only for customer (x,y,z) being pulled through api using their client id key :)