Currently, all conversations (email, SMS, etc.) are stored at the contact record level and are visible to any user who has access to that contact—including followers and non-owners. This creates an all-or-nothing visibility model where users can see conversations they did not send, receive, or need access to.

This is a significant limitation for organizations that require confidentiality between users, such as rehabilitation services, healthcare-adjacent organizations, legal teams, HR departments, and nonprofits handling sensitive client information.

Example use case:

In a rehabilitation or healthcare setting, a single patient (contact) may interact with multiple staff members (therapist, case manager, intake coordinator). Under the current system, all assigned users or followers can see every conversation tied to that patient, including sensitive or private communications that should be restricted by role or sender. This poses privacy, compliance, and ethical risks.

Requested functionality:

Introduce role-based and/or conversation-level privacy controls that allow admins to:

• Restrict users to viewing only conversations they personally sent or received

• Limit visibility to conversations created by specific roles or teams

• Optionally mark conversations as private or restricted (e.g., sender + admin only)

While “Only Assigned Data” limits which contacts a user can see, it does not address visibility of conversations within shared contacts. Granular conversation privacy controls would allow GoHighLevel to better support regulated and trust-sensitive industries without forcing contact duplication or sub-account workarounds.