Choose the right scope
Open the intended subaccount before creating resources. For example, a published flow assigned to an assistant must belong to that same subaccount. Copying an assistant is not a substitute for configuring the destination account’s integrations and resources.
Connected GHL and Direct accounts
The account’s integration type determines the workflow:- GoHighLevel-connected: GHL-specific messaging instructions depend on the connected location and its contacts, tags, and channels.
- Assistable Direct: native account resources provide the customer data path without requiring a GHL location.
Access is separate from connection
A working integration does not grant a user permission to edit its account. Access can come through workspace membership or assignment to a subaccount; individual features can apply further role and permission checks. If a feature is hidden or read-only, ask the workspace owner to review your access. If a resource is missing, check the selected account before recreating it. A “not found” response can also mean the resource is outside the current account’s scope.Which access control to use
For example, a client can access its wallet through account membership without joining the agency workspace. Conversely, a visible Billing link does not grant permission to manage agency pricing.