Currently, if you want a team member at the agency level to create sub-accounts as part of their job responsibilities, you must grant them full Agency Admin access. The problem is that this gives them access to many other settings, features, and sensitive areas of the agency account that they may not need or should not have access to.
Even more concerning, HighLevel allows you to enable permissions for creating sub-accounts without indicating that Agency Admin access is required. There is no error message or warning explaining this limitation, making the permission settings misleading and frustrating.
Agency owners should not have to grant employees full administrative access simply to perform a specific job function. This creates unnecessary security risks, particularly if an employee makes a mistake, leaves the company, or misuses their access.
HighLevel should allow agency owners to grant sub-account creation permissions independently of Agency Admin privileges.
This would provide better security, more flexibility, and greater control over employee access.
This is an important security and permissions issue that should be prioritized and resolved as soon as possible.
NOTE: The attached screenshot shows the error my team member received when I gave him Agency-User and the rights to create sub-accounts. The only way to resolve this was by making him an Agency-Admin.

Photo Viewer

View photos in a modal