A corpus only helps once an assistant can use it. Corpus connections link a corpus to an assistant, so the assistant searches that corpus's documents before it answers. Because a corpus is separate from any single assistant, one corpus can serve many assistants, and one assistant can draw on several corpora.Why connect corpora to assistants?#
Grounded, specific answers. A connected corpus gives the assistant your organization's actual content to answer from, instead of general knowledge.
Reuse without duplication. Connect the same "Product Documentation" corpus to a support assistant, a sales assistant, and an onboarding assistant. Update it once, and all three benefit.
Mix and match knowledge. Combine a shared company-wide corpus with a team-specific one, for example "Company Policies" plus "Engineering Handbook".
Control without deleting. Turn a connection off temporarily, for example while a corpus is being reorganized, without losing the setup.
How connections work#
Every assistant has a default corpus. It's created with the assistant (named after it, ending in "_Default") and is always connected. You can't turn it off or remove it.
You make changes in Staging. Corpus connections are part of the assistant's configuration, so you add or change them in Staging. People using the assistant don't see the change until you Deploy it to Production. See Staging & Publishing. Attachment can be switched on or off. Each added corpus has an Attachment switch, so you can stop the assistant from using it without removing the connection.
Use cases#
One corpus, several assistants: An IT team connects its "Device Setup Guides" corpus to both the IT help desk assistant and the new-hire onboarding assistant. When a laptop setup procedure changes, they update one document, and both assistants give the new instructions after the next deployment.Filling a knowledge gap: An assistant keeps saying it doesn't know something that's documented in another corpus. Connect that corpus, and deploy.Pausing a corpus: While a corpus is being reorganized, turn its Attachment switch off so the assistant stops using it, then turn it back on when it's ready.You can connect a corpus only to assistants for which you have Admin access.
1. Open the assistant's corpora#
In the sidebar, click Assistants. Find the assistant, click the three dots in its Actions column, then click View Corpora.2. Switch to Staging#
The Agent Corpus Connections page opens in Production, which shows the corpora the assistant uses now. Click Staging at the top right to make changes.3. Choose the corpus to connect#
Click Attach corpus. In the Create Connection panel, open Corpus Selection, search for your corpus, and select it. Then click Create Connection.4. Check the new connection#
The message Connection created successfully appears, and the corpus is listed with its Attachment switch turned on. Use the switch to turn the connection off or on, or the delete icon in Action to remove it.The assistant's default corpus can't be turned off or removed.
5. Deploy the change#
The counter next to Deploy shows how many changes are waiting in Staging. Click Deploy, review the changes, and confirm to make the new connection live in Production.Deploying publishes every pending Staging change for the assistant, not just this connection. Review the list before you confirm. For details, see Staging & Publishing. 