> For the complete documentation index, see [llms.txt](https://docs.cortecs.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortecs.ai/web-console/teams.md). # Teams Organize project members, settings, API keys, budgets, and usage with teams Teams let you organize the members of a project into multiple groups. You can then use those groups to separate API keys, apply different inference settings, set spending limits, and understand usage across your organization. For example, one project could contain separate **Development**, **Sales**, and **Support** teams while keeping billing and administration in one place. {% hint style="info" %} Teams are managed separately for each project. If your organization has more than one project, configure the teams for each project individually. {% endhint %} *** ## Who can manage teams Project administrators can: * Create and delete teams * Assign project members to teams * Remove project members from teams * Configure team-specific inference settings and budgets Every project member must belong to at least one team, but a member can belong to several teams at the same time. *** ## The Default team Every project includes a system-managed team named **Default**. It provides a safe fallback and keeps projects working even when you do not create any additional teams. The Default team is used for: * The global inference settings that other teams inherit * Existing or legacy API keys that were created before team assignment was available * Projects that do not use custom teams * Members who would otherwise no longer belong to any team You cannot delete the Default team. You can remove a member from it only after assigning that member to at least one other team. {% hint style="info" %} If you do not need separate groups, continue using the Default team. API keys, settings, budgets, and usage tracking continue to work as before. {% endhint %} *** ## Create a team 1. Open [**Console > Project**](https://cortecs.ai/userArea/console?tab=project). 2. Scroll to **Teams**. 3. Click **Add**. 4. Enter a **Team name**. 5. Click **Create**. Team names can contain letters, numbers, spaces, hyphens, and underscores, with a maximum of 50 characters. Each team name must be unique within the project.
Teams list in the Project tab showing the system-managed Default team and custom teams

Manage custom teams and the system-managed Default team from the Project tab.

*** ## Assign or remove members 1. Open [**Console > Project**](https://cortecs.ai/userArea/console?tab=project). 2. Under **Teams**, find the team you want to change. 3. Click the **Manage members** icon. 4. Select every project member who should belong to the team. Clear the selection for members who should be removed. 5. Click **Save**. You can use the search field to find a member, or **Select all project members** to update the whole group at once. {% hint style="warning" %} Removing a member from a team deletes that member's API keys and budgets associated with the team. Check for active integrations and spending rules before saving. {% endhint %} If a member is removed from their last custom team, the system keeps or returns them to the Default team so that they always belong to at least one team. *** ## Delete a team 1. Open [**Console > Project**](https://cortecs.ai/userArea/console?tab=project). 2. Under **Teams**, click the **Delete** icon next to the team. 3. Review the confirmation message. 4. Click **Delete**. {% hint style="warning" %} Deleting a team also deletes its associated API keys and budgets. Its team-specific inference settings are removed as well. This does not delete the project members themselves. {% endhint %} Members who would otherwise have no team are moved to the Default team. The Default team itself cannot be deleted. *** ## Assign API keys to teams Each new API key belongs to one team. This connects requests made with the key to the correct team's usage and budgets. For more information on the management of API keys, see [API Keys](/web-console/api-keys.md). *** ## Configure inference settings by team The Default team's inference settings are the project's global settings. Every other team reuses these settings unless an administrator creates an override. For more information on the inference settings, see [Inference Settings](/web-console/inference-settings.md). *** ## Set team budgets Budgets can give every team its own allowance or set a different limit for one selected team. Team budgets work together with any project, user, or API key budgets that also apply. For more information on budgets, see [Budgets](/web-console/budgets.md). *** ## View usage by team The Usage view can group and filter costs, tokens, and requests by team. Requests are attributed to the team selected when the API key was created. For more information on the usage dashboard, see [Usage](/web-console/usage.md). *** ## Scenarios ### Personal use For personal use, one person typically needs only one project. You can continue using the system-managed Default team without creating any custom teams. API keys, global inference settings, budgets, and usage reporting all work with the Default team. This is the simplest setup for individual development, testing, and personal applications. ### Small company For a small company, one Cortecs project can usually represent the whole organization. Create teams within that project to represent: * Departments such as Engineering, Sales, or Support * Internal projects or products * Temporary work groups Members can belong to more than one team when their responsibilities overlap. Team-specific API keys, inference settings, budgets, and usage reports make it possible to manage each group separately while keeping the company in one project. Some members may also create or use a separate project for personal work. This keeps their personal API keys, settings, budgets, and usage separate from the company project. ### Large enterprise For a large enterprise, use multiple projects when different parts of the organization require separate billing information. A project can represent a billing boundary such as a business unit, subsidiary, customer account, or independently managed cost center. Within each project, use teams to organize its departments, internal projects, and work groups. This provides separate billing between projects while preserving team-level settings, budgets, and usage reporting inside each project.