Currently, when a user is assigned to multiple sub-accounts in GoHighLevel, they must share the exact same permission set and access level across all of them.

This limitation makes it difficult to manage users who need different roles or visibility scopes per sub-account — for example, an admin role in one client account, but only a restricted “view-only” role in another.

Proposed Improvement:

Enable administrators to assign unique permission levels per sub-account for the same user. Each sub-account should have its own role and permissions configuration, independent from the global user profile.

Why this matters:

Agencies with multiple clients or brands often have the same team members working across several accounts, but in different capacities.

It would improve security, flexibility, and operational efficiency by removing the need to create duplicate users with different email addresses.

Aligns with enterprise-level user management standards (similar to role-based access control per workspace).

Example Use Case:

A marketing manager could have full access to automation and pipelines in one client sub-account, but only reporting and conversation view access in another — all under the same login.