> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assistable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand accounts and access

> Choose the right workspace and subaccount before configuring an assistant or integration.

A **workspace** groups the agency or account owner's operation. A **subaccount** contains a client or business's working resources, including assistants, conversations, knowledge, and integrations.

## Choose the right scope

| Scope | What to check before editing |
| - | - |
| Workspace | Organization-level settings, members, and billing responsibilities |
| Subaccount | The business, its connected services, assistants, and customer records |
| Assistant | Instructions, model, voice, knowledge assignments, tools, and channel behavior |

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.

Your Assistable subaccount ID and a connected GHL location ID are distinct identifiers. Use the identifier requested by the screen or API. For API scoping, follow [v3 Authentication](/v3/authentication).

## 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

| Control | What it decides | Reference |
| - | - | - |
| Workspace role | Agency responsibilities, including member management and workspace billing | [Roles and invitations](/v3/guides/accounts/invite-users#roles-and-scope) |
| Account membership | Whether the person can enter and work in the intended client account | [Invite an account user](/v3/guides/accounts/invite-users) |
| Navigation permissions | Which portal sections an account-only user sees | [All navigation switches](/v3/guides/accounts/navigation-permissions#available-switches) |
| Account lock | Whether a portal session must pass the workspace admin-password screen | [Portal lock controls](/v3/guides/accounts/portal-lock) |
| API-key scope | Which API resources and actions the key can use | [Authentication](/v3/authentication) |

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.

## Keep account responsibilities clear

Before onboarding a client, confirm who manages its integrations, who may publish assistants, and who funds usage. Use [How Billing Works](/v3/billing-guide) for workspace versus client wallets. Check the current plan and agreement for limits; the account hierarchy alone does not imply unlimited resources.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.