This is really problematic. Users who are generally the managers/employees in the ghl sub-account SHOULD NOT become contacts in the system.

Having to make the user(manager/employee) a contact(lead/customer) in the system to track activity is really concerning, and I can't understand why this is not a huge issue for everybody.

Because this scenario unfolds with sample of following users

user(manager 1)

user(manager 2)

user(employee 1)

user(employee 2)

user(employee 3)

A contact passes through an automation and say the automation notifies user(manager 1) about a contacts behaviour/action using the internal email notification action.

user(manager 1) now becomes a contact(lead/customer) in the system and gets the notification email.

Now later on when user(manager 2) sends an email to user(manager 1) all the users(employees) can now read this email !!

(manager 2) could be emailing (manager 1) about discussing the possibility of raising a disciplinary issue with one of the employees and now everyone sees this email!!!

Or (manager 1) sends a financial report to (manager 2) everybody gets to read it!

(I appreciate you can make users at the employee level data visibility scope only assigned data but that silos everybody)

Is there anyway you can put in the necessary tracking of user actions without having to make the user a contact(customer/lead)?

This is causing a real headache - if it cant be resolved we might just have to go the 'view only assigned data' option for all users.