Issue & Symptoms
On macOS, you may notice:
Two or more employee records that clearly belong to the same Mac.
The “active” employee changes when the user moves between office, home, or VPN networks.
Activity appears under a different account instead of the actual user’s account.
Cause 1: Hostname changes when switching networks
On some networks, macOS can change the computer’s hostname when you move between office, home, VPN, or different Wi‑Fi networks. Older Stealth Agents (especially before v0.1.230) use the hostname as part of the user identity. When the hostname changes, Teramind may treat the same Mac as a different user, which can create duplicate employees and cause monitoring to “switch” between them depending on the network.
Solution
1. Turn off dynamic global hostname:
Open System Settings (or System Preferences on older macOS).
Go to Sharing.
Make sure Use dynamic global hostname is disabled.
2. Set a fixed primary hostname:
Open Terminal and run:
sudo scutil --set HostName <new host name>
Replace <new host name> with your fully qualified hostname, for example, myMac.
3. Set a fixed Bonjour (local) hostname:
In the same Terminal window, run:
sudo scutil --set LocalHostName <new host name>
Replace <new host name> with a name usable on the local network, for example, myMac.
4. (Optional) Set the computer name shown in Finder:
sudo scutil --set ComputerName <new name>
Replace <new name> with a user-friendly computer name you see in Finder, for example, myMac.
5. Flush DNS cache and restart:
dscacheutil -flushcache
6. Then restart the Mac.
After reboot, the Mac should appear in Teramind with a single, stable identity that no longer changes with the network.
7. (Optional) Clean up duplicates in the Dashboard:
Once you confirm that only one employee is now receiving new activity from this Mac, you may disable monitoring for old employees/computer and remove them from the dashboard.
Cause 2: Permissions granted under the wrong macOS user account
macOS privacy permissions such as Accessibility and Screen Recording are granted per user account, not system‑wide. If an admin installs the agent and grants these permissions under their own macOS account, but the actual employee uses a different login, Teramind may either monitor the wrong account or not fully monitor the intended user.
Solution
1. Identify the macOS account to monitor:
On the Mac:
Go to System Settings → Users & Groups.
Confirm which local user account is the one that should be monitored (for example
jane.smith, not an admin setup account).
2. (Optional) Clear old permission entries:
On the Mac, open Terminal and run:
sudo tccutil reset Accessibility com.teramind.tmagent
sudo tccutil reset Accessibility teramind.tmui
sudo tccutil reset ScreenCapture com.teramind.tmagent
sudo tccutil reset ScreenCapture teramind.tmui
This removes stale Accessibility and Screen Recording entries so you can re‑grant them cleanly.
3. Re‑run the permissions steps (if required):
Check out this article to learn how to enable macOS permissions.
4. Double check the permissions:
While logged in as the user who should be monitored:
Go to System Settings → Privacy & Security → Accessibility:
Find the Teramind entries (e.g., Teramind Agent, System Monitoring).
Uncheck and then re-check them.
Go to System Settings → Privacy & Security → Screen Recording:
Do the same: uncheck and re-check the Teramind entries.
5. Sign out and sign back in:
Log out of the Mac.
Log back in as the monitored user and verify activity is now associated with the correct Teramind user.
6. Clean up incorrect users in the Dashboard
If older employee records are no longer receiving activity after fixing permissions, you may disable monitoring for old employees/computer and remove them from the dashboard.