Skip to main content
Create and manage groups of agents that work together with shared context, tools, and guardrails. Kubiya Platform Overview A team is a coordination layer over multiple agents. Teams inherit execution settings from environments, share credentials and Skills, and run with consistent OPA policies. Use teams to align agents around a function (e.g., Platform Engineering), a domain (e.g., Security Operations), or a project.

​
When to use

  • Several agents must collaborate on related tasks.
  • You want shared credentials, tools, and policies applied consistently.
  • You need clear separation by department, sensitivity, or project.

​
Prerequisites

  • At least one Environment (Ready).
  • One or more Agents created.
  • Any required secrets or integration credentials are available (ideally attached at the environment level).

​
Create a Team

Open: Teams > Create Team and complete the tabs below. You can save and edit later. Teams Creation

​
1) Basic

  • Team Name and Description: keep purpose-driven and clear.
  • Visibility:
    • Private – only you can use.
    • Organization – shared with your org.

​
2) Deployment

Defines where the team can run and what it inherits.
  • Runtime: choose the execution runtime (default is fine).
  • Environments: add one or more environments. Teams inherit env-level configuration and can run wherever there’s capacity.
  • Execution Environment (per team):
    • Environment Variables – non-secret parameters.
    • Secrets – attach only if team-specific (prefer env-level).
    • Integration Credentials – connect clouds, chat, observability, etc. Tip: If you’ll run the same team in dev/stage/prod, add all environments now and keep variations (endpoints, tokens) at the environment level.

​
3) Members

  • Select the agents that belong to this team. Add as many as needed.

​
4) Tools

  • Attach Skills the team can use (file ops, shell, Docker, Python, …).
  • Teams also inherit any Skills configured on the selected environments.

​
5) Advanced

  • Team Instructions – system prompt for coordination guidance.
  • AI Model & Temperature – defaults for team coordination.
  • Team Context – add Knowledge Base items and Resources the whole team can access.
  • OPA Policies – select policies to enforce rules and constraints at the team level. Note: Context and policies here are visible to all agents in the team.
Click Create Team.

​
Runtime behavior

When a task targets a team, Kubiya uses the team’s environments, credentials, tools, and policies to coordinate member agents through the workflow. Each step still runs in an isolated container with streaming logs and a full audit trail.

​
Manage

  • Configure the team anytime to adjust environments, tools, context, or policies.
  • Add/Remove members as responsibilities change.
  • Use the project filter on the Teams page to keep views focused.
  • Delete unused teams (agents remain available for other teams).

​
Best practices

  • Start with the minimum set of agents and least-privileged Skills.
  • Centralize shared config in Environments; attach at team level only when unique.
  • Use descriptive names tied to purpose (e.g., “Security Operations”).
  • Add OPA policies early for safety.

​
Troubleshooting

  • Team can’t access a system: Verify the Environment, Secrets, and Integration Credentials are attached and valid.
  • Tasks stay pending: Ensure at least one worker is connected to a queue in the target Environment.
  • Permission denied: Check OPA policies at both Team and Environment levels.
  • Tool missing at runtime: Confirm the Skill is attached to the Team (and still present on the Environment, if inherited).