An
orchestrator
is a special domain type that does not index any content of its own.
Instead, it fans an incoming question out to multiple
standard source domains
, then
merges and ranks their answers into a single response. Use an orchestrator when knowledge is
split across several product or team domains and you want one chatbot that can answer across
all of them.
Because orchestrators hold no content, they require
no embedding configuration
—
only an LLM configuration for merging and ranking source answers. Retrieval, attribution, and
content quality are all owned by the underlying source domains.
- From the Domains sidebar, click + Add.
- Choose the domain type Orchestrator.
- Enter a name and an optional description.
- Choose the default LLM configuration or supply a custom one. If you
provide a custom configuration, click Validate to verify connectivity before
continuing. Note that no embedding configuration is requested for orchestrators.
- Click Create. A banner appears directing you to configure source domains from
the Sources page — the orchestrator cannot answer anything until at least one
source is linked.
Open Settings → Sources on the orchestrator. You will see a checklist of every
standard domain in your organization (other orchestrators are excluded). Each row
shows the source domain's agent card description and its topic chips so you
can judge what that domain covers at a glance.
- Select the source domains the orchestrator should route questions to.
- Click Save.
If a previously linked source is no longer eligible (for example it was deleted or
converted), a warning is shown so you can update the selection.
The quality of orchestrator routing depends directly on each source
domain's
agent card. Make sure every source you link has a complete agent card —
see the
Agent card topic.
Analytics for an orchestrator are limited to App usage, Feedbacks, and
Unanswered questions. The Attributions, Compare feedback,
Human feedback, and LLM as a judge tabs are hidden, because document-level
attribution and quality are owned by the source domains, not the orchestrator. To review
those metrics, open the analytics of the individual source domain.
FAQ
What is an orchestrator domain and when should I use one?
An orchestrator is a special domain type that doesn’t index any content itself. It sends an incoming question to multiple standard source domains, then merges and ranks their answers into a single response. Use it when knowledge is split across several product or team domains and you want one chatbot that can answer across all of them.
Why doesn’t an orchestrator domain need an embedding configuration?
Orchestrators hold no content, so they don’t perform their own retrieval and therefore require no embedding configuration. They only need an LLM configuration to merge and rank answers from source domains. Retrieval, attribution, and content quality are owned by the underlying source domains.
How do I create an orchestrator domain?
From the Domains sidebar, click + Add, choose the Orchestrator domain type, and enter a name (and optional description). Choose the default LLM configuration or provide a custom one, validating connectivity if you supply a custom configuration. Click Create, then go to the Sources page to link at least one source domain before the orchestrator can answer anything.
How do I configure source domains for an orchestrator?
Open Settings → Sources on the orchestrator to see a checklist of every standard domain in your organization (other orchestrators are excluded). Select the source domains you want the orchestrator to route questions to, then click Save. If a previously linked source becomes ineligible (for example, deleted or converted), a warning appears so you can update your selection.
What analytics are available for an orchestrator domain, and why are some tabs hidden?
Orchestrator analytics are limited to App usage, Feedbacks, and Unanswered questions. Tabs like Attributions, Compare feedback, Human feedback, and LLM as a judge are hidden because document-level attribution and quality are owned by the source domains, not the orchestrator. To review those metrics, open analytics for the individual source domain.