Properly identify same employee account login

Scenario: When an employee sign in from the same computer but had it's IP or Hostname changed, it is logged as a new employee causing a license count use on the same employee.

For our MacOS endpoints, there are certain instances where the hostname of the computer changes I guess depending on the router's behavior where the computer is connected e.g:

Computer Hostname (CH1): MacBook-Endpoint-1

Computer Hostname (CH2): MacBook-Endpoint-1.local

Employee (E): Employee-Name

E logs in initially at computer with the CH1 hostname (E@CH1), and for an instance changed to a router then logged in again on the same computer but this time had its hostname changed to CH2 (E@CH2), so the same E had two entries in the employees being monitored (causing 2 license count, when it should only be one for the same computer and same employee).

Same goes with changing IP's, the behavior on the monitoring is to automatically create a new employee with multiple IPs (causing multiple license usage for that particular employee).

Maybe a MAC based approach to identify an employee and computer login might suffice instead of relying on the IP or Hostname of the employee? This will help Admins review which are truly active for monitoring and which accounts are inactive.

We actually had this issue to almost all of our Mac Users running on a M1 Chip, that's why we regularly review our usage count and then verify from the employees side their current local IP and hostname and then we disable the monitoring for those inactive users (employee entries) in the Teramind dashboard. We are totally unsure where the issue is, but we also have a fixed computer name on all our Mac endpoints, so it is weird when the TM Agent detects an IP instead of the Computer Name. Employees had 2, 4, 6, 8... entries (identified as new login by IP I guess by the TM Agent) coming from the same computer and same employee. In some cases the TM Agent correctly identifies the login based on the Computer Name.