> ## Documentation Index
> Fetch the complete documentation index at: https://docs.junis.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Squad Collaboration
> Let your squads talk to each other — one orchestrator can ask another squad and bring back the answer
## What is Squad Collaboration?
In Junis, each organization is a **squad** — an AI team with its own orchestrator, agents, knowledge, and personality. Squad Collaboration lets one squad's orchestrator **discover and message another squad** during a conversation, wait for its answer, and bring the result back to you.
> "우리 마케팅 스쿼드에 이번 캠페인 일정 물어봐줘" — your current squad asks the marketing squad and relays the answer, all in one chat.
**Zero setup**: Squad collaboration is automatically available to every orchestrator. There is nothing to configure.
***
## How It Works
Your orchestrator can list the squads you have access to — squads where you are an **active member**, plus **public** squads.
The orchestrator sends your request to the target squad's orchestrator, which answers using its own agents, tools, knowledge base, and wiki.
The response comes back into your current conversation, with the source squad clearly attributed.
### Example
```
You: "Ask our Data squad what last month's churn rate was."
Agent:
1. Lists your accessible squads, finds "Data"
2. Sends the question to the Data squad's orchestrator
3. Data squad answers using its own tools and knowledge
4. Your agent replies: "According to the Data squad, last month's churn was 2.3%..."
```
***
## What You Should Know
You can only reach squads where you are an **active member**, or squads that are **public**. A squad cannot call itself.
Each cross-squad call creates a new conversation in the target squad, visible in that squad's session list, and the incoming request is labeled with its origin (e.g. `[스쿼드 호출: 'Marketing' 조직에서 전달된 요청]`). Nothing happens invisibly.
Usage from a cross-squad call is billed under the **target squad's** billing rules — exactly as if you had chatted with that squad directly.
Squads can chain calls (A → B → C) up to a **maximum depth of 3**, and circular calls (A → B → A) are automatically blocked.
Your agent waits up to a few minutes for the target squad to answer. If the target squad needs longer, you get the session reference so you can open that squad's conversation and read the full answer there.
Very long messages and responses are truncated at generous limits to keep conversations responsive. For large deliverables, ask the target squad directly in its own chat.
***
## When to Use It
"물류 스쿼드에 재고 현황 물어봐줘" — pull answers from the squad that owns the data.
Route a legal, finance, or design question to the squad built for it, without leaving your chat.
Query public squads that offer their expertise to everyone.
Chain up to 3 squads for pipelines like research → analysis → summary.
If your agent doesn't know which squad to ask, just say "어떤 스쿼드에 물어볼 수 있어?" — it will list the squads you can reach.
***
## What's Next?
How multi-agent orchestration works
Managing multiple squads
Each squad's shared knowledge base
Members, roles, and permissions