Add entity overview table to user management hierarchy docs

Added a summary table describing the user tenant management hierarchy including:
- Organization, Team, Internal User, and API Key entities
- Database table names for each entity
- Brief descriptions and key relationships

Co-authored-by: Krish Dholakia <krrishdholakia@gmail.com>
This commit is contained in:
Cursor Agent 2026-03-19 19:49:30 +00:00
parent dfcf978745
commit 01063bab2b
No known key found for this signature in database

View file

@ -12,6 +12,15 @@ LiteLLM supports a hierarchy of users, teams, organizations, and budgets.
- Users can have multiple keys, and be on multiple teams. [API Reference](https://litellm-api.up.railway.app/#/budget%20management)
- Keys can belong to either a team or a user. [API Reference](https://litellm-api.up.railway.app/#/end-user%20management)
## Entity Overview
| Entity | Database Table | Description | Key Relationships |
|--------|---------------|-------------|-------------------|
| **Organization** | `LiteLLM_OrganizationTable` | Top-level entity for grouping teams | Contains multiple teams |
| **Team** | `LiteLLM_TeamTable` | Group of users with shared settings and budgets | Belongs to an organization, contains multiple users via team membership |
| **Internal User** | `LiteLLM_UserTable` | Users who can create keys and make LLM API calls | Can own keys, can exist across multiple teams, can belong to multiple organizations |
| **API Key** | `LiteLLM_VerificationTokenTable` | Authentication credentials for API access | Can be owned by either a user or a team (or both) |
:::info