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

# Accounts and organizations

> Learn how Text accounts relate to organizations and how teammates and teams are represented in the APIs.

A user has one Text account, which can belong to several organizations. Within each organization, an agent record stores that user's chat settings and group memberships.

> [!NOTE]
>
> Text uses different terms for people and teams in the app and APIs. The Text
> app calls people who handle conversations *teammates*. The API represents
> those users as *agents*. The app uses *team* as a general term, while the APIs
> use *groups* to route chats and *teams* to route tickets.

## Organizations

An organization brings together the accounts, chats, tickets, and settings for one business or workspace.

A few things to know:

* Every organization has at least one account and one owner.
* One account can belong to multiple organizations.
* Each account has a default organization that opens when the account signs in.

Most APIs identify an organization with `organization_id`. Some APIs and client-side configuration use `license_id`. There is no general public endpoint for converting between them, so retrieve and store the identifier required by each API.

> [accordion] Find your organization and license IDs
>
> Find `organization_id` in the Text app or retrieve it with [List
> organizations](https://www.text.com/docs/api/global-accounts/organizations/list-organizations.md). For an
> API that requires `license_id`, use [Get license
> info](https://www.text.com/docs/api/agent-chat/v3.5/configuration/get-license-info.md).

## Accounts and agents

A user who signs up to Text has one account with an `account_id`. Organization membership connects that account to an organization. The Configuration API represents this user within that organization.

| Record | What it represents | Where to find it |
| - | - | - |
| Text account | One Text user, their credentials, and their organization memberships | [Global Accounts API](https://www.text.com/docs/api/global-accounts.md) |
| Account settings for an organization | The account's role, permissions, and settings in one organization | [Global Accounts API](https://www.text.com/docs/api/global-accounts/account-organization-settings/get-account-settings-for-an-organization.md) |
| Agent | The account's chat settings in one organization, including group membership and routing settings | [Configuration API](https://www.text.com/docs/api/configuration/v3.6/agents/list-agents.md) |

If one account belongs to several organizations, its agent settings can differ in each organization.

![One Text account can belong to more than one organization](https://mintcdn.com/text-56a1eab5/w6OUMq7cYmabTZh8/public/images/key-concepts/users-and-accounts-light.png?fit=max\&auto=format\&n=w6OUMq7cYmabTZh8\&q=85\&s=b89a828ffd5c9b9039babae19a156311)

## Chatting groups and ticketing teams

The APIs use separate resources for routing chats and tickets:

| Text app concept | API resource | Purpose |
| - | - | - |
| Chatting team | `group` in the [Configuration API](https://www.text.com/docs/api/configuration/v3.6/groups/list-groups.md) | Groups agents and routes chats |
| Ticketing team | `team` in the [Ticketing API](https://www.text.com/docs/api/ticketing.md) | Assigns and routes tickets |


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