Skip to main content
Access: Use the sidebar under Settings → Account for account-level pages, and use the account switcher in the top left to switch between accounts.

​
Who Uses This Area

The Account area is mainly for admins, operations leads, platform operators, resellers, agencies, and anyone responsible for team access, client account structure, or billing ownership. Use it when you need to:
  • decide who can log in and what they can do
  • separate customers, clients, regions, or departments into their own accounts
  • update account-level branding and settings
  • control billing access and integration credentials at the account level
If you are deciding between one account, team members, subaccounts, or agency access, start with the Account Operating Model.

​
Account Structure

itellicoAI uses account boundaries to organize teams, manage access, and scale voice AI operations. Whether you are a single internal team, a reseller with many customers, or an agency managing client-owned accounts, the accounts system separates data boundaries, billing ownership, and management access.

​
Account Types

​
Main Accounts

Main accounts (also called parent accounts) are top-level accounts with:
  • Independent billing and subscriptions
  • Full administrative control
  • Ability to create subaccounts for centralized parent billing or isolated customer operations
  • Separate API keys, secrets, webhooks, and integrations

​
Subaccounts

Subaccounts sit under parent accounts and provide:
  • Isolated accounts for customers, clients, teams, or business units
  • Separate agents, contacts, and conversations
  • Independent team membership and permissions
  • Parent-managed governance, visibility, billing, and API-driven operations where permitted
Key characteristics:
  • Subaccounts can be nested when needed, but most setups should stay one parent-child layer
  • Parent accounts can access child accounts
  • Child accounts cannot access parent or sibling data
  • Users in multiple accounts can switch between accounts with the account switcher

​
Typical Account Structure

Use deeper nesting only when there is a clear governance reason. For most teams, separate customer, client, brand, or department subaccounts under one parent are easier to manage.

​
Access Rules

  • Downward access: Parents can access child subaccounts
  • No upward access: Children cannot access parent data
  • No sibling access: Subaccounts cannot access each other directly
  • Account switching: Users with multiple memberships can switch accounts

​
Security Best Practices

Keep high-privilege roles limited to users who actually need account-wide control.
Audit team members and roles on a regular cadence, then remove stale access promptly.
Use subaccounts to isolate customers, clients, departments, or regions so data boundaries stay clear.
Use separate keys per environment, rotate them regularly, and revoke compromised keys immediately.

​
FAQs

Subaccount capacity depends on your plan and account limits. See Plans for details.
Yes. A user can belong to multiple accounts and switch context with the account switcher.
Yes. API keys are created per account, including subaccounts.
For ownership transfers or complex hierarchy changes, contact support@itellico.ai.

​
Next Steps

Creating Accounts

Create new main accounts and subaccounts

Team Management

Invite members, assign roles, and manage access

Client Service Models

Choose parent billing, agency access, or a hybrid setup

Security

Configure authentication and session controls

API Keys

Generate and manage API keys