> ## Documentation Index > Fetch the complete documentation index at: https://docs.openlayer.com/llms.txt > Use this file to discover all available pages before exploring further. # Assign teams > Group API keys so they share usage limits and guardrails A team is a grouping of API keys. Put related keys on a team, and any **usage limit** or **guardrail** you scope to that team applies to all of them at once. It's the way to govern many keys with one rule, like a single monthly spend cap across every app a squad ships. ## Create a team Teams are created inline, wherever you pick one. When you create an [API key](/gateway/api-keys) or an [invite](/gateway/invites), type a new name in the **Team** picker and the team is created on the spot. Existing keys can be moved onto a team from the API keys table. Creating a team from the team picker ## How team rules combine with key rules Usage limits and guardrails can target a single key or a whole team. When both exist, both apply: * A **team limit** caps the combined usage of every key on the team. * A **key limit** caps that one key, on top of any team limit. Guardrails work the same way. Scope a rule to a team to cover every key at once, or to a single key for an exception. See [Set usage limits](/gateway/budgets-and-limits) and [Guardrails](/gateway/guardrails).