Users & Permissions

Subaccount-Specific Roles & Permissions for Multiple Sub-Account Users
Navigating user permission conflicts when a single client operates across multiple subaccounts. Right now, an Account-level user can easily be assigned to multiple subaccounts under one email login. However, roles and permission toggles are applied globally across every subaccount they touch. Here is a common, real-world bottleneck we hit this week: * Subaccount A (Primary Business): Our client is the business owner. They need full Account Admin privileges to manage billing, integrations, and company-wide settings. * Subaccount B (Local Non-Profit): The same individual serves on the board. In this subaccount, they only need restricted User access (e.g., standard contact viewing, assigned tasks, zero access to sensitive financial/admin tools). Because role and toggle permissions are global to the user profile: * If we make him an Admin in Subaccount A, he automatically inherits Admin capabilities in Subaccount B. * If we strip his permissions down for Subaccount B, he loses the access needed to run his own business in Subaccount A. The current workaround? Forcing the client to manage two distinct logins using email aliases (e.g., name@company.com vs. name+nonprofit@company.com ). While aliases technically function, they create unnecessary friction, confuse non-technical clients switching between accounts on desktop or the LeadConnector mobile app, and introduce compliance/security risks. The Solution We Need: True Role-Based Access Control (RBAC) scoped per subaccount: * Assign a base user login once (single email / single password). * Set the role (Admin vs. User) independently inside each assigned subaccount. * Allow granular permission toggles and "Only Assigned Data" restrictions to be defined on a per-location basis.
0
·
Enhancement
Load More
→