Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.llmgrid.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

The Teams section allows you to organize users and workloads into logical groups. Teams are a core governance boundary in LLMGrid and are commonly used to manage membership, model access, budgets, and rate limits. Teams can be manually created or automatically provisioned depending on your tenant configuration.

​
Your Teams

The Your Teams tab lists all teams that you own or belong to.

​
Available Columns

  • Team Name
    Human-readable team identifier.
  • Team ID
    Unique identifier for the team. Select the Team ID to view team details and manage members.
  • Created
    Date the team was created.
  • Spend (USD)
    Total spend attributed to the team.
  • Budget (USD)
    Maximum allowed spend for the team, if configured.
  • Models
    Models accessible to the team (for example, all proxy models or a restricted list).
  • Organization
    Organization the team belongs to, if applicable.
  • Info
    Summary information such as the number of keys and members.
  • Actions
    Edit or delete the team (subject to permissions).
Use the search, filters, and reset filters options to quickly find specific teams.

​
Available Teams

The Available Teams tab shows teams that exist in the tenant but that you are not currently a member of. Typical use cases
  • Discover teams you can request access to
  • Review team descriptions and available models
If no teams are available, this view will display a message indicating that there are no teams to join.

​
Default Team Settings

The Default Team Settings tab defines baseline settings applied when new teams are automatically created. These defaults are especially useful for environments where teams are provisioned dynamically.

​
Default Settings Include

​
Models

The default list of models that newly created teams can access.

​
Max Budget

The default maximum budget (in USD) assigned to new teams.

​
Budget Duration

Defines how often the team budget resets. Examples include:
  • daily
  • weekly
  • monthly

​
TPM Limit

Default tokens‑per‑minute limit applied to new teams.

​
RPM Limit

Default requests‑per‑minute limit applied to new teams. Select Edit Settings to update these defaults.

​
Creating a New Team

  1. Select Create New Team.
  2. Provide a team name and optional description.
  3. Configure models, budgets, and limits as needed.
  4. Save the team.
Once created, users and keys can be associated with the team.

​
Team Governance Model

  • Team-level budgets and rate limits act as upper bounds
  • Virtual keys created under a team cannot exceed team limits
  • Usage, spend, and logs can be filtered by team
  • Teams simplify cost attribution and operational ownership

​
Common Use Cases

  • Separate workloads by application or department
  • Enforce spending limits per team
  • Control model access at a group level
  • Attribute usage and cost for internal chargeback
  • Simplify administration of keys and users

​
Best Practices

  • Create one team per major application or project
  • Set budgets and limits early to avoid unexpected spend
  • Use teams in combination with tags for detailed cost tracking
  • Review team usage regularly using the Usage dashboard
  • Restrict model access to what each team actually needs