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

# Manage Teams in Tyk AI Studio

> Understand how to use Teams in Tyk AI Studio to organize users and manage role-based access control (RBAC) for LLM providers, data sources, and tools.

## Availability

| Edition | Deployment Type |
| :- | :- |
| [Community](https://tyk.io/docs/ai-management/ai-studio/overview.md#community-edition) & [Enterprise](https://tyk.io/docs/ai-management/ai-studio/overview.md#enterprise-edition) | Self-Managed |
| Teams in Tyk AI Studio help you organize [Users](https://tyk.io/docs/ai-management/ai-studio/users.md) and easily manage their access to [LLM providers](https://tyk.io/docs/ai-management/ai-studio/llm-management.md), [data sources](https://tyk.io/docs/ai-management/ai-studio/datasources-rag.md), and [tools](https://tyk.io/docs/ai-management/ai-studio/tools.md). By linking Teams to specific [Catalogs](https://tyk.io/docs/ai-management/ai-studio/catalogs.md), you ensure users access only the AI resources relevant to their role. | |

```mermaid theme={null}
graph LR
    User1[User: Alice] --> TeamA[Team: Developers]
    User2[User: Bob] --> TeamA
    User3[User: Charlie] --> TeamB[Team: Support]
    
    TeamA -->|Access| LLMCat[LLM Catalog: GPT-4]
    TeamA -->|Access| ToolCat[Tool Catalog: Code Search]
    
    TeamB -->|Access| LLMCat2[LLM Catalog: Claude]
    TeamB -->|Access| DataCat[Data Catalog: KB Articles]
```

### Use cases

* **Role-Based Access Control**: Group developers into an "Engineering" Team and grant them access to advanced LLM models and coding tools, while grouping support staff into a "Support" Team with access to customer knowledge bases.
* **Resource Isolation**: Ensure that sensitive data sources (like HR documents) are only accessible to the "HR" Team by linking the specific data [Catalog](https://tyk.io/docs/ai-management/ai-studio/catalogs.md) only to that Team.
* **Simplified Onboarding**: When a new employee joins, simply add them to the relevant Team to automatically grant them access to all the necessary AI tools and models for their department.

### Community vs Enterprise Edition

In the **Community Edition**, the Teams feature is not available for custom configuration. Instead, there is a single, built-in **"Default" Team**. All users are automatically assigned to this Default Team, and it is permanently linked to the default catalogs.

In the **Enterprise Edition**, you have full access to create, manage, and delete custom Teams, allowing for granular Role-Based Access Control (RBAC) across your organization. Note that even in the Enterprise Edition, the "Default" Team cannot be deleted.

## What is a Team?

A Team acts as the central access control mechanism in Tyk AI Studio. Instead of assigning permissions to individual [Users](https://tyk.io/docs/ai-management/ai-studio/users.md), administrators assign [Catalogs](https://tyk.io/docs/ai-management/ai-studio/catalogs.md) (LLM providers, Data sources, and Tools) to a Team. Users are then added as members of the Team.

This architecture simplifies permission management, as a user's access rights are dynamically inherited from their Team memberships. A user can belong to multiple Teams, and a Team can have multiple Catalogs of different types.

## Configuration

When configuring a Team, the following options are available:

* **Team Name**: A descriptive name for the Team (e.g., "Solutions Architects", "Marketing").
* **Manage Team Members**: An interface to search and add existing users to the Team, or remove current members.
* **Roles** (Enterprise Edition): The roles that every member of the Team inherits in the admin UI and API. Refer to [Roles and Permissions](https://tyk.io/docs/ai-management/ai-studio/rbac.md).
* **Add Catalogs**: Sections to link the Team to specific catalogs:
  * **LLM providers catalogs**: Grants access to specific AI models.
  * **Data sources catalogs**: Grants access to specific datasets or knowledge bases.
  * **Tools catalogs**: Grants access to specific tools (e.g., web search, calculators).
* **Team budget** (Enterprise Edition, when Team budgets are on): The monthly budget, the budget start date, and the default allocation for each new App. You also select the action at the limit: **Alert administrators only** or **Alert and block the team's Apps**. Refer to [Team Budgets](https://tyk.io/docs/ai-management/ai-studio/budgeting.md#team-budgets).

## How to Create a Team

To create a new Team in Tyk AI Studio:

1. Navigate to **Access > Teams** in the admin UI sidebar.
2. Click on the **Create team** button.
3. Enter a descriptive **Team name**.
4. In the **Manage team members** section, search for existing [Users](https://tyk.io/docs/ai-management/ai-studio/users.md) and add them to the Team.
5. (Enterprise Edition) In the **Roles** section, select the **Team roles** that the members inherit.
6. In the **Add catalogs** section, select one or more [Catalogs](https://tyk.io/docs/ai-management/ai-studio/catalogs.md) for this Team. You can select LLM provider, Data source, and Tool catalogs.
7. Click **Create team** to create the Team and apply the access rules.

![Create Team Form](https://mintcdn.com/tyk/MNmoZfm1CtCrsgHi/img/ai-management/ai-admin-team.png?fit=max\&auto=format\&n=MNmoZfm1CtCrsgHi\&q=85\&s=9a576e8faac76211a60ef8a9e4d42238)

## Team Budgets

In the Enterprise Edition, a Team can have a budget. The budget limits the total spend of the Team's Apps, and gives each new App an allocation from a pool. Team budgets are off by default. To turn them on, set the **Team budgets** switch on the Teams page. For the full behavior, refer to [Team Budgets](https://tyk.io/docs/ai-management/ai-studio/budgeting.md#team-budgets).

To make sure that an App goes to the correct Team, set a **Budget team** on the user. AI Studio gives each new App of the user to that Team.