Please make the NinjaOne connection more like the SentinelOne connection.

While connecting NinjaOne to the SIEM, we were not able to split the data coming in by the Organization as built in NinjaOne. The events being ingested by the SIEM show the NinjaOne Organization, but all of the data can only be sent to a single Huntress Organization.

SentinelOne allows for a single API key to be created. This only has to be connected one time in Huntress, then any organization current or future, will show as an Unmapped Organization. This capability is not available for NinjaOne, but it needs to be! Please.